Round-Robin Consensus
Validators take turns in order, and DAR role reviews are driven by economic seconds. If the review inputs are missing, the network rejects the action rather than falling back to a fixed block count forever.
MSG Chain
Round-Robin + DAR consensus · On-chain wasm_migrate upgrades · How contract roles are resolved at runtime · Runtime principal authority carries the subject-neutral principle into permissions: they come from role and delegation, not subject type. Signing and deployment in production still require human approval.
Validators take turns in order, and DAR role reviews are driven by economic seconds. If the review inputs are missing, the network rejects the action rather than falling back to a fixed block count forever.
DAR runs continuously and combines a 104/96 hysteresis band with an 86400-economic-second review window, so qualification changes, role review, and scheduling stay in step.
The public pages show the block, transaction, and receipt structure; the whitepaper goes further into failed receipts, on-chain upgrade receipts, and how contract roles are resolved.
Explore consensus boundaries, on-chain upgrade paths, registry and contract-role resolution, and implementation constraints.
Consensus & Review Runtime & RegistryOpen the strict architecture layer to see consensus, wasm_migrate upgrades, reply_on and atomic rollback, and how contract roles are resolved at runtime, all in one place.
Whitepaper Home Knowledge Graph