Skip to main content

Protocols

The Raze Solana RPC relay accepts transactions over three protocols. Choose based on your latency and integration requirements.

Servers


HTTP (JSON-RPC)

Standard HTTP POST with JSON-RPC 2.0. Returns transaction signature or bundle ID. See sendTransaction and sendBundle for full details. Public RPC endpoint: https://rpc.raze.bot/ — CORS-enabled, used by web3.js and browser clients. You can pass a Helius-style API key in the query string: ?apikey=, ?api-key=, or ?api_key= (header wins if both are set). Any other Solana JSON-RPC method (getBalance, getAccountInfo, getLatestBlockhash, etc.) is transparently proxied to a load-balanced upstream pool. The gateway also serves Helius-compatible DAS methods (getAsset, getAssetsByOwner, …) locally from Raze History.

QUIC (Solana TPU)

Native Solana TPU protocol over QUIC. Compatible with solana-tpu-client and any client using ALPN solana-tpu. Fire-and-forget — no response is returned. Connection details:
  • TLS with self-signed certificate (verification skipped by Solana clients)
  • ALPN protocol: solana-tpu
  • Max transaction size: 1232 bytes
  • Open a unidirectional stream, write the raw transaction bytes, close the stream

UDP (Raw Bincode)

Lowest latency option. Send raw bincode-serialized Solana transactions as UDP datagrams. Fire-and-forget — no response, no connection overhead. Details:
  • Max transaction size: 1232 bytes per datagram
  • No handshake, no connection state
  • Processed on a dedicated OS thread with recvmmsg() batch processing (32 packets per syscall)

Tip-based routing

All protocols use the same tip-based routing. The relay extracts tip amounts from transaction instructions (zero-copy, no full deserialization) and forwards accordingly: