Products
Configs and templates come first because they unblock you today. Hosted infrastructure follows once the basics are solid.
Chain configs, contract addresses and typed helpers for viem and ethers.
One install gives your app the BOT Chain network definitions it needs, so you stop copying chain IDs and RPC URLs between projects.
npm i @uzolabs/sdkClone-and-deploy starters: token, NFT, DEX, bridge, gasless app, AI agent.
Starter repos that deploy to BOT Chain testnet as written, with the network config, scripts and a small frontend already wired up.
RPC with eth_getLogs and WebSockets enabled.
The public mainnet RPC disables eth_getLogs, which breaks event feeds and indexers. Uzo RPC is planned to fill that gap.
eth_getLogs enabledHosted indexing, no node required.
Query contract events and history over an API instead of running and syncing your own node and indexer.
The problem
Building on BOT Chain today means stitching things together before you write a line of your app.
Network details are spread across many pages, so every new project starts with a hunt.
Every builder writes their own chain config for viem, ethers, Hardhat and Foundry.
eth_getLogs is disabled on the public mainnet RPC, so indexing and event feeds break.
Get involved
Star the repos, try a template, and tell us where BOT Chain tooling still trips you up.