The Acrux API. Hubs and memberships from the Hub Registry, the schedule preview, transactions, the faucet, Fault Lab runs, measured facts and the spec map, with the error envelope every Acrux service returns.
The API serves what is not the live net itself: the Hub Registry's hubs and members as indexed from Solana, the Algorithm 3 schedule preview for an epoch, transaction lookup, the Acrux Net faucet, Fault Lab runs and their replays, the figures measured on the net, and the map from the paper to the code. The live net is the JSON-RPC gateway and the event stream.
Local
API
http://127.0.0.1:4920
OpenAPI 3.1 document
GET /openapi.json
Every response is JSON. Every failure is the error envelope, with the HTTP status its code carries. Lists are paged: pass cursor and limit (1 to 100, default 24) and follow page.nextCursor until page.hasMore is false.
bash
curl -s http://127.0.0.1:4920/v1/hubs?limit=10
ts
import { createClient } from '@acrux/contract'const api = createClient('http://127.0.0.1:4920')const hubs = await api.hubs({ limit: 10 })
The service's status and the configuration it still lacks. status is ready when every setting is present, waiting while some are missing; missingConfiguration names them.
Every hub in the Hub Registry, active, pending and inactive, with members, stake, proposer stake and what a pending hub still needs. Query: cursor, limit.
The registry's configuration as the program holds it: program ID, cluster, deposit, registration fee, cooldown and inactivity periods, code rules, the active-hub minimums and the current epoch. /hubs/register reads it to show the deposit and the fee before signing.
A validator's membership by its identity: hub, stake, proposer stake, whether it is capped, the epoch it takes effect, a pending move or leave and its cooldown. NOT_FOUND if the identity is in no hub.
The proposer schedule Algorithm 3 draws for an epoch from the registry and a stake snapshot: each hub's share of windows, the regional runs, and every window's hub and proposers. Query: epoch, optional, the next epoch by default. The node computes the same schedule through the same code path. See Proposer schedule.
Whether address can receive a faucet grant now: the policy, the grants left for this key and this IP in the current period, and when the period resets.
Grants address Acrux Net SOL, and 100 AXA and 100 AXB, the demo pool's tokens, in one transfer from the faucet. Body: FaucetRequest. The grant's transactionId follows the transfer through getTransaction; the balance is spendable once it executes.
Code
Cause
FAUCET_LIMIT
this key or this IP has used its grants for the period; retryAfterSeconds says when to try again
CONFIGURATION_REQUIRED
the faucet's amount, limits or period are not configured
Starts a run of scenario on a fresh sandbox cluster, with the scenario's seed or the one given. Body: LabRunRequest. Answers 201 with the run in status queued; follow it on /stream or by reading the run.
Server-sent events: the run's recorded events, then its live ones until it ends. Each message has event set to the event type, id to its sequence, and data to the full envelope. Send Last-Event-ID to resume after a sequence.
The figures measured on Acrux Net: slot pacing, commit spread, attestation arrival relative to blocks and cblock finalization time, each at p50 and p99, and the window handover per hub link with its floor, with the sample size and time of measurement.
The map from the paper to the code: every algorithm line and lemma with the file and function that implements it and the Fault Lab scenario that shows it, the parameters, and every choice the paper left open with Acrux's decision. /spec renders it.
time between the first and last commitment of a slot
commitSpreadUs.p50
integer
yes
median, µs
commitSpreadUs.p99
integer
yes
99th percentile, µs
attestationRelativeToBlockUs
object
yes
when attestations reach validators relative to the block; negative is before
attestationRelativeToBlockUs.p50
integer
yes
median, µs
attestationRelativeToBlockUs.p99
integer
yes
99th percentile, µs
cblockFinalizationUs
object
yes
time from a cblock's first slot to its finalization
cblockFinalizationUs.p50
integer
yes
median, µs
cblockFinalizationUs.p99
integer
yes
99th percentile, µs
handoverUs
map of string to object
yes
window handovers per hub link, keyed like FRA-NYC: p50, p99, the link's floor (50 ms plus the arrival of the second hub's votes for the 60% certificate) and the sample count, in µs