QUIC
Blocksprint provides QUIC endpoints on port 10000 for ultra-low-latency transaction sending. Choose the endpoint closest to your application.
Endpoints
| Region | Endpoint | Provider |
|---|---|---|
| Frankfurt | fra.blocksprint.io:10000 | Teraswitch |
| Frankfurt 2 | fra2.blocksprint.io:10000 | Vultr |
| Frankfurt 3 | fra3.blocksprint.io:10000 | Cherry Servers |
| Amsterdam | ams.blocksprint.io:10000 | Cherry Servers |
| Amsterdam 2 | ams2.blocksprint.io:10000 | Teraswitch |
| Amsterdam 3 | ams3.blocksprint.io:10000 | Vultr |
| New York | nyc.blocksprint.io:10000 | Teraswitch |
| Singapore | sgp.blocksprint.io:10000 | Teraswitch |
| Tokyo | jp.blocksprint.io:10000 | Teraswitch |
| London | lon.blocksprint.io:10000 | Teraswitch |
INFO
Frankfurt and Amsterdam each have three servers. If your application runs in or near Frankfurt or Amsterdam, always send each transaction to all three servers in that region (fra, fra2 and fra3, or ams, ams2 and ams3), with a different nonce for each server.
Connection Details
| Setting | Value |
|---|---|
| Protocol | QUIC (UDP) |
| Port | 10000 |
| ALPN | solana-tpu |
| TLS | 1.3 (required) |
| Authentication | Client certificate derived from API key |
| Transactions | One signed transaction per unidirectional stream, as raw wire bytes |
| Max transaction size | Legacy and v0: 1,232 bytes. Transaction V1: 4,096 bytes. |
| Rejected API key | Connection closed with code 1 (unauthorized) or 3 (key expired) |
The client certificate is a self-signed certificate for an Ed25519 key whose 32-byte seed is the SHA-256 hash of your API key. The Rust and Go examples show how to create it.
INFO
QUIC uses the same tip and rate-limit rules as HTTP: every transaction needs a tip of at least 0.001 SOL to one of the tip addresses. Nothing is sent back for a transaction, so track the signature on your own Solana RPC. If a transaction does not land, check your API key, tip and rate limit, or contact support with the signature.
For Transaction V1, finish each stream after writing the transaction and serialize it with a V1-capable SDK (in Rust, wincode rather than bincode).
Custom Servers
We offer custom servers with custom providers at no additional cost. Contact us on Discord.