Operating a DevNet CDN PoP Node
The binary of the CDN PoP node For DevNet2 is publicly available.
Fill out this form to be notified of new releases and to be entered for a chance to win on-chain prizes: https://docs.google.com/forms/d/e/1FAIpQLScbxN1qlstpbyU55K5I1UPufzfwshcv7uRJG6aLZQDk52ma0w/viewform
💡 Prepare for Testnet: Run a DevNet2 node, and keeping it running 24/7 will increase your node score, this will directly translate into a high node score for Testnet. The higher the node score the more traffic the protocol will direct to the node and increase the rewards.
Key Features
Location-Based Rewards: Operators in underrepresented or high-demand regions earn additional incentives.
PoP Node Rewards: Rewards are based on metrics such as data served, latency, and uptime. Consistent uptime and performance standards yield higher rewards, while downtime and churn result in rejoin penalties to deter disruption.
Perform basic tests
Last updated