Mainnet performance
RUFF prepares requests concurrently and sends deliveries through two gas wallets in parallel. A request needs at least one later block before fulfillment.
Recorded measurements
Section titled “Recorded measurements”On September 29, 2026, the Arc mainnet launch run submitted 106 requests at rates of 1, 5, and 10 requests per second.
| Measurement | Result |
|---|---|
| Delivered | 106 of 106 |
| Proofs checked | 106 of 106 |
| Callback failures | 0 |
| Median request-to-callback latency across runs | 1.0–1.4 seconds |
| Longest observed latency | 1.77 seconds |
| Typical delivery distance | 2–3 blocks, with 0.5-second blocks |
These observations describe that run. They do not establish sustained throughput at higher loads or a worst-case latency bound. RUFF does not offer a contractual delivery deadline.
Requests and their evidence are available in RUFF Explorer. The verification guide shows how to check a result independently.
What affects delivery time
Section titled “What affects delivery time”Delivery depends on block inclusion, RPC response times, outstanding transactions, and callback gas. A burst can create a queue even when all requests fit within the hub’s pending limits.
WebSocket events wake the scanner; independently checked HTTP reads supply the chain data. A polling fallback detects requests if notifications are missed. The relayers prepare work in parallel, while nonce ordering still applies within each sending wallet.
Cost and capacity
Section titled “Cost and capacity”The default launch fee is 0.01333 USDC for 100,000 callback gas. Proof verification and callback execution are included in that quoted service fee; the caller separately pays the request transaction’s gas.
Use the current tariff and limits when sizing an integration. Measure the consumer’s callback cost and account for stored-result recovery.