Solana TPU Sender endpoints
TPU delivery with HTTP JSON-RPC and authorized QUIK client endpoints in Amsterdam, Frankfurt and Washington DC. API keys and connection setup through Supanode Telegram.
// updated 2026-10-23
HTTPS submission
Use the endpoint issued with your API key. The documented HTTPS base is:
https://sfls.l2.p2p.org
Private requests use / or /rpc, an API-key header and a transaction tip. The public route is /public, with its own tip minimum and rate limit. See tips and limits.
Regional endpoints
The following addresses are listed in the current connection documentation:
| Region | HTTP JSON-RPC | QUIK transport (separate authorization) |
|---|---|---|
| Amsterdam | http://ams3.sender.syncro.p2p.org:8080 | ams3.sender.syncro.p2p.org:8090 |
| Frankfurt | http://fra.sender.syncro.p2p.org:8080 | fra.sender.syncro.p2p.org:8090 |
| Washington, DC | http://us.sender.syncro.p2p.org:8080 | us.sender.syncro.p2p.org:8090 |
Request your preferred region and transport from Supanode on Telegram. Our team confirms the address and access enabled for your profile. Prefer the issued HTTPS URL when sending API-key headers; the listed regional HTTP URLs are unencrypted.
The connection guide labels port 8090 as QUIK. This transport requires separate authorization: create a key pair and send only the public key to Supanode. Request the transport-specific integration details from our team. The examples in this documentation use HTTP JSON-RPC.
The p2p.org hostnames are the current service endpoints. Get API keys, connection details and support from Supanode.