@uzolabs/sdk/chains.
Early release. This is published in
@uzolabs/sdk 0.2.0 on npm and you can use it today. The API may change before 1.0, so pin the version.The two chain objects
Both are viem
Chain objects built with defineChain. You can use them anywhere viem or wagmi asks for a chain.
Why use them
A chain object is only a few lines, but they’re easy to get wrong. The SDK’s objects include two values that hand-written versions often miss:- The Multicall3 address. BOT Chain’s Multicall3 is at
0x47FA21f684bBAD707A53a0f9BE59F1422F46C265on both networks. The standard address that many tools assume has no code on testnet. With the SDK’s chain objects, viem’smulticalland wagmi’suseReadContractswork without any extra setup. - The explorer API URL.
blockExplorers.default.apiUrlpoints at BOTScan’s v2 API, which the explorer client uses.
How to use them
clients.ts
getAddresses(chain.id).
To use your own RPC endpoint, pass it to the transport: http("https://your-rpc.example"). The chain object stays the same.
Next steps
botChain
Every field of the mainnet object.
botChainTestnet
Every field of the testnet object.
Use with wagmi
Add both networks to a React app.
Network details
RPCs, faucet and limits.