Third-Party RPC Providers
As of the current phase, no third-party RPC providers have been announced for OXN. All public RPC traffic runs through the endpoint operated by the OXN team.
Current options
For OXN Testnet, use:
- Official public endpoint:
https://rpc.bout.network - Your own node (once documented): see Running a Read-Only RPC Node
What third-party providers typically offer
When infrastructure providers (Alchemy, Infura, QuickNode, dRPC, and similar) add OXN support, expect the following features:
- Elevated rate limits compared to the free public endpoint
- Historical archive access — full historical state, not just recent
- Additional method support — some providers expose extra
debug_*andtrace_*methods - SLA guarantees with monitoring and support
- Regional endpoints for lower latency
- API keys for usage tracking and billing
When to use a third-party provider
- Your application has commercial requirements for uptime and support.
- You need historical data older than the public endpoint retains.
- You need higher rate limits than the public endpoint allows.
- You want provider-specific features (e.g. archive nodes, MEV protection).
What to watch for
Confidentiality preservation. OXN's encryption is client-side — the RPC provider is on the outside of the encrypted envelope. But a malicious or compromised provider could still see request patterns and metadata. Choose providers whose privacy posture matches your threat model.
No hidden decryption. No third party can decrypt OXN calldata without the caller's session key. If a provider claims to offer "decoded transaction inspection" for OXN, ask carefully — either they're mistaken, or the transactions they're decoding were sent in plain.
Interoperability. Confirm that a provider's endpoint supports OXN-specific features (encrypted call construction, signed queries) — some may support only the standard Ethereum JSON-RPC subset.
Being listed here
If you operate an infrastructure business and want to offer OXN endpoints, contact the team through the Support channels. We list validated providers on this page.
Next steps
- Public RPC Endpoints — the official endpoint
- Running a Read-Only RPC Node — self-hosting