Bolt Endpoints & Configs

Regional endpoints and configuration for Raiden Bolt

All regions run on dedicated bare-metal infrastructure optimized for minimum validator latency.

HTTP Endpoints

Both HTTPS (443) and HTTP (80) are supported on all endpoints.

sendTransaction (JSON-RPC)

Region	Location	Endpoint
FRA	Frankfurt	`http://fra.bolt.raiden.wtf/api/v1/sendTransaction`
AMS	Amsterdam	`http://ams.bolt.raiden.wtf/api/v1/sendTransaction`
LON	London	`http://lnd.bolt.raiden.wtf/api/v1/sendTransaction`
NYC	New York	`http://nyc.bolt.raiden.wtf/api/v1/sendTransaction`
TKY	Tokyo	`http://tky.bolt.raiden.wtf/api/v1/sendTransaction`

sendRawTransaction (Binary)

Region	Location	Endpoint
FRA	Frankfurt	`http://fra.bolt.raiden.wtf/api/v1/sendRawTransaction`
AMS	Amsterdam	`http://ams.bolt.raiden.wtf/api/v1/sendRawTransaction`
LON	London	`http://lnd.bolt.raiden.wtf/api/v1/sendRawTransaction`
NYC	New York	`http://nyc.bolt.raiden.wtf/api/v1/sendRawTransaction`
TKY	Tokyo	`http://tky.bolt.raiden.wtf/api/v1/sendRawTransaction`

QUIC Endpoints

Region	Location	Endpoint
FRA	Frankfurt	`fra.bolt.raiden.wtf:4433` (UDP)
AMS	Amsterdam	`ams.bolt.raiden.wtf:4433` (UDP)
LON	London	`lnd.bolt.raiden.wtf:4433` (UDP)
NYC	New York	`nyc.bolt.raiden.wtf:4433` (UDP)
TYK	Tokyo	`tky.bolt.raiden.wtf:4433` (UDP)

QUIC uses the same hostname as HTTP — just a different port (4433/UDP). QUIC access is currently on-demand only — contact the Raiden team to enable it.