Client Lab
Alpenglow readiness
LiveTestnet
Mainnet's Alpenglow certificates, votes and aggregates plus edge cases, each with the reference outcome, as signed vector sets for your client's CI; a scored conformance check; and per-slot vote latency and credits attribution for a validator.
Included in: Validator Ops (every size), Client Lab.
Each vector set, check report and attribution is signed by the service’s own key, listed in /attest/keys.json.
Endpoints
Served from http://186.233.184.235:8080. Send a key as Authorization: Bearer psol_…. Indexes and status files need no key.
/alpenglow-readiness/vectors/index.json/alpenglow-readiness/vectors/<set>.tar/alpenglow-readiness/vectors/<set>/manifest.json/alpenglow-readiness/vectors/<set>/statement.jsonPOST /alpenglow-readiness/check/alpenglow-readiness/validators/<vote>.json
curl -fsS -H "Authorization: Bearer psol_…" "http://186.233.184.235:8080/alpenglow-readiness/vectors/index.json"
curl -fsS -H "Authorization: Bearer psol_…" -H "Content-Type: application/json" --data-binary @results.json "http://186.233.184.235:8080/alpenglow-readiness/check"
curl -fsS -H "Authorization: Bearer psol_…" "http://186.233.184.235:8080/alpenglow-readiness/validators/<vote>.json?slots=0"Testnet
Free without a key under http://186.233.184.235:8080/testnet; testnet never counts against a plan or mainnet’s free tier. On its gated paths a key sent anyway is checked and served at testnet’s free limits, never charged; an unknown or revoked key gets 401.
/testnet/alpenglow-readiness/vectors/index.jsontn_data/testnet/alpenglow-readiness/vectors/<set>.tartn_data/testnet/alpenglow-readiness/vectors/<set>/manifest.jsontn_data/testnet/alpenglow-readiness/vectors/<set>/statement.jsontn_data/testnet/alpenglow-readiness/validators/<vote>.jsontn_data
tn_data(Testnet views and planners): 5 requests a second, bursts of 10; 2 connections per address, without a key- Its testnet statements are signed by testnet keys, listed in
/testnet/attest/keys.json; never check them against mainnet’s/attest/keys.json.
Access and limits
alpenglow_lab: Alpenglow readiness for client teams: the signed vector sets (index, bundles, manifests, raw bytes) and the conformance check (POST, up to 4 MiB, scored and signed per request).alpenglow_attrib: Participation and latency attribution for one vote account over up to 20,000 slots of participation.db, signed per request with the service's own key.
| Plan | alpenglow_lab | alpenglow_attrib | Data a month |
|---|---|---|---|
| Validator Ops, up to 1.5M SOL | Not included | 1 requests a second, bursts of 5; 3,000 requests a month per key | 2 TB per key |
| Validator Ops, up to 5M SOL | Not included | 1 requests a second, bursts of 5; 10,000 requests a month per key | 5 TB per key |
| Validator Ops, up to 25M SOL | Not included | 2 requests a second, bursts of 10; 30,000 requests a month per key | 10 TB per key |
| Client Lab | 2 requests a second, bursts of 10; 1 Gbps per connection; 20,000 requests a month per key | 1 requests a second, bursts of 5; 10,000 requests a month per key | 5 TB per key |
Limits apply to each key; the free tier’s apply to each address. Prices for each plan are on the plans page.