English
JSON-RPC Endpoint
This page covers connecting a wallet or client directly to DotOne Smart Chain. For the full JSON-RPC method list, WebSocket subscriptions, and Explorer API, see the API Reference.
Add DotOne to Your Wallet
Most EVM wallets (MetaMask, Rabby, Trust Wallet, ...) support adding a custom network manually. Use the following parameters:
| Field | Mainnet |
|---|---|
| Network Name | DotOne Smart Chain |
| RPC URL | https://rpc.dotone.network |
| Chain ID | 505 |
| Currency Symbol | DOTO |
| Block Explorer | https://dotscan.one |
A public Testnet is in development and coming soon — its network parameters will be published here once available. Double-check the Chain ID and RPC URL against the API Reference before adding funds or deploying contracts.
RPC Endpoints
| Network | Type | Endpoint |
|---|---|---|
| Mainnet | HTTPS RPC | https://rpc.dotone.network |
| Mainnet | WebSocket | wss://ws.dotone.network |
| Testnet | — | Coming soon — in development |
These public endpoints are shared, so they're fine for development and light use, but not for anything running in production. If you're building something serious, run your own node or use a third-party RPC provider that supports custom EVM chains, and batch your requests and use WebSocket subscriptions instead of polling — see Rate Limits in the API Reference.
Starting a Local JSON-RPC Session
Once you're running your own node (see Node Operators), you can attach to its JSON-RPC console the same way you would on any Geth-based chain:
bash
geth attach http://127.0.0.1:8545From the console, standard eth_, net_, and web3_ namespace calls behave as documented in the API Reference.
Compatibility Notes
A few things worth knowing if you're coming from Ethereum tooling. DotOne runs Proof of Staked Authority, not Proof of Work, so mining-related calls like eth_mining and eth_hashrate don't really apply here. Finality comes from validator voting rather than the probabilistic confirmation-depth model you're used to on Ethereum — see Validator Overview for how block production and finality actually work. And if you're calling eth_getLogs or anything else that scans logs across a wide block range, expect it to be slow on the public endpoints — a WebSocket log subscription or the Explorer/indexer API will serve you better for historical queries.