Docs/Network
Network

Security model

The two-validator topology, RPC boundaries, and custody risks.

Security model

The Beta prioritizes cost and speed over high availability. This is an operational choice, not a decentralization claim.

Single-server topology

Both validators share one physical server. One host failure can stop consensus and every public service. A compromise of the host can expose both validator environments and the service stack. Stopping either validator is expected to stop block finalization.

Gateway boundaries

Public RPC is terminated at the TLS gateway and filtered by method, rate, body size, and connection limits. Validator RPC, QBFT/admin APIs, databases, Graph admin, metrics, and signing material remain internal. No account should be unlocked on a validator or RPC node.

Key and supply risk

The Dev Wallet receives 100% of the native genesis supply. Validator keys and the Dev Wallet are critical custody material and require encrypted offline backups, recovery testing, access logging, and two-person operational approval before a public launch.

Intended use

Do not use the Beta for regulated assets, custody, brokerage, fiat settlement, or funds whose loss cannot be tolerated. The public website and status page intentionally disclose these boundaries.