TON coming soon

A TON validator node runs in our fleet, but TON's client API is not a plain HTTP RPC on the node — it requires the ton-http-api bridge (toncenter v2 dialect) speaking ADNL to a liteserver. That bridge is being deployed; the /ton gateway path is reserved and will go live with it.

What to expect

Endpoint	https://rpc.lab.au.ro/ton (reserved)
Protocol	toncenter-style JSON-RPC (getMasterchainInfo, getTransactions, sendBoc, …)
SDK	@ton/ton TonClient with endpoint + apikey header

// the integration that will work on launch:
import { TonClient } from '@ton/ton'
const client = new TonClient({
  endpoint: 'https://rpc.lab.au.ro/ton',
  apiKey: undefined,                 // key rides the gateway header instead:
  httpAdapter: undefined,
})
// (final connection snippet will be published — and live-verified — at launch)

Want it sooner? Tell us — chain priority follows demand.