The registered development topology contains four clusters of ten operator identities and a 7-of-10 bitmap multisig design. The public RPC is currently stale, so this page does not claim current participation, admission, rewards, or operator openings. The 100-cluster mainnet topology remains a target.
The target is a 10-member cluster with independent ML-DSA-65 operator keys and a 7-of-10 certificate. Public onboarding requires an advancing network and published admission contract.
RPC, archive, oracle, and GPU markets need explicit proofs, prices, and payment contracts. This page does not claim current service revenue.
An advancing head, consistent peer health, reproducible cadence, and current public status precede operator recruitment or economic promises.
The v0.4.0 registry describes four clusters × ten operator identities plus two relays. Repeated RPC checks on 16 July 2026 did not advance beyond height 74,907, latest timestamp 8 July. Registry membership does not prove that an operator is online or signing.
Do not send a bond, rely on a reward estimate, or follow an unsolicited onboarding request. A future opening must publish current network health, exact software and hardware requirements, signed artifacts, economic parameters, and a versioned admission path.
Any released downtime rule needs a versioned evidence format, grace period, and appeal posture. Historical design values are not current bond terms.
A future slashing path must verify conflicting signatures against the same round and identity. Exact penalties require activated state and published parameters.
The SLH-DSA backup and in-protocol rotation were removed. A break-day response is a time-bounded freeze plus coordinated hard fork; future crypto agility requires a new genesis and independent review.
Any 1:1 community-cluster handoff needs an activated roster, signed transition evidence, and an advancing network. It is not current policy merely because it appears in a roadmap.
A ratchet is meaningful only if its exact state transition is released and independently testable. No current threshold is asserted here.
Foundation reward burns require finalized reward state and public transactions. This page makes no current or mainnet reward promise.
A released roster should identify organizational control and conflicts. Explorer labels are useful display data, not a substitute for protocol evidence.