QuaiForge is now Klasp. 🩵
Same non-custodial checkout. Same live @QuaiNetwork + @blippay integration. But built from day one to work across every chain, not just one.
New name, new look — same commitment: no code, no custody, ever.
Special thanks to everyone who came and participated in the Quai × Blip Buildathon: Jos.
It was a pleasure seeing developers at work, building, experimenting, and bringing their ideas to life. But as they say, all good things have to come to an end.
It has been a long journey. We saw so many ideas that could flourish and grow into something massive, but like in life, not everyone gets the opportunity to win.
Initially, we thought we could have up to 8 products take the allocated bounty. However, after seeing the quality of the projects, we decided that rather than splitting the bounty across multiple projects, it would be better to reward a single, highly innovative product.
I remember back in secondary school when we would participate in hackathons like this and sometimes wouldn’t make it past the semifinals. At the time, I thought the product was what was holding me back.
I didn’t understand that the real issue was my inability to learn from my failures and use them as fuel to keep building.
Even if you didn’t win this time, that doesn’t mean you won’t win the next one.
Keep moving forward. Keep building. Keep learning. Most importantly, don’t give up.
The eyes of the ecosystem and the blockchain industry will continue to be on you for future opportunities. So I urge every participant to put your head down, keep building, and keep moving forward.
A special thank you to @blockfuselabs. You are indeed one of the best hubs in Jos.
And I don’t just mean that because of what we were able to achieve with the Buildathon. The energy, authenticity, and talent that came out of the hub were some of the most impressive I’ve seen in Jos.
The builders have a very rigorous journey ahead of them, and I’m glad they have @ScarFaceLabs to help pave the way. More importantly, I’m glad they have the mindset required to see this through.
I’m incredibly happy to see the number and quality of products that came out of this opportunity.
I’m also extremely proud that this opportunity was brought to Nigerian builders by @quainetwork.
As long as I’m in a position to do so, I’ll continue working to show the world the amount of talent brewing here in Africa and prove that we are not just consumers of technology. We are building it here too.
A special shoutout to @globalAfriverse for making it possible for us to coordinate such an event in Jos.
Another big thank you to @Crypto4bailout for instilling valuable knowledge in us about how to successfully ship products in the African market.
To every participant:
@CampusOSAfrica · @fundX__ · @Moneepay · @NordAiii · @q4opinionmarket · @QiFlow_ · @quaibounty · @QuaiForge · @rhodium_hq · @riplx_official · @QUAIMerchant · @usewyp
Thank you for showing up, building, and putting your ideas to the test.
This may be the end of this Buildathon, but it is not the end of your journey.
Keep building.
Keep shipping.
Keep learning.
Keep improving.
You may not have won this one, but there are many more opportunities ahead. Every hackathon, every failed prototype, every rejection, and every lesson is another step toward becoming a better builder.
And I am extremely proud to announce the winner of the Quai × Blip Buildathon: Jos.
Winner: Rhodium — @rhodium_hq
Rhodium uses Blip to streamline WhatsApp marketplace purchases. Users and merchants can buy and sell goods using USDT, QUAI, and QI.
1 sentence pitch:
Utilising the Blip architecture, Rhodium aims to streamline WhatsApp marketplace purchases by enabling both merchants and users to buy and sell goods using USDT, QUAI, and QI.
What stood out:
A novel and narrow-in-scope idea that has broad overlap with users globally, while also enabling local users and merchants to buy and sell goods using one of the most widely used platforms in the world.
Honourable Mentions
Tripplepay — @Tripplepay_M
P2P, mobile, lightning fast. Keep track of your business’s onchain finances through a simple, intuitive, and easy-to-use experience tailored for both web and mobile users utilising Blip Pay.
What stood out:
By broadening the interface to keep track of invoicing and purchases while utilising a web interface, Tripplepay enables businesses to consolidate their payment infrastructure for blockchain payments. The use of platforms like Facebook, WhatsApp, X, and local P2P vendors also creates a strong onboarding funnel with significant growth potential.
MoneePay — @Moneepay
Utilising trustless escrow contracts, businesses and users are able to buy and sell goods P2P without the scam anxiety often attached to these transactions.
What stood out:
Adding a bounty system for developers and freelancers allows founders and project managers to crowdsource work that they would otherwise have to spend valuable time and resources sourcing.
QuaiForge — @QuaiForge
A no-code, user-friendly, one-click checkout widget that allows merchants to seamlessly integrate Blip payments into their websites.
To every builder who participated:
You should be proud of yourselves.
You took an idea from your head, turned it into something tangible, and put it in front of people to judge. That alone takes courage.
Winning is great, but building is the real advantage.
Keep refining your products. Keep talking to users. Keep shipping. Keep learning from the things that didn’t work.
The builders who stay consistent after the applause is gone are the ones who eventually build something the world cannot ignore.
This is only the beginning.
Keep building. Africa is watching.
Quick question for the builders in here 👇
What's the one thing that stops you from accepting crypto payments in your own project or business? Wallet complexity? No good widget? Regulatory worry?
Building QuaiForge, we heard "all three." Curious what you'd add.
Demo day has its own hassles. You can be having a full viable working product and by morning of Demo day a different scenario entirely. We demoed our product @QuaiForge and its working principle. It was awesome! 💪
@blockfuselabs@QuaiNetwork@blippay
Card processors take 1.5–3.9% and can't touch crypto at all.
QuaiForge charges less, settles wallet-to-wallet, and lets you accept a payment method your competitors can't.
Built for merchants ready to move first.
Great builder communities don't happen by accident.
They are created by people willing to share knowledge, answer questions, challenge ideas, make introductions, and give builders the confidence to keep going.
Throughout the @QuaiNetwork × @blippay Buildathon, mentors, speakers, ecosystem contributors, and community members showed up for the builders.
To everyone who gave their time, knowledge, and energy:
Thank you. You helped make the experience what it was.
Your customers already have crypto. Now you can accept it.
QuaiForge: one button, zero code, funds go straight to your wallet.
No custody. No middleman. No excuse. 🟢
Why merchants are choosing QuaiForge:
✅ One button, no code required
✅ You get paid directly — we never touch your funds
✅ Lower fees than card processors
✅ Every payment verifiable on-chain, not just a receipt you have to trust
Accept crypto without becoming a developer.
That's a wrap on QUAI x BLIP Buildathon Jos 🔨🟢
One week ago QuaiForge was an idea. Today we pitched a live contract on Orchard, a working checkout widget, and a real go-to-market plan.
Thank you @QuaiNetwork, @blippay, and @blockfuselabs for the space to build.
@QuaiForge That's because metadata hash is required, it's not a bug.
Don't forget to join our discord to get all of your questions answered.
Here you can take a look at some examples on how to generate that:
https://t.co/edDn2sEttc
Nigeria moved $92.1B on-chain in the past year — 2nd highest grassroots crypto adoption globally.
Paystack, Flutterwave, Monnify can't legally touch any of it.
That's the gap QuaiForge is built for. 🟢
@blippay@QuaiNetwork@blockfuselabs
Spent tonight tracking down a real bug in the quais SDK: ContractFactory.deploy() silently defaults to the literal string "IPFSHash" when no metadata hash is passed, then fails its own validation.
Filing it upstream. This is what building on a young ecosystem looks like 🔨
Small merchants can't accept on-chain payments — building a checkout flow means real engineering.
We have done that for you!
@QuaiForge fixes that: a drop-in "Pay with Blip" widget for @QuaiNetwork, built on @blippay's own checkout infrastructure.
QUAI x BLIP Buildathon Jos 🔨