XDC staked in masternodes right now
XDC staked in masternodes
3.82B XDC
XDC RPC (validator contract balance, block times) · updated 9 min ago
XDC price
$0.02923 -2.08% 24h
CoinGecko · updated 56s ago
What is an XDC masternode?
XDC uses XDPoS 2.0, a delegated proof-of-stake consensus. Masternodes are the servers that produce and confirm blocks. Each one locks at least 10 million XDC as a stake, and in return earns a share of the rewards paid every epoch (xdc.org, xinfin.org). A block is final after three more blocks confirm it, about six seconds.
XDPoS 2.0 replaced the first version of the consensus on 30 September 2024; the XDC Network timeline lists it with every other upgrade since 2017. Masternodes are not only run by individuals: MoneyGram said in October 2026 that it is joining as an institutional validator (see MoneyGram joins XDC as a validator).
Active XDC masternodes
Active masternodes
108
Standby nodes
267
Under penalty
5
Round
29,478,576
| Explorer | |||
|---|---|---|---|
| 1 | xdce79e…ee78d | Active | XDCScan ↗ |
| 2 | xdcbbd2…35cfe | Active | XDCScan ↗ |
| 3 | xdc2f68…a1bd4 | Active | XDCScan ↗ |
| 4 | xdc49d3…6c713 | Active | XDCScan ↗ |
| 5 | xdcb9a3…17708 | Active | XDCScan ↗ |
| 6 | xdc2139…ef80e | Active | XDCScan ↗ |
| 7 | xdc76df…55a05 | Active | XDCScan ↗ |
| 8 | xdc070e…0bfe6 | Active | XDCScan ↗ |
| 9 | xdc5454…8bedc | Active | XDCScan ↗ |
| 10 | xdc83e1…7ee23 | Active | XDCScan ↗ |
| 11 | xdc9200…5b99f | Active | XDCScan ↗ |
| 12 | xdc0002…c9d1f | Active | XDCScan ↗ |
| 13 | xdc2edd…19f06 | Active | XDCScan ↗ |
| 14 | xdc7c0f…fc8c9 | Active | XDCScan ↗ |
| 15 | xdcbb08…d6b00 | Active | XDCScan ↗ |
| 16 | xdc75ea…c5221 | Active | XDCScan ↗ |
| 17 | xdcf480…0442d | Active | XDCScan ↗ |
| 18 | xdc9bbf…51864 | Active | XDCScan ↗ |
| 19 | xdc361f…c5858 | Active | XDCScan ↗ |
| 20 | xdc3495…3d3f3 | Active | XDCScan ↗ |
| 21 | xdc226d…e375b | Active | XDCScan ↗ |
| 22 | xdc249f…41a47 | Active | XDCScan ↗ |
| 23 | xdce8bc…91e32 | Active | XDCScan ↗ |
| 24 | xdc7fca…44a9c | Active | XDCScan ↗ |
| 25 | xdc44d2…d9505 | Active | XDCScan ↗ |
| 26 | xdc2e32…ce18f | Active | XDCScan ↗ |
| 27 | xdc74f2…2b61f | Active | XDCScan ↗ |
| 28 | xdcb570…ac9fa | Active | XDCScan ↗ |
| 29 | xdc2a45…6a992 | Active | XDCScan ↗ |
| 30 | xdcde14…f328c | Active | XDCScan ↗ |
| 31 | xdc370b…40481 | Active | XDCScan ↗ |
| 32 | xdc4288…93ad4 | Active | XDCScan ↗ |
| 33 | xdcfab2…ca299 | Active | XDCScan ↗ |
| 34 | xdcef7c…47447 | Active | XDCScan ↗ |
| 35 | xdca454…c28ae | Active | XDCScan ↗ |
| 36 | xdc695c…d07dd | Active | XDCScan ↗ |
| 37 | xdcc7bf…e9b4b | Active | XDCScan ↗ |
| 38 | xdc3dd2…99480 | Active | XDCScan ↗ |
| 39 | xdc6f35…71eec | Active | XDCScan ↗ |
| 40 | xdceb0f…c6cb7 | Active | XDCScan ↗ |
| 41 | xdcaf3d…3024f | Active | XDCScan ↗ |
| 42 | xdc7b07…ddeb4 | Active | XDCScan ↗ |
| 43 | xdc8eee…74ff2 | Active | XDCScan ↗ |
| 44 | xdce02c…0882e | Active | XDCScan ↗ |
| 45 | xdca6de…9df9c | Active | XDCScan ↗ |
| 46 | xdc6e5b…2753d | Active | XDCScan ↗ |
| 47 | xdca9c2…8ce87 | Active | XDCScan ↗ |
| 48 | xdc618e…12d6a | Active | XDCScan ↗ |
| 49 | xdc58f2…60367 | Active | XDCScan ↗ |
| 50 | xdc9e05…b7739 | Active | XDCScan ↗ |
| 51 | xdcb594…1319a | Active | XDCScan ↗ |
| 52 | xdc4e11…d95d9 | Active | XDCScan ↗ |
| 53 | xdc241f…27c05 | Active | XDCScan ↗ |
| 54 | xdc03d9…6c9ff | Active | XDCScan ↗ |
| 55 | xdc1a7c…f02d4 | Active | XDCScan ↗ |
| 56 | xdca465…dbdb2 | Active | XDCScan ↗ |
| 57 | xdca70b…8eace | Active | XDCScan ↗ |
| 58 | xdca72c…7a962 | Active | XDCScan ↗ |
| 59 | xdc6219…c8418 | Active | XDCScan ↗ |
| 60 | xdc6344…5ab7f | Active | XDCScan ↗ |
| 61 | xdca4f1…c1cc1 | Active | XDCScan ↗ |
| 62 | xdc4584…a0fb8 | Active | XDCScan ↗ |
| 63 | xdc8073…ef7da | Active | XDCScan ↗ |
| 64 | xdcd7a6…98f4a | Active | XDCScan ↗ |
| 65 | xdc5c71…78576 | Active | XDCScan ↗ |
| 66 | xdc2a4b…dde17 | Active | XDCScan ↗ |
| 67 | xdc745a…dfcd5 | Active | XDCScan ↗ |
| 68 | xdca4ae…ff83d | Active | XDCScan ↗ |
| 69 | xdc0fb4…b8322 | Active | XDCScan ↗ |
| 70 | xdc8615…79f1c | Active | XDCScan ↗ |
| 71 | xdc1ffc…96f3e | Active | XDCScan ↗ |
| 72 | xdc0302…8cd57 | Active | XDCScan ↗ |
| 73 | xdc149e…fb0fe | Active | XDCScan ↗ |
| 74 | xdc5ccd…6b89e | Active | XDCScan ↗ |
| 75 | xdc047f…9f470 | Active | XDCScan ↗ |
| 76 | xdc74d3…30c4b | Active | XDCScan ↗ |
| 77 | xdcb169…fb40d | Active | XDCScan ↗ |
| 78 | xdc2a59…9feb2 | Active | XDCScan ↗ |
| 79 | xdc449b…2bc21 | Active | XDCScan ↗ |
| 80 | xdccc82…c3b6c | Active | XDCScan ↗ |
| 81 | xdcd64c…a318e | Active | XDCScan ↗ |
| 82 | xdc7850…c01d5 | Active | XDCScan ↗ |
| 83 | xdc3b8a…38766 | Active | XDCScan ↗ |
| 84 | xdc079d…81fb4 | Active | XDCScan ↗ |
| 85 | xdca43a…1e617 | Active | XDCScan ↗ |
| 86 | xdc0407…09487 | Active | XDCScan ↗ |
| 87 | xdcebf8…f83d3 | Active | XDCScan ↗ |
| 88 | xdca828…c4b5b | Active | XDCScan ↗ |
| 89 | xdc90c8…c2f04 | Active | XDCScan ↗ |
| 90 | xdc0f0c…afeed | Active | XDCScan ↗ |
| 91 | xdc64e2…b4443 | Active | XDCScan ↗ |
| 92 | xdc391f…8658c | Active | XDCScan ↗ |
| 93 | xdcf5e2…49e09 | Active | XDCScan ↗ |
| 94 | xdc825c…fdc93 | Active | XDCScan ↗ |
| 95 | xdce25c…28a54 | Active | XDCScan ↗ |
| 96 | xdc4b70…7b746 | Active | XDCScan ↗ |
| 97 | xdce2bc…75db7 | Active | XDCScan ↗ |
| 98 | xdc609c…9f819 | Active | XDCScan ↗ |
| 99 | xdce865…94b21 | Active | XDCScan ↗ |
| 100 | xdc25c6…2eaff | Active | XDCScan ↗ |
| 101 | xdce494…4a8a7 | Active | XDCScan ↗ |
| 102 | xdcccab…08a2c | Active | XDCScan ↗ |
| 103 | xdcb38a…60b6a | Active | XDCScan ↗ |
| 104 | xdce8e8…8729d | Active | XDCScan ↗ |
| 105 | xdc2d74…9e821 | Active | XDCScan ↗ |
| 106 | xdc92d3…4d2c8 | Active | XDCScan ↗ |
| 107 | xdc9043…2763f | Active | XDCScan ↗ |
| 108 | xdcc67c…196ab | Active | XDCScan ↗ |
XDC RPC (XDPoS) · updated 8 min ago
XDC masternode requirements
- Stake: a minimum of 10 million XDC per node, with no upper limit, locked in the masternode wallet. KYC is required.
- Server: a 6-core CPU, at least 16 GB of RAM, at least 1 TB of SSD or NVMe storage and a stable 1 Gbps connection; Ubuntu 22.04 LTS recommended. The server needs a public IP without NAT.
- Uptime: core validators must stay online; nodes that stop signing are temporarily excluded.
Node tiers and masternode rewards
Core validators
108 masternodes that validate blocks and reach consensus. Their owners are paid 4,500 XDC per epoch in total on chain (xinfin.org's illustrative figure is 6,000).
Protector nodes
Up to 432 nodes that add redundancy and fault tolerance.
Observer nodes
Further nodes that observe consensus and relay transactions. They receive half the protector reward.
An epoch is 900 blocks; how long that takes depends on the block time, measured live on the masternode calculator. According to xinfin.org, protector and observer rewards are currently paid from the XDC Ecosystem Reward Wallet; moving them fully on-chain is planned for a future network upgrade, subject to testing and governance. To see what a core masternode owner address actually received in each epoch, measured from the chain, use masternode rewards by address.
The XDC documentation describes a different, work-in-progress reward proposal (docs.xdc.network, rewards mechanism). Until it is adopted, the figures above from xinfin.org describe the current model.
How much does an XDC masternode earn? A worked example
On chain, masternode owners are paid 4,500 XDC per epoch in total, about 41.7 XDC per masternode per epoch (measured by our masternode rewards checker). xinfin.org gives a pool of 6,000 XDC per epoch for 108 core validators, which it labels illustrative (xinfin.org); we show it only for comparison. The yearly rate then depends on how many 900-block epochs fit in a year, which depends on the block time. Measured from the chain right now:
Core validator APR (live estimate)
3.0%
XDC RPC (validator contract balance, block times) · updated 9 min ago
One epoch (900 blocks) right now
73 min
XDC RPC (validator contract balance, block times) · updated 9 min ago
Epochs per day right now
19.9
XDC RPC (validator contract balance, block times) · updated 9 min ago
What the example leaves out
The rate is arithmetic on published figures, not a promise: xinfin.org says its numbers are indicative and based on past performance. Real earnings are lower if the node misses epochs, the reward rules can change by network upgrade, and server costs and the XDC price change what the rewards are worth to you. Try your own numbers in the calculator below.
XDC masternode rewards calculator
| XDC | USD | |
|---|---|---|
| Stake required | 10,000,000 XDC | $292.35K |
| Rewards per month | 25,000 XDC | $731 |
| After server cost | Not applicable | $671 |
| Rewards per year | 300,000 XDC | $8.77K |
Core validator rate measured on chain: owners were paid about 41.8 XDC per masternode per epoch (the usual payout over the last 7 days, see the masternode rewards checker), and at the measured block time of 4.83s one 900-block epoch takes about 73 minutes. xinfin.org's illustrative figure of 6,000 XDC per epoch for 108 validators would give about 4.0%. Protector and observer rates are community estimates (xdc.dev). Checked 2026-10-02. Real rewards depend on uptime, the reward model in force and the XDC price. Not financial advice.
CoinGecko · updated 56s ago
Masternode, standby node or staking provider?
Run your own masternode
For holders of at least 10 million XDC who can run a server around the clock. You keep full control and earn the full node reward, but you carry the uptime risk and the server cost (xinfin.org).
Protector and observer nodes
Nodes outside the 108 core validators can serve as protector or observer nodes, which xinfin.org rewards at a lower rate (see the tiers above). They add redundancy and can move into the core set when places open.
Stake through a provider
For smaller amounts. A provider pools XDC from many holders into masternodes and passes on part of the reward after its fee. You give up some control and depend on the provider. Options and their terms are on our staking page.
How to set up an XDC masternode
- Hold at least 10 million XDC in a wallet you control.
- Prepare a server that meets the requirements above, with a public IP.
- Install and sync the node using the official guides: setting up an XDC masternode and the masternode setup in the XDC docs.
- Complete KYC and register the node with the stake locked in the masternode wallet, as described in the XDC docs.
- Monitor uptime: a node that signs no block in an epoch is excluded for the next four epochs.
Every step in detail, with the server requirements, the commands and how a full node differs from a masternode, is in our guide how to run an XDC node or masternode.
Help is available on the xdc.dev developer forum. Not ready for 10 million XDC? See the other options on our staking page.
XDC masternode risks
Downtime
A masternode that signs no block during an entire epoch is excluded from block production for the next four epochs and earns nothing in that time. Nodes that keep underperforming are removed from the active list (XDC docs, slashing).
Misbehaviour
Provable misbehaviour can be detected by XDC 2.0's forensic system and penalised (xdc.org).
Price and lock-up
Rewards are paid in XDC, so their value moves with the price, and the stake stays locked while the node runs. The official docs do not state an unbonding period; staking providers such as Kiln state about 30 days after resigning.
Scams
No one legitimate will ask for your wallet's recovery phrase to “set up” a masternode, and no one can guarantee a return. More in the safety center.
XDC masternode FAQ
At least 10 million XDC per node, with no upper limit, plus KYC. Source: xinfin.org.
Yes. XDC uses XDPoS 2.0, a delegated proof-of-stake consensus in which masternodes that stake at least 10 million XDC produce and confirm blocks.
Yes: by running a masternode with at least 10 million XDC, or with smaller amounts through a staking provider. See XDC staking.
The live rate for core validators is shown above, worked out from what the chain actually paid per masternode over the last 7 days and the block time measured from the chain, before costs. xinfin.org's illustrative figure of 6,000 XDC per epoch would give a higher rate.
Yes. The XDC documentation says masternodes must complete a KYC process and stake 10 million XDC.
A masternode that signs no block during an epoch is excluded from block production for the next four epochs and earns no rewards in that time. Nodes that keep underperforming are removed from the active set. Source: XDC docs, slashing.
The stake can be penalised for provable misbehaviour detected by the network's forensic system. Downtime alone leads to temporary exclusion and lost rewards, not loss of stake. Source: xdc.org.
The official docs do not state an unbonding period. Staking providers such as Kiln state about 30 days after resigning.