The developer path for BOT Chain.
BOT Chain has the pieces. Uzo is the path. SDKs, templates and infrastructure that take you from zero to shipped.
npm i @uzolabs/sdkThe problem
The pieces are there. The path is not.
Building on BOT Chain today means stitching things together before you write a line of your app.
Scattered setup
Network details are spread across many pages, so every new project starts with a hunt.
No ready configs
Every builder writes their own chain config for viem, ethers, Hardhat and Foundry.
Blocked event queries
eth_getLogsis disabled on the public mainnet RPC, so indexing and event feeds break.
What we're building
Four tools, one path.
Start with configs and templates today. Hosted infrastructure follows once the basics are solid.
Reference
BOT Chain at a glance.
The details you reach for most, in one place. Tap to copy.
Mainnet
- Chain ID
- 677
- RPC
- https://rpc.botchain.ai
- Explorer
- https://scan.botchain.ai
- Native token
- BOT
- Faucet
- None
Testnet
- Chain ID
- 968
- RPC
- https://rpc.bohr.life
- Explorer
- https://scan.bohr.life
- Native token
- tBOT
- Faucet
- Claim tBOT
Quickstart
Connect in minutes.
Pick your tool. Every config below points at real endpoints. Claim test tBOT from the testnet faucet first.
import { defineChain, createPublicClient, http } from 'viem'
export const botChain = defineChain({
id: 677,
name: 'BOT Chain',
nativeCurrency: { name: 'BOT', symbol: 'BOT', decimals: 18 },
rpcUrls: { default: { http: ['https://rpc.botchain.ai'] } },
blockExplorers: { default: { name: 'BOTScan', url: 'https://scan.botchain.ai' } },
contracts: {
multicall3: { address: '0x47FA21f684bBAD707A53a0f9BE59F1422F46C265' },
},
})
const client = createPublicClient({ chain: botChain, transport: http() })
console.log(await client.getBlockNumber())Roadmap
One road, four stretches.
Each phase unlocks the next. No dates we cannot keep.
Phase 1
Fix the path
- SDK chain configs
- Network reference
- viem and Chainlist contributions
Phase 2
Build the path
- Hardhat and Foundry quickstarts
- Contract verification guide
- Starter templates
Phase 3
Hackathon ready
- AI agent template
- Paymaster tutorial
- Indexer starter
Phase 4
Run the rails
- Uzo RPC as a hosted service
- Uzo Index as a hosted service
- 1
Phase 1
Fix the path
- SDK chain configs
- Network reference
- viem and Chainlist contributions
- 2
Phase 2
Build the path
- Hardhat and Foundry quickstarts
- Contract verification guide
- Starter templates
- 3
Phase 3
Hackathon ready
- AI agent template
- Paymaster tutorial
- Indexer starter
- 4
Phase 4
Run the rails
- Uzo RPC as a hosted service
- Uzo Index as a hosted service
Principles
How we walk it.
Ship what works
Snippets and templates should run on BOT Chain as written. If one does not, that is a bug we fix.
Honest status
In progress means in progress. Nothing is called live until you can use it today.
Open by default
Code and configs live in public repos, and gaps are tracked in the open.
BOT Chain first, never BOT Chain only
Built for BOT Chain, on standard EVM tooling, so what you learn carries to any chain.
Get involved
Walk the path with us.
Star the repos, try a template, and tell us where BOT Chain tooling still trips you up.