Phase 1
Fix the path
Get the basics right so every common tool knows BOT Chain exists.
- SDK chain configs
- Network reference
- viem and Chainlist contributions
Uzo Deploy is on mainnet
The developer path for BOT Chain
Deploy a verified contract from your browser, or add BOT Chain to your viem app with one install. Mainnet is chain 677.
npm i @uzolabs/sdk viem
Verified on BOTScan automaticallyVerify · Step 4 of 4
BOT Chain mainnetchain 677
Products
Five tools. One path to shipped.
One install for BOT Chain. Chains, addresses and ABIs for viem.
@uzolabs/sdk v0.3.0 defines BOT Chain once so you stop copying chain IDs and RPC URLs. It never touches private keys.
- @uzolabs/sdk/chainsAvailable
botChain and botChainTestnet for viem
- @uzolabs/sdk/contractsAvailable
Addresses and typed ABIs
- @uzolabs/sdk/explorerAvailable
A BOTScan client with no API key
- @uzolabs/sdk/bdexAvailable
Quotes and swaps on BDEX
- @uzolabs/sdk/bridgePlanned in 0.4.0
Bridge helpers
- @uzolabs/sdk/paymasterPlanned in 0.5.0
Gasless transactions
import { createPublicClient, http } from 'viem'
import { botChain } from '@uzolabs/sdk/chains'
const client = createPublicClient({
chain: botChain,
transport: http(),
})
// Reads the latest block from BOT Chain mainnet.
const block = await client.getBlockNumber()npm i @uzolabs/sdk viem
From template to verified contract. Four steps, one signature.
On mainnet a deploy costs gas plus a 0.1 BOT fee, shown before you sign. Practice first on testnet with free tBOT.
Configure
Pick Token, NFT Collection or Tip Jar and fill in the form.
Review
See the contract, the network and the cost before anything is sent.
Sign
Approve one transaction in your own wallet. Uzo never holds your keys.
Verify
The source is verified on BOTScan for you, with a link to the contract.
Two networks. Test on one, ship on the other.
Get test tBOTBOT Chain mainnet
Mainnet- Chain ID677
- TokenBOT
- RPCrpc.botchain.ai
- Explorerscan.botchain.ai
BOT Chain testnet
Testnet- Chain ID968
- TokentBOT
- RPCrpc.bohr.life
- Explorerscan.bohr.life
Four phases. Lit squares have shipped.
See the roadmapPhase 2
Build the path
Guides and starters that take a project from an empty folder to a deployed contract.
- Hardhat and Foundry quickstarts
- Contract verification guide
- Starter templates
- Uzo Deploy: browser deploys with automatic verification
Phase 3
Hackathon ready
Templates for the builds people reach for when the clock is running.
- AI agent template
- Paymaster tutorial
- Indexer starter
- Agent Vault in Uzo Deploy
Phase 4
Run the rails
Hosted infrastructure for the gaps public endpoints leave open, like event queries.
- Uzo RPC as a hosted service
- Uzo Index as a hosted service
Questions
Straight answers about cost, keys and what is ready today.
What is Uzo Labs?
An independent project from Lagos that builds developer tools for BOT Chain: an SDK, starter templates, a browser deploy tool and a testnet faucet.
What does a deploy with Uzo Deploy cost?
On mainnet you pay network gas plus a fixed 0.1 BOT fee, both shown before you sign. On testnet you pay in tBOT, which is free from the faucet and has no value.
Does Uzo hold my keys or my contracts?
No. You sign in your own wallet, and Uzo holds no admin keys over anything you deploy.
Are the templates ready for real value?
They are tested, not audited. Read the code and test on testnet before you put real value behind a contract.
Why use the SDK instead of defining the chain myself?
You stop copying chain IDs, RPC URLs and contract addresses between projects, and you get typed ABIs and a BOTScan client in the same install.
Where do I get test tBOT?
From the Uzo Labs faucet or the BOT Chain faucet. Test tokens are for chain 968 only and have no value.