RAINRAINRISK MARKETS · PROTOCOL
⚠ HONEST STATUS: This is a demo deployment on Arbitrum One using play-money RUSD (faucet token — the protocol itself is token-agnostic). Contracts are pre-audit — Sourcify-verified, 163/163 forge + 38/38 integration tests green, but no external audit yet. Current max position is 3,125 RUSD, bond-limited (design target at $300M TVL: $520k–600k). Parametric insurance is a supported capability, not a launched product. One V1 incident is fully disclosed in the audit package. Credibility is the product — read the gaps before the claims.

ONE TRADE, THREE FORMS

Games · Predictions · Insurance — the same underlying risk transfer, served by one protocol

Every risk-transfer industry performs the same operation: a risk seller and a risk buyer agree on an uncertain event, and value moves when it resolves. People trade risk at random through games, for profit through predictions, and as protection through insurance. The industries differ only in where the truth comes from and who participates — not in the trade. RAIN serves all three on one primitive: trustless resolution, instant pre-collateralized settlement, and an underwriting vault that prices spread against variance regardless of what the distribution is called.

GAMES · LIVE PREDICTIONS · LIVE VIA RAIN MARKETS PARAMETRIC INSURANCE · SUPPORTED PERSONAL INSURANCE · ROADMAP

1GAMES — RISK BOUGHT AT RANDOM · LIVE

Blackjack and roulette run today on Arbitrum One over RAIN Channels: ~300 ms per action, zero gas, provable fairness — every card and spin a mutual commit-reveal, every state dual-signed, every dispute objectively decidable on-chain. The games are the protocol's live proof under the most adversarial conditions possible: if it can settle a $520k blackjack hand in 300 ms with fraud proofs, it can settle any risk.

Who it's for: gaming operators — bond into HouseBond, run a house node, plug in new games via IRulesVerifier. Live games · SDK & builder guide · play the demo ↗

2PREDICTIONS — RISK TRADED FOR PROFIT · LIVE VIA RAIN MARKETS

The Rain prediction-markets side (built by the Rain markets team) runs permissionless markets on world events: creation, trading, order book, liquidity, split/merge — with an AI + dispute + appeal resolution layer that serves as the protocol's oracle for real-world outcomes. It ships as rain-sdk-v2 on npm and is wrapped unmodified inside the unified SDK's rain.predictions module.

Who it's for: trading firms and market builders — trustless transaction builders for every market action, api-backed reads for indexing and order books (labeled as such). Unified SDK

3PARAMETRIC INSURANCE — RISK SOLD AWAY AS PROTECTION · SUPPORTED

A parametric cover is a prediction-market position bought as protection. The event is public-data-verifiable — flight delayed ≥ 3 h, rainfall > X mm, price < Y — so no claims process exists: the data either printed past the threshold or it did not. Everything needed is live today: the resolution layer (Rain markets' dispute system or signed data feeds), underwriting capacity (the risk vault), and instant pre-collateralized settlement.

Worked example — flight-delay cover

ROLEWHOWHAT HAPPENS
Risk buyerTraveler with a €400 non-refundable connectionBuys €400 of the YES side of “flight AB123 arrives ≥3 h late” at the market price (say 10% → €40 premium). Intent: protection, not profit.
Risk sellerMarket counterparties + the risk vault (underwriting capacity)Sell the risk for the ≈€36 expected margin; exposure is bounded by the vault's exposure rules, payout collateralized before the position opens.
ResolutionThe prediction-markets resolution layer / signed flight dataReads the public arrival record. Disputed outcomes escalate through the bonded dispute + appeal game.
SettlementThe protocolIf late: the traveler is paid €400 the moment the market resolves — no adjuster, no cheque, no delay. If on time: underwriters keep the premium.

The precise line. What is supported today is parametric cover on public-data events — a capability the live components already serve. Personal/individual insurance — private loss events, per-claim assessment, quote-based underwriting, long-lived reserve management — is explicitly Stage 2 / roadmap. We state the line plainly rather than blurring it.

Who it's for: insurance companies — distribute parametric products on protocol rails, or deploy a dedicated instance settling in your own token (token-agnostic deployments). Whitepaper §7P

+RANDOMNESS AS A PROTOCOL SERVICE

The games vertical forced the protocol to solve trustless randomness at interactive speed: two-party commit-reveal hash chains — unbiased if either party is honest — with on-chain fraud proofs and a Pyth Entropy session seed as defense-in-depth. Any builder who needs cryptographically fair random outcomes can consume the same machinery. Randomness research · Channels spec