How do you build a market with more than two possible answers on Rain?
Every market is a pool, and each possible answer inside it is a sub-pool that trades as its own Yes or No.
Take "Who will win the league?"
Every team gets its own sub-pool, with its own price and its own result.
For builders, that means one structure for every market your platform runs, from a single yes/no to a full list of outcomes.
One question, as many answers as it needs.
How does a platform on Rain make money?
Traders pay a 5% fee on every trade and the protocol splits that fee between the roles that make a market work: the liquidity providers who fund the pool, the creator who launches the market, and the resolver who settles the outcome.
Run every role yourself, or share them with your users. Your platform, your call.
Every market has to answer one question: who's on the other side of your trade?
Rain has two answers.
The AMM is a pool that always quotes a price. You trade against it directly, and the price moves with every trade. No waiting for a counterparty, which matters most in new and niche markets where one might not exist yet.
The order book is traders quoting each other. Set the exact price you'll buy or sell at, and your order sits onchain until someone takes it. Sharper pricing where there's real activity.
Rain gives builders both. Quiet markets stay tradeable, busy markets stay tight, and your platform calls the same SDK either way.
Your market is live. Here's what happens when people trade it.
Trading on Rain means buying shares in an outcome. A user picks an option, sets an amount, and the SDK hands your platform a transaction ready to sign. Prices move with every trade, so a position is always worth what the market currently believes.
Selling is the same motion in reverse. Users can exit any time while the market is open, or hold to resolution and claim if their outcome wins.
For your platform, the whole lifecycle is method calls: buy, sell, read positions, claim.
You decide what the experience looks like. The protocol handles what happens underneath.
The Rain SDK is built on three pillars. The split exists so key management never leaks into business logic.
Rain is the stateless core. It prepares unsigned transactions and reads data, but holds no keys and signs nothing. That's why it can run anywhere, including a public server, with nothing to expose.
RainAA is the signer. It derives a smart account from the user's wallet and sends every transaction with gas sponsored by the builder. No popups per trade
RainSocket is the live feed. Trades, prices, fills, resolutions, pushed the moment they happen.
Rain builds it. RainAA signs it. RainSocket tells you it landed.
Launching a prediction markets platform used to take a team and months of engineering.
On Rain it's an afternoon: install the SDK, point your agent at the docs and describe the platform you want. Your agent writes the integration. You review and sign.
There is no application form and no approval step.
The docs are live now. Start today.
rain.one/docs/For-Developers…
Rain retweeted
Sports and crypto are most of prediction market volume today. That's a fraction of what the primitive covers.
Anything with a future outcome and a probability can be a market. The primitive underneath covers every credible asset in the world, and the basic systems to get there still have to be built.
Two years from now I think we'll still call this the beginning.
Most agents in prediction markets have the same job description: trade.
Someone else built the venue, someone else wrote the rules, and the agent shows up to take positions.
On Rain, agents are builders.
With a single prompt they can launch entire forecasting platforms.
You stop renting space in someone else's market and start running your own.
It's official: Rain SDK v2 is live, and open to anyone building on it.
The SDK has been on npm for a while. We held the official announcement until @hackenclub completed the audit of the prediction market contracts. Now that the green light is secure, v2 replaces v1.
What changes for builders:
- Orders are placed, matched and cancelled onchain.
- Off-chain matching that settles after the fact is gone. You choose AMM or order book per market.
- Your users sign once per session, then trade without wallet prompts.
- Collateral splits into complete Yes/No share sets and merges back 1:1, without touching the book or moving price.
- Resolution, disputes and appeals run at the protocol level, with bonds and time windows at each stage.
Prediction markets have been a product you use. On Rain, they're an end-to-end platform you build.
Every SDK is readable. The question is by who.
Most are built for a developer to study, integrate, and maintain.
Rain's is built for an agent to use: creation, pricing, trading, liquidity, resolution, each one a piece it can call directly.
So the agent assembles the platform, and no person has to interpret the docs to get there.
Which leaves one job: knowing what you want to build.
🤖 Made with AI
We just burned $108M.
Not locked. Not vested. Burned. 🔥
7,419,354,838 $RAIN permanently removed from circulation - exactly as our community voted in our first DAO governance decision.
Promises made on-chain, kept on-chain.
arbiscan.io/tx/0x426c80c749f…
$RAIN is now available on @HyperliquidX.
A decentralized exchange purpose-built for trading, with the order book fully onchain and fills settling into your own wallet.
Permissionless protocol, permissionless venue.
🤖 Made with AI