API Reference

Build on an Open Network

dotOne Smart Chain exposes a standard set of APIs for developers, researchers, and integrators. All public endpoints follow Ethereum-compatible JSON-RPC conventions, making integration straightforward for any EVM-compatible tooling.


RPC Endpoints

Mainnet

Type
Endpoint

HTTPS RPC

https://rpc.dotone.network

WebSocket

wss://ws.dotone.network

Chain ID

505

Testnet

Type
Endpoint

HTTPS RPC

https://testnet-rpc.dotone.network

WebSocket

wss://testnet-ws.dotone.network

Chain ID

5000005


JSON-RPC API

dotOne is fully compatible with the Ethereum JSON-RPC specification. All standard eth_, net_, and web3_ namespaces are supported.

Example — Get Latest Block Number

Request:

curl -X POST https://rpc.dotone.network \
  -H "Content-Type: application/json" \
  --data '{
    "jsonrpc": "2.0",
    "method": "eth_blockNumber",
    "params": [],
    "id": 1
  }'

Response:


Example — Get Transaction by Hash

Request:


Example — Get Wallet Balance

Request:

Response:

Balance is returned in Wei. Divide by 10^18 to convert to DOTO.


WebSocket API

WebSocket connections allow real-time subscriptions to on-chain events without polling.

Connect

Subscribe to New Block Headers

Subscribe to Pending Transactions

Subscribe to Contract Logs


Explorer API

The DotOne Explorer exposes a REST API for querying indexed blockchain data — useful for analytics, dashboards, and monitoring tools.

Base URL: https://explorer.dotone.network/api

Common Endpoints

Get Transaction Details

Get Address Transaction History

Get Token Transfers for Address

Get Block Details

Get Contract ABI


Supported Libraries

DotOne is compatible with all standard EVM development libraries:

Library
Language
Usage

ethers.js

JavaScript / TypeScript

Wallet, contract, provider interactions

web3.js

JavaScript

Full Ethereum API coverage

viem

TypeScript

Modern, type-safe EVM client

web3.py

Python

Backend integrations and scripts

ethers-rs

Rust

High-performance applications

Connect with ethers.js

Connect with web3.py


Rate Limits

Public RPC endpoints are available for development and light usage. For production applications requiring consistent throughput:

  • Use a dedicated node or private RPC endpoint

  • Implement request batching where possible

  • Use WebSocket subscriptions instead of polling for real-time data

  • Cache responses for static or slowly-changing data (e.g. block confirmations)

For high-volume integrations, contact the DotOne team regarding dedicated infrastructure access.


Further Reference

Last updated

Was this helpful?