Docs Start
Endpoints and limits
The public Acrux Net endpoints, JSON-RPC, the event stream, the API and the site, with their rate limits, the faucet and Fault Lab allowances.
Acrux Net is served at four addresses. Every example in these docs uses them.
| Service | Address | Reference |
|---|---|---|
| JSON-RPC gateway | https://rpc.acrux.computer, and wss://rpc.acrux.computer for Solana's subscriptions | JSON-RPC, Solana PubSub |
| Event stream | wss://events.acrux.computer | Event stream |
| API: hubs, schedule, faucet, Fault Lab, facts | https://api.acrux.computer | HTTP API |
| Site: explorer, sends, Fault Lab, hubs | https://acrux.computer |
The same JSON-RPC answers Solana's methods, so web3.js, Anchor clients and the solana CLI point at https://rpc.acrux.computer (Solana programs and tools). The Hub Registry runs on Acrux, through this RPC, and on Solana mainnet, through any Solana RPC (Hub Registry program).
import { connect } from '@acrux/sdk'
export const acrux = connect('https://rpc.acrux.computer')Rate limits
Counted per client IP address.
| What | Limit |
|---|---|
| JSON-RPC reads | 50 a second, bursts of 100 |
submitTransaction, submitFragment and Solana's sendTransaction | 50 a second, bursts of 500 |
Simulation: simulateTransaction and sendTransaction's preflight | 4,000,000 compute units a second, bursts of twice that |
| Event-stream and Solana PubSub connections open at once | 8, within a cap across every client |
| Fault Lab runs | 6 an hour; at most 10 runs waiting or running across the net |
POST /v1/solana-rpc | the site's own pages only; 300 reads and 20 sends a minute |
Past a limit, the gateway answers HTTP 429 with JSON-RPC error -32005 and data.error.code RATE_LIMITED, and closes a stream connection past the limit as soon as it opens, with close code 1013 and reason RATE_LIMITED. The API answers 429 RATE_LIMITED with retryAfterSeconds. Every refusal carries the error envelope.
Faucet
POST /v1/faucet funds an Acrux Net address for sending and swapping on the net; /faucet on the site does the same for any address you paste, a wallet's included. A wallet joins Acrux Net through its custom RPC setting: Add Acrux network.
| A grant | 2 test ACRUX, 100 AXA and 100 AXB, the demo pool's two tokens, in one transfer |
| Per key | 3 grants every 24 hours |
| Per IP | 10 grants every 24 hours |
A grant past either count is refused with FAUCET_LIMIT and retryAfterSeconds. GET /v1/faucet/{address} shows the grants an address has left.
Browser requests
The JSON-RPC gateway, its WebSocket and the event stream serve browser requests from every origin, as Solana's public RPCs do, so a wallet or a dapp on its own domain calls them from the browser. The API serves browser requests from https://acrux.computer only, and refuses another origin with 403 ORIGIN_NOT_ALLOWED; an app calls the API, the faucet included, from its server. A request without an Origin header is served from anywhere: a server, a script, the CLI, or the SDK on Node.
Health
| Address | Answers |
|---|---|
GET https://rpc.acrux.computer/health | the gateway: status ready once a window is producing and its state is being written, its contract version, and chainState |
GET https://api.acrux.computer/health | the API: status ready when the net is, its contract version, and in missingConfiguration anything it has not read yet |
Your own net
acrux net up runs the same net on your own machine (Run a local cluster), with its gateway on http://127.0.0.1:4930 and its stream on ws://127.0.0.1:4931; its limits are yours to set (Configuration).