MSG Chain
Stake MSG, enter Round-Robin + DAR consensus, and join a DAO-governed active validator set. Validator eligibility is determined by stake and DAR qualification, regardless of subject type; AI does not take over validator duties in production today, and signing and deployment still require human approval.
Once you meet the validator stake and uptime requirements (steady-state minimum stake 100,000 MSG, uptime at least 60%), DAR keeps scoring uptime (0-40), stability (0-30), holdings (0-20) and holding duration (0-10). The validator cap defaults to 100 and never drops below 100, and it can be expanded through DAO governance.
Deploy a node, register validator info, enter the governed active set, and keep passing ongoing DAR qualification, slashing, challenge, and recovery checks. A node that only syncs and serves queries can run as a non-validating node without staking.
Validator rewards stay in the validator pool. Settlement is triggered by events such as claim, register, unregister, slashing, and role changes, and it stays tied to DAR qualification checks and the penalty-and-recovery flow.
MSG Chain separates "who produces blocks" from "who governs". Four roles are distinguishable on-chain: non-validating nodes, candidate nodes, validators, and core validators. They differ in admission, quota, duty, and reward source.
| Role | Admission | Quota / Cap | Duty | Reward Source |
|---|---|---|---|---|
| Non-validating node (full / light) | No stake required | Uncapped | Sync blocks, relay transactions, serve RPC and query endpoints | No block or candidate reward |
| Candidate node | Stake 10,000 - 100,000 MSG (14-day unbonding period) | Candidate cap 10,000, expandable by governance | Stand by and keep passing DAR qualification scoring | Candidate pool: scaled by qualified seats over the candidate economic denominator, then split equally per qualified seat |
| Validator | Stake at least 100,000 MSG (steady state) | Active-set cap 100, expandable by governance | Take turns producing blocks, sign consensus, vote in governance | Validator pool: minted at the full base rate and distributed to active validators |
| Core validator | Determined by DAR ranking; not a separate stake tier | max(3, ceil(validators x 0.21)), capped at 100 | Form the governance core chamber; BFT threshold is ceil(core x 2/3) | Same pool as validators |
On this chain, "full node" and "light node" describe a data-retention mode (whether historical blocks are pruned), not an admission role alongside validators. "Non-validating node" is the term used here for a node that syncs and serves queries without producing blocks.
MSG Chain goes live through an official launch announcement once features are validated on local and real public-network nodes; mainnet status flips only upon that announcement. After launch, node software iterates through the decentralized resource market, with each operator deciding its own upgrades under consensus rules.
Disclaimer summary: node upgrades are each operator's own decision and risk; packages are provided "as is" by multiple publishers, without warranty of merchantability, fitness for a particular purpose, or uninterrupted service. Read release notes and verify signature and hash before upgrading; consensus-violating versions are rejected by the network.
See the DAR weights, the validator cap rules that DAO governs, and the qualification requirements.
Governance PageDeploy your node infrastructure and connect networking, monitoring, block cadence, and the settlement runtime.
Developer PageOpen the whitepaper validator modules to see how claim, register, slashing, challenge, restore, and DAR qualification checks relate.
Validator Module Penalty Loop