CoinYQ Dossier

Three rulebooks govern the same RAIN

Rain has a functioning market stack, a legal white paper that strips RAIN of present platform and governance rights, and deployed token code that still needs an owner to execute burn-linked issuance. The most revealing part of its history is not a launch date but the distance between the interface people can use, the rights the issuer is willing to promise, and the controls the contract actually retains.

The market exists before the token story is settled

Official builder documentation marks Rain's market factory, AMM trading, on-chain order book, resolution and disputes as live on Arbitrum One. It exposes an SDK plus REST and WebSocket services, while a separate Orbit L3 CLOB is still labelled in development. That distinction matters: Rain is not merely a ticker attached to a roadmap, but neither is every announced component already production infrastructure.

The product must turn disputed facts into settled payouts. Rain's current guide gives challengers a 1-hour window and requires collateral equal to the lower of 0.1% of market volume or $1,000. It says Lex, an Olympus AI judge, reviews first and a further appeal moves to human oracles. Those mechanics describe the market's operating problem; they do not by themselves give RAIN holders ownership of the app or its cash flows.

The March white paper takes rights off the table

Rain Foundation's White Paper v2.0, published on 2026-03-26, fixes the regulated identity of the asset: an Arbitrum ERC-20 at 0x25118290e6A5f4139381D072181157035864099d, with an initial supply of 1,150,000,000,000 RAIN and an admission-to-trading start of 2025-03-24. The Panama foundation is named issuer and administrative overseer.

The same paper draws a narrow legal boundary. RAIN is not required to trade, deposit or create markets. Holders receive no platform access, ownership, profit, refund or redemption rights, and no governance function was exercisable at publication. Governance is described as a future system whose timing, scope and rules had not been finalized.

Even the economic story is conditional. The paper says buyback and burn can be changed, suspended or discontinued and does not guarantee price support. It also marks 'supply adjustment protocols' false. Those statements are difficult to square with the stronger, present-tense tokenomics elsewhere on the same project's site.

Two help pages cannot agree on the entrance ticket

The token help page says holding RAIN is required for Trading Power and participation in prediction markets. It describes the DAO as responsible for all governance decisions and says creators, liquidity providers and resolvers are rewarded in RAIN. Read alone, it makes the token sound like both an access credential and an active political instrument.

The DAO help page says the opposite about access: no RAIN is needed to use the app or participate in markets. It still says holders may submit or vote on proposals. The fee page adds a 5% split—1% to creators, 1.2% to liquidity providers, 0.3% to resolution and 2.5% to buyback and burn—while the inflation page says 10% of burned tokens is automatically minted and manually claimed by the team for the Foundation.

CoinYQ treats each page as a project claim, not a right created by repetition. The sources reviewed on 4 September 2026 did not establish a versioned rule set reconciling access, voting and supply policy with the legal paper and deployed implementation. The applicable layer still needs to be identified for each specific action.

The upgrade key disappeared; the mint operator did not

Hacken's final report of 2025-08-22 captures an earlier design. The owner could trigger a daily mint worth $50,000 using an external price oracle, replace that oracle, change the treasury and authorize UUPS upgrades. Hacken warned that one role could unilaterally influence issuance and upgrades, and that the spot-price dependency could distort the mint amount.

The implementation deployed on 2025-11-04 changed that design. The listed proxy now reaches 0x47716e35f0fa48301aedc77778f794e0ed2c3f0b. Its dailyMinting function can be called only by the owner, no more than once per 86,400 seconds, and creates 10% of the tokens recorded as burned since the prior call for a treasury address the owner can replace.

The present implementation inherits UUPS code but its authorization hook always reverts with 'UUPS upgrades disabled.' It is therefore inaccurate to carry the audit's upgrade power forward as a current fact. The unresolved control is narrower and still material: a live owner decides when the burn-linked mint runs and where its output goes, while the help center calls issuance automatic and the white paper says no supply-adjustment protocol exists.

One reported vote is evidence, not a constitution

A project press release distributed on 2026-07-29 says independent holders completed Rain's first DAO vote. According to that release, they chose a $23 million USDT buyout and burn for locked Credit Refund allocations at $0.0031 per token, while Foundation and team allocations abstained. That is concrete evidence of what Rain says happened in one settlement.

It does not close the larger question. The release does not independently establish that the DAO holds the token owner's mint and treasury powers, and it does not rewrite the March legal paper's statement that no governance right was then exercisable. Rain's story is therefore a three-part record: a usable market system, a deliberately narrow legal promise, and code whose current owner control is smaller than the audited version but more active than the words 'automatic' or 'supply adjustment: false' suggest.

How the project changed

  1. 2025-03-24
    Admission to trading begins

    White Paper v2.0 records this date as the start of RAIN's offer or admission to trading.

  2. 2025-08-22
    Hacken signs off on the oracle-mint design

    The final audit records owner control over a $50,000 daily oracle-priced mint, oracle, treasury and UUPS upgrades.

  3. 2025-11-04
    A replacement implementation changes the controls

    The current implementation replaces the oracle formula with 10%-of-burn minting and disables UUPS authorization while retaining an owner-triggered mint and changeable treasury.

  4. 2026-03-26
    The legal paper denies present token rights

    Rain Foundation publishes White Paper v2.0 with no current platform, redemption, profit, ownership or exercisable governance rights.

  5. 2026-07-29
    Rain reports its first holder vote

    A project release says independent holders approved a $23 million USDT buyout-and-burn settlement at $0.0031 per locked token.

Evidence and primary sources

Last evidence review: 2026-09-04

What is Rain?

Rain is a prediction-market protocol and builder stack on Arbitrum One. Official developer material marks market creation, AMM and order-book trading, liquidity, resolution, disputes, REST and WebSocket services as live; the separate Orbit L3 CLOB remains in development. Its current dispute guide describes a 1-hour challenge window, collateral equal to the lower of 0.1% of market volume or $1,000, an initial Lex AI ruling, and a possible appeal to human oracles.

RAIN is the protocol's ERC-20 at 0x25118290e6A5f4139381D072181157035864099d, but the product and the token do not share one stable rulebook. White Paper v2.0, published 2026-03-26 by the Panama-based Rain Foundation, says holders have no current platform-access, ownership, profit, refund, redemption or exercisable governance rights. Current help pages simultaneously say that RAIN is required for Trading Power and market participation, that it is not required to use the app, and that holders can already submit or vote on proposals.

What problem does Rain solve?

Prediction markets need more than a question and two tradeable answers. Someone must create and fund a market, prices must adjust as positions change, the result must be resolved, and a disputed answer needs an appeal path. Rain packages those functions for both its own interface and third-party builders rather than presenting only a token.

The harder problem for a RAIN holder is evidentiary: which document defines the token today? The dated legal paper, undated live help pages, a historical Hacken audit and the current deployed implementation describe different combinations of access, voting, burning, minting and administrative control. CoinYQ keeps those layers visible instead of converting the broadest marketing statement into a present legal right.

How does Rain work?

Rain's market stack supports public or private markets, 2-26 options, AMM or order-book trading, liquidity provision and a resolution process that official guides say can move from AI or manual resolution into disputes and human-oracle appeals. The fee page says 5% of market trading volume is split as 1% to the creator, 1.2% to liquidity providers, 0.3% to resolution and 2.5% to RAIN buyback and burn. These are current project descriptions, not independently guaranteed cash-flow rights for a token holder.

The token implementation changed after Hacken's 2025-08-22 audit. That report reviewed an owner-triggered, oracle-priced mint worth $50,000 per day and owner control over the oracle, treasury and UUPS upgrades. The implementation deployed on 2025-11-04 and reached through the listed proxy instead makes dailyMinting owner-only, calculates new issuance as 10% of tokens recorded as burned since the last call, allows one call per 86,400 seconds, and sends the result to an owner-changeable treasury. It explicitly disables UUPS authorization, so the present implementation is owner-operated but not currently owner-upgradeable.

This also leaves a live contradiction. The help center calls 10%-of-burn issuance automatic, while the code requires an owner transaction. White Paper v2.0 marks supply-adjustment protocols false even though the implementation can mint against recorded burns. A 2026-07-29 press release says independent holders completed a first DAO vote for a $23 million USDT settlement at $0.0031 per locked token; CoinYQ treats that as the project's evidence of one vote, not proof that every governance power promised in the help center is legally active or controls the token owner.

Key facts

  • Product status: official builder documentation marks the prediction-market protocol, SDK, REST API and WebSocket live on Arbitrum One; the Orbit L3 CLOB remains in development.
  • Token identity: Arbitrum ERC-20 proxy 0x25118290e6A5f4139381D072181157035864099d; current implementation observed on 2026-09-04 is 0x47716e35f0fa48301aedc77778f794e0ed2c3f0b.
  • Legal record: White Paper v2.0 was published 2026-03-26 by Rain Foundation in Panama and lists 2025-03-24 as the admission-to-trading start.
  • Initial supply: 1,150,000,000,000 RAIN with 18 decimals.
  • Current legal-rights baseline: no platform access, ownership, profit, refund, redemption or exercisable governance right under White Paper v2.0.
  • Help-center conflict: one page requires RAIN for Trading Power and market participation; another says RAIN is unnecessary for app or market use while describing proposal and voting participation.
  • Current mint path: owner-only dailyMinting issues 10% of recorded daily burns, no more than once per 86,400 seconds, to an owner-changeable treasury; UUPS authorization is explicitly disabled.
  • DAO evidence boundary: the project says a first vote on 2026-07-29 selected a $23 million USDT buyout-and-burn at $0.0031 per locked token; it does not establish the full legal or technical reach of DAO control.

Official links

Categories

Related coins

Frequently asked questions

Do I need RAIN to use Rain markets?

The sources do not give one answer. White Paper v2.0 and the DAO help page say no; the token help page says RAIN is required for Trading Power and market participation. Check the actual app rule for the action you intend to take.

Can RAIN holders govern the protocol today?

White Paper v2.0 says no governance right was exercisable when published on 2026-03-26. The help center describes proposal and voting participation, and a project press release claims a first holder vote on 2026-07-29. That shows a reported vote, but the reviewed sources do not reconcile its scope with the legal paper or prove that it controls the token owner.

Is 2.5% of every market's volume guaranteed to buy and burn RAIN?

The help center describes that 2.5% policy. The legal paper calls buyback and burn discretionary, changeable and no guarantee of price support, so it is not a contractual yield or permanent holder right.

Can the RAIN owner mint or upgrade the token?

The current implementation lets the owner call a burn-linked daily mint and change the receiving treasury. It inherits UUPS machinery but its authorization function always reverts, so current evidence says mint execution remains owner-controlled while upgrades are disabled.

Why does the 2025 Hacken audit describe different controls?

It reviewed an earlier implementation with a $50,000 oracle-priced daily mint and owner control of oracle, treasury and upgrades. The current implementation replaced that formula, removed the oracle setter and disabled upgrades; the audit is historical evidence, not a complete description of today's code.

External trackers

Choose a tracking site for Rain: