Hey Product Hunt 👋

I'm Chidile, a software engineer in Lagos.

A few weeks ago, I was building on BOT Chain, an EVM chain, and kept hitting the same walls. It isn't in viem's chain list, so you have to write your own config. Contract addresses are spread across different pages. The public mainnet RPC blocks event queries, which breaks most dashboards and listeners. None of it is hard on its own, but every developer has to rediscover all of it before writing a line of code.

BOT Chain already has the pieces: a fast chain, an explorer, a DEX, and a bridge. What it was missing was a clear path through them. So I built one.

Uzo means road in Igbo. Here's what's live today:

1. @uzolabs/sdk on npm: a typed, viem-native SDK with ready chain configs for mainnet and testnet, verified contract addresses and ABIs, and an explorer client. One install and you're connected.

2. docs.uzolabs.xyz: guides that take you from zero to a verified contract on testnet, plus workarounds for the chain's known gaps.

What's next: DEX and bridge helpers in the SDK, clone-and-deploy starter templates, and a hosted RPC with event queries and WebSockets enabled. Everything is open source on GitHub.

I'd love your help with two things:

1. Try it and tell me what broke or confused you. Bug reports are the best gift today.

2. If you've built on a newer EVM chain, what was the most painful part of getting started?

Thanks for checking it out. I'll be here all day answering questions.