Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for 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.
In partnership with Protocol Labs, we’re excited to welcome builders from everywhere to APOLLO, your mission control to engage with the builder…
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.
As discussed for the first version of the WalletConnect specification, the permission requests could be expanded in the future to include different levels of data being shared by the Wallet to the Dapps, allowing Dapps to request it with the permission of the User
However to complete our first version we will stick to only sharing an array of account addresses owned by the User, similar to web3.eth.accounts and the number of accounts shared is ought to be controlled by the User through the wallet
* Check the type of data provided is either an array or a string
* Verify that the strings in the array or the string are valid addresses
* Wrap in an array if it’s a single string
* Provide explicit errors for developer debugging