Last Updated: 05/2022
Why Become a Proton Block Producer?
Join the Proton ecosystem and earn income as a trusted Block Producer (BP) by providing infrastructure to the growing Proton network.
Receive daily rewards from system inflation in XPR
Proton Blockchain has annual inflation which accrues to both staked XPR holders and Block Producers. 1% of the annual inflation is designated to BPs to keep the network operating efficiently.
Develop products on the Proton ecosystem
Being a BP is a great opportunity to learn the Proton ecosystem, opening the door for fast blockchain applications like dApps, DEXs, NFT marketplaces, and more. Proton offers high speed and high throughput performance for developers.
Unlock preferential consideration for Worker Proposal Funding and Bounty Projects
Proton BPs are an excellent pool of candidates for paid development work on the Proton ecosystem. Many BPs have side contracts, or have been awarded bounties to advance the development of Proton Blockchain.
Steps to become a Proton BP:
- Read through this Guide
- Join the Testnet Telegram
- Successfully launch and maintain a node on the Proton Testnet for two weeks
- Must sign blocks without issues for two weeks on Testnet
- Must maintain Testnet infrastructure even after registering on Mainnet
- Launch your Proton Mainnet Block Producer
Proton BP Requirements:
- Be a Legal Entity
- Production Node: High performance, low latency infrastructure meeting the following criteria:
- CPU: 3.5+Ghz Processor tuned for performance mode; bare-metal vs. shared/vps instance
- RAM: 64GB+
- Drives: 1TB+ SSD (NVMe preferred)
- Bandwidth: 50mbit/s+
- Provide the standard nodeos HTTP API (ie: /v1/chain/)
- Public API/P2P endpoints should NOT be run from block production node. BP node should have no pubically exposed services
- EOS-VM OC mode must be disabled and last block in round released early (see configuration notes)
- Response Times - In the event of any issue detected with mainnet/testnet infrastructure, the BP needs to provide the following response times:
- Response/Acknowledgement of issue - 4 hours
- Resolution of issue - 12 hours
- Proper monitoring and available staff to address issues is required
- Publish BP Information:
- Properly formatted bp.json provided at website used during BP registration
- Public API/P2P endpoints listed properly for each network (mainnet and testnet)
- BP logo/links properly showing on protonscan.io
- Secondary Infrastructure: Producer nodes should have no public services exposed; a dedicated API/P2P server is required.
- Backup Nodes and Syncing: A backup producer in a separate location is recommended. It is suggested to always peer with the BP before and after you in the schedule (cleos get schedule)
- Hyperion History Node: Hyperion requires a state-history node (which requires a few extra settings and additional disk space) as well as the infrastructure to run the Hyperion services (ElasticSearch, RabbitMQ, NodeJS indexer/api)
- AtomicAssets API Node: Atomics API also requires a state-history node and additional infrastructure to run the Postgres, indexer, and api services)
- Load Balancing: Load balancing and HA services for all services is recommended (HAProxy/nginx with multiple backend servers)
Metal will vote subjectively for BPs, taking the following criteria into account as competitive but not required factors:
- Uptime of the nodeos endpoints
Proton Consortium is responsible for maintaining the BP requirements and protecting the security of the chain. If a BP fails to comply with the requirements, a one week temporary unregistration from mainnet may be imposed (or longer if unaddressed or repeat offenses).