Validators
Validator readiness
Coming soon
Whether the next epoch boundary admits a validator under Alpenglow's rules, and what each pending feature gate asks of it, signed.
Included in: Recovery, Pro, Operator, Validator Ops (every size) (not on sale yet).
Endpoints
Served from http://186.233.184.235:8080. Send a key as Authorization: Bearer psol_…. Indexes and status files need no key.
/readiness/<vote>.json/readiness/summary.json/readiness/boundary.json/readiness/features.json
curl -fsS -H "Authorization: Bearer psol_…" "http://186.233.184.235:8080/readiness/<vote>.json"Access and limits
readiness: Validator readiness at the next boundary, signed per request with its own key.
| Plan | readiness | Data a month |
|---|---|---|
| Recovery | 5 requests a second, bursts of 20 | 2 TB per key |
| Pro | 10 requests a second, bursts of 40 | 5 TB per key |
| Operator | 20 requests a second, bursts of 50 | 10 TB per key |
| Validator Ops, up to 1.5M SOL not on sale yet | 10 requests a second, bursts of 40 | 2 TB per key |
| Validator Ops, up to 5M SOL not on sale yet | 10 requests a second, bursts of 40 | 5 TB per key |
| Validator Ops, up to 25M SOL not on sale yet | 10 requests a second, bursts of 40 | 10 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.