We got a reply from Ozzy, the owner of pons.
We’ve now connected and are working on the next steps for Capet.
We’re building, testing, and moving things forward. More to share soon.
Capet is just getting started.
We’re moving forward with the conversation and working on the next steps.
capet is being built around Pons and its launch ecosystem on Robinhood Chain.
More building. More updates soon.
Capet update is live.
Another product update is now live, with improvements across the launch and prediction experience.
We’re continuing to tighten the core flow, test the mechanics, and ship improvements as we build.
Capet is moving. More updates coming.
The long-term Capet roadmap goes beyond a few market-cap targets.
We’re working toward more market types around token launches and more ways for users to express a view on what happens next.
Still early.
We want someone seeing Capet for the first time to understand a market immediately.
What is the question?
What is the deadline?
What happens if YES wins?
What happens if NO wins?
The interface should answer those questions without making users search for them.
Today’s work:
Testing markets.
Reviewing settlement conditions.
Cleaning up the launch flow.
Fixing edge cases.
No major announcement.
Just another day of building Capet.
Token launches already create a lot of predictions naturally.
“Will it bond?”
“Will it reach $30K?”
“Will it reach $100K?”
Capet is turning those questions into actual markets.
That’s the product.
Small improvements compound.
Today it was the prediction flow.
Tomorrow it might be settlement.
Next week it could be a completely new market type.
We’re keeping the team focused on shipping consistently.
Capet is moving from the “does the idea work?” stage into the “how do we make this really good?” stage.
The core flow works.
Now we're improving everything around it.
We’re continuing to build around the Pons Family ecosystem on Robinhood Chain.
We’ve connected with Ozzy and reached out about what we’re building with Capet.
Long-term ecosystem building matters to us just as much as shipping the product.
We’ve been testing different ways to structure prediction markets around newly launched tokens.
The biggest lesson so far:
Clear questions make better markets.
A defined target, deadline and settlement condition should always be obvious before someone takes a position.
Our current focus is simple:
Make launching a token easy.
Make creating a prediction market clear.
Make taking a position straightforward.
Make settlement reliable.
Everything else comes after that.
We’re not building Capet around a single launch cycle.
The goal is to build a launchpad and prediction market infrastructure that can support thousands of markets over time.
That means getting the foundation right now.
A lot of Capet progress right now isn’t visible from the outside.
Market logic, settlement conditions, payout handling, launch flow and UX.
Not the most exciting things to post about, but they’re what make the product work.
We’ve been running more test launches internally.
Every test gives us another edge case to fix, especially around prediction markets and settlement.
The product gets better every time we break something and fix it.
Another Capet update shipped.
We’re spending this phase tightening the core experience rather than adding features for the sake of adding them.
Launch, prediction, settlement, payout.
That loop needs to be solid first.
We’re building Capet on @ponsdotfamily@RobinhoodCrypto and excited to be part of the ecosystem while we build the next generation of launchpad + prediction markets on Robinhood Chain.
A lot of Capet development right now is happening behind the scenes.
Market logic, settlement, payouts, edge cases.
The boring stuff that makes the product work.