For validators and node operators
Propose in every slot, from a hub.
Under New Constellation a validator proposes as one of 3 co-located proposers of its hub, within 10 ms of the others, for windows of 16 slots.
What changes for a validator
- Hubs
- Validators register their location and join a hub: a group within δlocal = 10 ms of each other, named by airport code. A hub becomes active with 4 members and 1% of total stake.
- Proposer stake
- Each member’s stake is capped so no member holds more than 1/k of its hub. Windows go to hubs by hub stake with probability α = 0.5, uniformly otherwise.
- Co-location
- The 20 ms commit exchange (2δlocal) only holds between nodes that are close. A proposer whose commitment misses it is marked late and its block is dropped from the slot.
- Every slot
- Build and encrypt a block for 50 ms, commit, attest with the key, then validate, merge and execute like every other validator. Votes go to cblocks of 4 slots.
Run it
- 01
Run Acrux Net on one machine
Acrux Net, or a local cluster of 12 validators in Frankfurt, New York, Tokyo: four per hub, with the distances between them on the wire, three proposers drawn per window.
Read the guideacrux net up - 02
Follow Acrux Net and check it
Your node loads the latest finalized cblock’s state, then re-executes every finalized slot on its own SVM: it checks each attestation, decrypts the agreed blocks with the released keys, merges them and compares its state hash with the net’s and the certificate. One line per slot.
Read the guideacrux node follow http://127.0.0.1:4930 - 03
Join a hub
Membership is a Solana transaction signed by the validator identity. It takes effect at the next epoch boundary.
Register or joinacrux hub join FRA --identity key.json
Telemetry
Every node serves Prometheus metrics on its metrics port. Each metric, its labels and what it measures are in Telemetry and metrics.
Registry: hub_registry · register_hub, join_hub, leave_hub, move_hub, release_hub, sweep_fees