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.
Sentry nodes are one way to protect validators from a DOS attack by not exposing them directly to the internet. Sentry nodes are full nodes which connect to other validators and the peer-to-peer network and insulate the validator. The validator node (the one with the signing keys) is kept isolated from the rest of the gossip network and is only connected to the sentry node(s).
This task is to create a sentry node configuration and script which can launch two separate nodes and have them connected to each other so that one is public-facing to the p2p network (the sentry) and the other only connects to the sentry (the validator). The validator should still be able to participate in Polkadot consensus on the Alexander testnet. When everything is working, write a short guide on how someone would deploy it. You can base the guide on the [current validator guide](https://wiki.polkadot.network/en/latest/polkadot/node/guides/how-to-validate/) for Polkadot. However, do not repeat content already written there, instead write your guide as an “extension” to this already existing one.