0block docs

Introduction

0block is a latency-optimized Solana transaction landing service with stake-weighted QoS and same-slot inclusion.

0block is a latency-optimized Solana landing service built by NYX Labs. It provides a lightweight API for submitting transactions directly to Solana's network with sub-millisecond routing, stake-weighted QoS (SWQoS), and automatic prioritization through 0-block inclusion.

Who it's for

  • Trading engines and bots that require fast, reliable transaction landing
  • Infrastructure providers that want to bypass congested public RPCs
  • Developers testing or deploying custom Solana workflows

How it works

0block is a submission egress — a JSON-RPC gate that sits in front of a staked upstream. On every inbound sendTransaction it:

Verifies a tip

It confirms a tip instruction is present — a SystemProgram transfer to an allowlisted 0block tip account, at or above the minimum (0.001 SOL). Transactions without a qualifying tip are rejected.

Forwards to a staked upstream

The raw transaction is forwarded verbatim to a staked validator/RPC, so it lands with prioritized routing and higher inclusion probability.

Relays the response

The upstream JSON-RPC response is relayed back to you unchanged.

A 2xx / result from 0block means your transaction was accepted for forwarding (submission-acked) — not that it landed or was confirmed. On Solana, a transaction that reverts rolls back its tip while still burning fees, so tip presence is never proof of payment. Always confirm landing against a separate trusted RPC. See Tracking your transactions for the full status lifecycle.

Next steps