Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
Aloha, Gitcoiners! How do you feel about Data Dignity, Quadratic Voting, Quadratic Finance and Decentralized Identity?
KERNEL is an 8-week, invite-only program for top tech talent looking to build relationships, products, and companies in blockchain and Web 3. 100 tal…
Type in [[ 2- term.length]] more characters to get results
[[ result.title ]]
[[ result.description | truncate(70) ]]
No matches found
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
The source code of a verified contract is displayed without carriage return when it is saved with Unix line endings (`\n` instead of Windows' `\r\n`).
Because of this, the code is not readable, e.g., here: https://blockscout.com/poa/core/address/0xb87b6077d59b01ab9fa8cd5a1a21d02a4d60d358/contracts
At the moment, I see the next picture:
However, if we copy the code and paste it in Sublime, we'll see it's ok.
Include a library that provides line numbers, and code highlighting for the source code contract verification section.