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…
We’re excited to publically announce that Matic Network is partnering with Gitcoin to launch the Build-n-Earn Program – assisting dApps t…
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.
If the user is working with a locked account in a node, they need to manually open a separate console to unlock it before running any CLI operation. Instead, detect locked accounts and prompt for the password.
Avoid asking for the password as an option in the command line, since it can be easily sniffed (and is even kept in bash history). Instead, ask for them interactively, or use a [dedicated file descriptor](https://stackoverflow.com/a/6607773) or environment variable for automated workflows.
Do not discard the password after unlocking, since the CLI operations may take long enough that the account is re-locked. Capture these errors, and re-unlock the account as needed.