A complete community guide to XDC Network's node architecture — what masternodes are, the upcoming Staking, Rewards & Burning upgrade (now live on Apothem), the new three-tier node structure, and rewards.
The XDC Network is entering one of the most significant phases in its history. The XDC 3.0 Staking, Rewards & Burning upgrade introduces a new three-tier node architecture — Core Validator (Masternode), Protector Node, and Observer Node — along with a redesigned reward mechanism and a token-burning model to control inflation.
The upgrade is currently live on the Apothem Test Network, and a security audit is in progress before the mainnet rollout which is scheduled in October. This is the right time for every community member, node operator, and prospective staker to understand what's changing, why it matters, and how to prepare.
This article covers everything: what a masternode is, the current node structure, the upcoming node roles and their rewards, KYC requirements, node setup, and infrastructure options.
What Is a Masternode?
A masternode is a full node on the XDC Network that does far more than simply store a copy of the blockchain. Masternodes are the backbone of the network — they:
- Validate transactions and produce (mine) blocks
- Participate in consensus via XDC's Proof of Stake mechanism
- Guarantee uptime, security, and decentralization for the entire ecosystem
To operate a masternode, an operator must lock 10,000,000 XDC as self-bond collateral. This economic stake ensures that every validator has real skin in the game.
In return, masternode operators earn block rewards and participation incentives, making it both a service to the network and a yield-generating activity.
Key requirements at a glance:
| Requirement | Detail |
|---|---|
| Stake | 10,000,000 XDC |
| Uptime expectation | 100% — dedicated or cloud server infrastructure |
| KYC/KYB | Mandatory for all node operators |
| Rewards | Block rewards + incentives, distributed per epoch |
The Current Node Structure: Masternodes and Standby Nodes
Today, the XDC Network operates with two node categories:
Masternodes (Validators)
The active set of 108 validator nodes that take turns producing and validating blocks. These nodes participate directly in consensus and earn the highest rewards.
Standby Nodes
Nodes that have staked the full 10M XDC and meet all requirements, but are outside the active 108 validator set. They remain synced and ready to step into the validator set when a slot opens, and earn a slightly lower reward rate for maintaining readiness.
This two-tier model has served the network well — but XDC 3.0 takes it much further.
What's Changing: The XDC 3.0 Three-Tier Node Architecture
Under the Staking, Rewards & Burning upgrade, the network moves from the Masternode/Standby model to a layered, three-role consensus architecture. Every role still requires the same 10M XDC stake — what changes is the function each node performs and the reward it earns.
1. Core Validator (Masternode)
The most critical node type on the network.
- Contributes 10,000,000 XDC
- Validates transactions and produces blocks
- Ensures network uptime, security, and decentralization
- Earns block rewards and incentives for active participation
- Must maintain 100% uptime on dedicated or cloud server infrastructure
- Capped at 108 Core Validator slots
2. Protector Node (New in XDC 3.0)
A brand-new role designed for fault tolerance.
- Contributes 10,000,000 XDC
- Acts as a backup for Core Validators — from the next update, the architecture targets 4 Protector Nodes for every Core Validator (432 Protector slots)
- Enables seamless block production during disruptions — if a Core Validator fails, Protectors keep the network producing blocks without downtime
- Earns proportional rewards from the reward pool based on the number of associated Protector Nodes
- Adds a redundancy layer that meaningfully strengthens network resilience
3. Observer Node (New in XDC 3.0)
The entry point into the validator ecosystem.
- Contributes 10,000,000 XDC
- Non-block-producing — observes consensus and broadcasts transactions
- Ideal for individuals and organizations that want to contribute to decentralization today and move up to Protector or Core Validator roles as slots open
- Receives 50% of the Protector Node reward — passive earning without active consensus duties
- No cap on the number of Observer Nodes
How role assignment works: The 108 Core Validator slots fill first, then the 432 Protector slots. Once Protector capacity is full, new qualifying nodes automatically become Observer Nodes.
Reward Structure Under XDC 3.0
Rewards are calculated from fixed protocol emissions relative to the 10,000,000 XDC self-bond. Reward pools are allocated per epoch and shared among the nodes in each tier — Core Validators earn the highest rate for producing blocks, Protector Nodes earn proportional rewards from their pool, and Observer Nodes receive 50% of the Protector reward rate.
Want the exact percentage-based calculations? Ask an AI assistant like Claude or ChatGPT to calculate the approximate APR for each node role based on the fixed protocol emissions and the 10,000,000 XDC self-bond — they can walk you through the per-epoch and annualized math step by step.
Per-epoch view: An epoch is 900 blocks/rounds (~50 minutes). Reward pools are allocated per epoch and shared among the nodes in each tier — for example, 108 Core Validators sharing the validator pool and the Protector Nodes sharing the protector pool.
How rewards are paid today: Until the next network update — planned around October 2026 — node rewards are distributed from the XDC ecosystem wallet. Once the upgrade goes live on mainnet, reward distribution moves to the new on-protocol mechanism described above.
The Burning Mechanism
Alongside restructured rewards, XDC 3.0 introduces token burning to reduce inflation. A portion of network fees/emissions is permanently removed from circulation, making the reward model economically sustainable long-term rather than purely inflationary.
⚠️ Important: Reward parameters reflect the current proposal and testnet configuration. Final mainnet values are subject to governance approval and may be refined based on audit findings and Apothem results. Always verify against official XDC announcements before making staking decisions.
KYC / KYB Requirements (New Format Drafts)
All node operators must complete identity verification. New draft formats have been published for both individuals and organizations:
- Individual (KYC) — new format draft: KYC Document Format — Individual
- Organization (KYB) — new format draft: KYB Document Format — Organization
Complete the applicable document before (or alongside) your node registration. Each masternode requires its own separate KYC.
How to Set Up a Masternode
Setting up an XDC masternode is straightforward with the official tooling. Provision a reliable dedicated server or cloud VM, then clone the official node repository from github.com/XinFinOrg/XinFin-Node and follow the Docker-based setup guide at xinfin.org/docker-setup — the recommended path for most operators. Once your node is synced, lock your 10,000,000 XDC via the official masternode DApp, submit your KYC/KYB documents, and register your node's coinbase address. From there, keep the node updated and monitored to meet the 100% uptime expectation.
Prefer to test first? Spin up a node on the Apothem Test Network (Chain ID 51) to get familiar with the flow before committing on mainnet (Chain ID 50).
Infrastructure Operators & Trusted Institutions
The network is currently secured by leading infrastructure operators and trusted institutions including: SBI VC Trade (SBI VC Japan), Cumberland (a DRW company), Deutsche Telekom, GSR Markets, HashKey Cloud, Republic, UOB Venture Management, Animoca Brands, Clearpool, RedStone, stakeFi, BCW Group, SettleMint, Bitrue, InvestaX, IXS, Hivemind Capital, Blueprint, CertiK, StorX, NTT DOCOMO GLOBAL, DSRV, and Bridge (a Stripe company).
Third-Party Masternode Services
If you don't have the resources to maintain a masternode yourself, a number of third-party services and community providers offer managed node infrastructure, including: IndSoft, Node Forge, Zeeve, Blockdaemon, Tatum, NOWNodes, Asternodes, Ankr, thirdweb, and Goldsky.
Disclaimer: XDC Network does not officially endorse third-party services. Please perform due diligence before proceeding.
Conclusion
The XDC 3.0 Staking, Rewards & Burning upgrade is more than a reward reshuffle — it's a structural evolution of how the network achieves security, resilience, and decentralization:
- Core Validators keep producing blocks with the strongest incentives
- Protector Nodes add a fault-tolerance layer the network has never had before
- Observer Nodes open a passive on-ramp into the validator ecosystem
- Token burning keeps the economics sustainable
With the upgrade live on Apothem and the audit progressing, mainnet is on the horizon. Whether you're a current masternode operator, an institution evaluating XDC infrastructure, or a community member preparing to participate — now is the time to understand the architecture and get ready.
Questions about node setup, role assignment, or rewards? Drop them in the comments or post on xdc.dev — happy to help.
Discussion (0)