Planned. This service is not live yet. This page explains what it will do and what to use in the meantime.
Why it’s needed
BOT Chain’s public RPC endpoints work well for reading state and sending transactions. Two things are missing for apps that react to on-chain activity:- Event queries. BOT Chain’s JSON-RPC page documents
eth_getLogsas disabled on the public endpoints. In our tests it answered bounded block ranges, but you can’t rely on a method the operator says is off. - WebSockets. No WebSocket URL is published, so
eth_subscribefor new blocks, logs or pending transactions isn’t available.
What Uzo RPC will do
Uzo RPC is planned as an RPC service for BOT Chain mainnet and testnet that adds:eth_getLogsthat is supported, so event-driven apps and indexers can use it in production.- WebSocket endpoints for
eth_subscribe. - Standard JSON-RPC, so existing tools such as viem, ethers, Foundry and Hardhat work by changing only the URL.
What to use meanwhile
Learn more
Logs and WebSockets
The limitation and every workaround that works today.
Endpoints
The public endpoints to use until Uzo RPC launches.
Uzo Index
The planned event index that builds on a logs-enabled RPC.
Product status
What is live, in development and planned.