Most launchpads pair every new coin with the same generic asset, so the market underneath says nothing about the idea. OutcomePad lets you launch against an outcome — and the pair becomes part of the story.
A major event does not need to produce just one coin. Every launch that picks the same outcome shares its reference layer.
drag to shuffle
Normally you launch SHIP / ETH, and ETH tells you nothing about why SHIP exists. Here the launch connects to a specific outcome instead.
Choose the event or question the launch should be associated with, and define the outcome — including which side of it you are on.
Will the product ship before Dec 31? · YES
OutcomePad creates a canonical onchain reference token for that outcome. The same defined outcome maps back to the same asset rather than creating endless duplicates.
SHIPYES
Create your coin and open its market directly against the outcome token, in a real pool whose liquidity locks as it is created.
SHIP / SHIPYES
Instead of launching SHIP / ETH, the coin now trades against something that describes what the launch is about. Every future coin that picks the same outcome reuses the same SHIPYES — the registry has no branch that deploys a second one.
reading the factory…
No. An outcome token does not resolve. Nobody adjudicates whether the thing happened, nothing settles, and holding it pays you nothing either way. It is a fixed-supply reference asset named after a question, a side and a date.
It exists so a coin can be paired with the idea it is about instead of with ETH. That is the whole claim.
To the contract, nothing — the token keeps trading after the date passes, because nothing resolves. The date earns its place by being one of the four fields that make the identity: it is what stops the same question with two different deadlines from collapsing into one token. Two dates, two markets.
Nothing. There is no protocol fee anywhere in the contracts, no launch fee and no allocation. The pool charges 1% and all of it is claimable by whoever launched the coin.
Nobody, including us. It is deployed by the registry rather than by a wallet, and has no owner, minter, pauser or upgrade path. The same defined outcome always maps back to the same reference asset, so a busy event does not fragment into a hundred near-identical tokens.
No. The position is minted to a locker contract that has no burn function and no withdraw — only collect(), which pulls fees to the recorded creator and moves no liquidity. There is no privileged address, ours included, that could pull it.
An ETH pair is the same for every coin launched that day, so it is infrastructure — it has nothing to do with the idea. Pairing against an outcome makes the other side of the trade describe the launch, and puts the side you are taking into the market structure itself.
It costs you something real. Your chart moves when the quote asset moves, and a buyer is taking two positions at once — that is not hidden anywhere. What you get for it is that the pair means something.