TON Access
The most reliable decentralized RPC network for TON dapps making HTTP queries to blockchain state from the browser. Unrestricted anonymous access without an API key.
No throttling for
anonymous dapp users
Read more
RPC gateways like toncenter throttle anonymous users to 1 request per second. Most dapps cannot operate under these restrictions since their users are anonymous.
Decentralized access without
registering API keys
Read more
RPC gateways like toncenter reduce throttling by registering an API Key. This API Key cannot be stored client-side (secret) and cannot be stored server-side (centralized).
No need to run your own RPC
backend server
Read more
You should never run a server as part of your dapp since servers are centralized. If you suffer devops downtime, your users will lose access to their funds.
Trust a protocol, not a
centralized business
Read more
Dozens of permissionless validators of the Orbs Network staked with $100 million. Your access to TON does not depend on a single centralized business.
Robust API with no single
point of failure
Read more
Operated by the dozens of independent validators of the Orbs Network that are running in mainnet since 2019 with virtually no downtime.
Supports all RPC API flavors
HTTP v2, v4, raw ADNL
Read more
The TON ecosystem has different RPC API flavors, each with its own tradeoffs - HTTP v2 by TonCenter, HTTP v4 by TonHub and raw ADNL. TON Access supports all three.
HTTP API Flavor
TonCenter HTTP API v2 docs
TonHub HTTP API v4 docs
Raw ADNL Proxy docs
Client Library
Network
Mainnet
Testnet
Orbs Network has dozens of independent validators running Proof-of-Stake consensus with over $100 million staked. The network has been running in mainnet since 2019. By routing your dapp RPC requests through Orbs validators, you maintain decentralized access to the chain without relying on a single centralized business.
We created TON Access by learning from the failings of Ethereum. Most EVM dapps access the chain through Infura, a centralized business. By depending on Orbs validators, we can guarantee decentralized access, similar to what pokt.network is doing on EVM.
Registering API keys in web3 always seemed absurd to me. Where are you supposed to store them? Client-side isn’t safe and server-side means running a centralized backend.
We use cookies to ensure that we give you the best experience on our website. By continuing to use our site, you accept our cookie policy.