NETSoon

Docs Run a node

Join a hub

Register a hub or join one with your validator identity through the Hub Registry, then leave, move or release, with the acrux hub commands.

A validator takes part in New Constellation's schedule through a hub: a group of co-located validators registered under a code like FRA. The acrux hub commands send the Hub Registry instructions, signed and paid by your validator identity. Every change takes effect at the next Solana epoch boundary.

Before you start

NeedsWhy
Your validator identity keypair, as a Solana keypair fileit signs the membership; acrux keygen --out key.json writes a new one
SOL on that key, on the cluster you name with --rpcthe membership's rent and the transaction fees; a registration also pays the deposit and fee

All acrux hub commands take:

OptionDefaultMeaning
--identityacrux-key.jsonthe keypair that signs and pays
--rpchttp://127.0.0.1:4990the Solana JSON-RPC to send through
--programABjgHL8TcjxUjx6vfwsVQyvxiXR6pFgMkeESgwK6CbDmthe Hub Registry program id

Each prints the instruction's name and its signature once the transaction is confirmed, join_hub confirmed: <signature>, and waits up to 30 s for that.

  1. Find the hub

    Every registered hub, its location and its members is on /hubs, and from GET /v1/hubs. Join the hub whose members you reach within δlocal = 10 ms ms.

  2. Join

    Terminal
    acrux hub join FRA --identity key.json

    Sends join_hub. Your membership counts from the next epoch. The identity pays the membership's rent.

  3. Wait for the epoch boundary

    From the next epoch your membership is in effect and counts toward the hub's member floor of 4. Check it at GET /v1/registry/members/{identity} or on the hub's page.

  4. Be scheduled

    A hub with at least 4 members and 1 %% of total stake is active, and the proposer schedule draws its windows by stake. Upcoming windows are on GET /v1/schedule.

Register a new hub

Terminal
acrux hub register AMS --latitude 52.31 --longitude 4.76 --identity key.json

Sends register_hub. The code is 3 to 8 capitals A to Z, not yet taken. The latitude and longitude, in degrees, are turned into an ECEF point on the WGS84 ellipsoid at sea level, in whole metres. The registrant pays the deposit, held in the hub account, and the registration fee, a share of the deposit; the values are served by GET /v1/registry/config. The registrant then joins the hub like any member.

A new hub has the registry's inactivity period to gather its 4 members.

Leave

Terminal
acrux hub leave FRA --identity key.json

Sends leave_hub. Your membership ends at the next epoch boundary and the cooldown starts.

Move

Terminal
acrux hub move FRA AMS --identity key.json

Sends move_hub. You are a member of the second hub from the next epoch boundary, and the cooldown starts.

A leave or move is accepted once your membership is in effect, nothing else is pending and your cooldown has ended. The cooldown runs for the registry's cooldown epochs after the change takes effect.

Release a hub

Terminal
acrux hub release AMS --identity key.json

Sends release_hub for a hub that has stayed below its member floor past the inactivity period. Anyone can send it; --identity only pays the fee. The deposit and the account's rent return to the registrant, and the code is free to register again.

When a command is refused

A refused instruction comes back as custom program error: 0x…. The code names the reason, such as 6010 CooldownActive or 6011 HubNotInactive; every code, its name and its message is on Hub Registry.