Status Roadmap
Docs/Network
Network

Network operations

Consensus parameters, upgrades, maintenance, and recovery.

Network operations

Orbyn is operated as a centrally managed Experimental Mainnet Beta. The operator maintains the two validators, the RPC/archive node, Blockscout, gateway, and observability stack on one physical server.

Consensus behavior

Besu QBFT uses two validators in this Beta configuration. Both validators are required for expected block production. Besu’s four-validator minimum for BFT is not met, so this network must not be described as Byzantine fault tolerant.

Upgrades

There are no automatic protocol upgrades. Planned consensus, EVM, validator-set, fee, or gas-policy changes require two operator approvals, a reproducible configuration diff, private rehearsal, backup verification, a rollback procedure, and a documented maintenance window.

No protocol change is planned during the first 30 days after launch except for security or outage response.

Availability objectives

  • Beta availability target: 99.0% outside scheduled maintenance.
  • Recovery point objective: 24 hours.
  • Recovery time objective: 24 hours.
  • A validator restart should recover operations within 15 minutes after the healthy process returns.

Maintenance and incidents are communicated through the status page.