Wallet and tBOT
The faucet says I already claimed, or the robot check won't load
The faucet says I already claimed, or the robot check won't load
The BOT Chain faucet gives up to 10 tBOT per address per 24 hours. Use the Uzo Labs faucet (0.1 tBOT per wallet per 24 hours), ask a teammate to send you some, or ask the organizers. See Get testnet tokens.
insufficient funds for gas
insufficient funds for gas
The wallet sending the transaction has no tBOT. Check with
cast balance --ether YOUR_ADDRESS --rpc-url https://rpc.bohr.life. Make sure the address you funded is the same one your tool signs with: cast wallet address --account uzo-dev.MetaMask warns that chain 968 belongs to another network
MetaMask warns that chain 968 belongs to another network
In public chain lists, 968 is registered to a different network. Add BOT Chain testnet by hand with RPC
https://rpc.bohr.life and symbol tBOT. See Connect a wallet.I need testnet USDT
I need testnet USDT
Claim Test USDT from the BOT Chain faucet, or swap tBOT for it on BDEX V2. It has 6 decimals, not 18.
Deploying
invalid opcode, or the deploy reverts with no reason
invalid opcode, or the deploy reverts with no reason
Your compiler targeted an EVM upgrade BOT Chain doesn’t support. Set
evm_version = "cancun" in foundry.toml (or evmVersion: "cancun" in Hardhat), clean and rebuild. See Supported EIPs.forge create prints a transaction but nothing is deployed
forge create prints a transaction but nothing is deployed
Add
--broadcast. Without it Foundry only simulates.Transaction underpriced or stuck
Transaction underpriced or stuck
Testnet accepted 20 gwei as the minimum gas price in our tests. Most tools pick this up automatically. If yours doesn’t, pass
--gas-price 20gwei to cast send or forge create. See Gas and fees.Foundry install fails on Windows
Foundry install fails on Windows
The installer needs a Unix shell. Use WSL or Git Bash, not PowerShell or Command Prompt.
Verifying
Verification fails or says the bytecode doesn't match
Verification fails or says the bytecode doesn't match
Use the deployed address, not the transaction hash. Use the same compiler version, optimizer settings and EVM version you deployed with. If it’s too soon after deploying, wait 20 seconds and retry.
It says the contract is already verified
It says the contract is already verified
That’s fine. BOTScan verifies contracts automatically when their bytecode matches one that’s already verified.
Frontend and data
My WebSocket connection fails
My WebSocket connection fails
BOT Chain has no public WebSocket endpoint. Use an
http transport and poll. See Logs and WebSockets.eth_getLogs times out
eth_getLogs times out
Query a bounded range, a few thousand blocks at a time, not from block 0. Or read decoded logs from the BOTScan API.
viem says the chain is not defined
viem says the chain is not defined
BOT Chain isn’t in viem’s built-in chain list. Import
botChainTestnet from @uzolabs/sdk/chains or define it with defineChain.Rules and security
Can we deploy to mainnet?
Can we deploy to mainnet?
Build and judge on testnet. Mainnet uses real BOT and gains you nothing at a hackathon unless your event’s rules ask for it.
Someone asked for my private key or recovery phrase
Someone asked for my private key or recovery phrase
Don’t share it, with anyone. Mentors and organizers never need it. To get help with a transaction, share the address or transaction hash instead.
Can we use code we wrote before the event?
Can we use code we wrote before the event?
It depends on your event’s rules. Ask the organizers, and say in your README what you built during the event.
Next steps
Day-one checklist
Make sure the basics are done.
Known limitations
Every gap in BOT Chain’s public infrastructure.