Skip to main content
Get every member of your team ready to build on BOT Chain testnet: a wallet, tBOT, working tools and one contract deployed and verified. Tick each box as you go. Do this before the event if you can. Venue Wi-Fi is slowest in the first hour, when everyone installs tools at once.

Wallet

  • Create a development wallet with cast wallet new uzo-dev, or a fresh MetaMask account. Don’t use a wallet that holds real money.
  • Write down your address (it starts with 0x). Never share the private key or recovery phrase, including with mentors.
  • If you use MetaMask, add BOT Chain testnet by hand: chain ID 968, RPC https://rpc.bohr.life. See Connect a wallet.

tBOT

  • Claim from the BOT Chain faucet: up to 10 tBOT per address per 24 hours.
  • If that doesn’t work, claim 0.1 tBOT from the Uzo Labs faucet, or ask the organizers. Some events pre-fund wallets.
  • Check your balance:
check-balance.sh
0.1 tBOT is enough for the quickstart many times over. It used about 0.004 tBOT in our test.

Toolchain

  • On Windows, open WSL or Git Bash. The Foundry installer needs a Unix shell.
  • Install Git.
  • Install Foundry and check it: forge --version. See Foundry setup.
  • If you’ll build a web app, install Node.js LTS and check node --version.
  • Optional: install the Uzo SDK in your app with npm install @uzolabs/sdk viem. See Installation.
Prefer a browser-only setup? Remix needs no installs, and works with MetaMask.

First deploy

  • Follow the quickstart to deploy Counter to testnet.
  • Verify it on BOTScan with forge verify-contract. The quickstart shows the command.
  • Open your contract at https://scan.bohr.life/address/YOUR_CONTRACT and check the Contract tab shows the source.
  • Call it once with cast send and read the result with cast call.

Team

  • Create one GitHub repo for the team and give everyone access.
  • Agree who owns the deployer wallet. Keep its key in a Foundry keystore (--account) or a local .env file listed in .gitignore. Never commit a key.
  • Read the submission requirements and pick a track.

Stuck?

Check the hackathon FAQ first, then ask a mentor. Bring the exact error message and the command you ran.

Next steps

Example tracks

Pick something to build.

Templates

Start from a working project.
Last modified on October 2, 2026