This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
The developer path for BOT Chain. A typed, viem-native SDK with ready chain configs, verified contract addresses and ABIs, plus docs that take you from zero to a verified contract on testnet. Open source.
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.
No comment highlights available yet. Please check back later!
About Uzo Labs on Product Hunt
“The Infrastructure Layer for BOT Chain”
Uzo Labs was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #85 on the daily leaderboard. The developer path for BOT Chain. A typed, viem-native SDK with ready chain configs, verified contract addresses and ABIs, plus docs that take you from zero to a verified contract on testnet. Open source.
Uzo Labs was featured in Open Source (69k followers), Developer Tools (521.5k followers) and Web3 (7.9k followers) on Product Hunt. Together, these topics include over 119.1k products, making this a competitive space to launch in.
Who hunted Uzo Labs?
Uzo Labs was hunted by Chidile. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Uzo Labs stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Chidile
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.