Rain (RAIN): core definition and technology
Rain, ticker RAIN, is the native governance and ecosystem token of Rain Protocol, a decentralized prediction-market infrastructure project deployed on Arbitrum One. Rain Protocol is designed as an underlying platform for developers, communities, organizations, and AI agents to create and operate prediction markets, rather than as only a single consumer-facing betting application.
The project describes itself as the “Uniswap of prediction markets.” Its infrastructure includes:
- Smart contracts for market creation, trading, liquidity, settlement, and disputes.
- Software development kits, including Rain SDK v2.
- REST and real-time APIs for third-party applications.
- Automated market makers and planned or deployed on-chain order-book functionality.
- Public and private prediction markets.
- AI-assisted market creation and outcome resolution.
- Governance through the Rain DAO.
The protocol is distinct from several unrelated businesses and projects that also use the Rain name, including Rain Financial, a Middle Eastern crypto exchange; Rain.xyz, a stablecoin payments and card-issuing company; Rain.fi, a Solana lending project; and Rainlang/Raindex, a DeFi scripting ecosystem. The contract address is therefore important when identifying the token.
Blockchain architecture
RAIN is an ERC-20 token on Arbitrum One, an Ethereum Layer 2 network.
| Attribute | Details | |
|---|---|---|
| Blockchain | Arbitrum One | |
| Token standard | ERC-20 | |
| Decimals | 18 | |
| Contract address | 0x25118290e6A5f4139381D072181157035864099d | |
| Explorer | Arbiscan | |
| Official website | rain.one | |
| Official X account | @rain__protocol |
The token contract is displayed on Arbiscan as a proxy-based ERC-20 contract. This means the user-facing contract can delegate functionality to an implementation contract, an architecture commonly used to support upgrades, although upgradeability also makes the administrator and governance controls important parts of contract-risk analysis.
Arbitrum provides Ethereum-compatible execution with generally lower transaction costs and faster confirmation than Ethereum mainnet. That architecture is relevant to prediction markets because users may need to open, trade, adjust, and settle positions relatively frequently. Transactions are executed on Arbitrum, while the network’s rollup design ultimately relies on Ethereum for settlement and security.
Rain’s application layer also advertises deposits or access from Ethereum, Base, and BNB Chain. This is cross-chain application access, not evidence that the RAIN token itself is natively deployed as a separate asset on each of those networks.
Primary use cases and real-world applications
Prediction markets
The central use case is the creation and trading of markets tied to future events. Potential market categories include:
| Market category | Examples of possible applications | |
|---|---|---|
| Sports | Match results, tournament outcomes, and major events such as the 2026 FIFA World Cup | |
| Politics and elections | Election outcomes and political developments | |
| Economics | Interest rates, inflation, macroeconomic events, and other economic indicators | |
| Crypto and finance | Asset-price outcomes and market events | |
| Entertainment | Awards, releases, and cultural events | |
| Technology and business | Product launches, corporate events, and technology milestones | |
| Communities and organizations | Internal forecasts, competitions, and private questions | |
| AI-agent markets | Markets generated and monitored by autonomous software agents |
Rain’s permissionless model is intended to allow creators to launch markets without relying on a centralized operator to approve every listing.
Public and private markets
Rain supports both public markets and private markets. Public markets are intended for broad participation, while private markets can be accessed through invitations or codes. This creates potential applications for organizations, teams, online communities, and enterprise forecasting, where the market does not need to be open to the entire public.
Infrastructure for third-party builders
Rain provides the components needed to build independent prediction-market applications. Developers can use the protocol’s SDKs, APIs, and smart contracts to create:
- Custom front ends.
- Embedded forecasting tools.
- Community-specific applications.
- Enterprise or organizational forecasting systems.
- Specialized sports, finance, or entertainment products.
- AI-agent interfaces.
The infrastructure model separates the protocol from individual user interfaces. Rain’s stated objective is for third parties to build products on top of the protocol and potentially receive a share of trading activity generated through their applications or markets.
AI-agent functionality
Rain positions itself as infrastructure for the “agentic era.” In March 2026, the project announced an OpenClaw and AI-agent interface that could allow an agent to create a live prediction market from a single prompt.
Potential functions include:
- Generating market descriptions.
- Monitoring relevant events.
- Creating markets automatically.
- Interpreting outcome data.
- Assisting with market resolution.
This could reduce the operational burden of launching large numbers of specialized markets. However, it also makes the accuracy of AI-generated market terms, data sources, and resolution logic especially important.
Liquidity provision and trading
Users can provide assets to liquidity pools that support market trading. Liquidity providers may receive protocol incentives, including RAIN rewards. Rain’s Version 2 plans also include expanded liquidity infrastructure, AMM-based trading, and on-chain order books.
The combination of AMMs and order books is intended to serve different trading needs. AMMs can provide continuous liquidity for less active markets, while order books may offer more precise pricing and trading control when a market attracts sufficient participants.
Governance and protocol access
RAIN is intended to provide:
- Governance participation through the Rain DAO.
- Access to the platform’s “Trading Power” features.
- Rewards for market creators, liquidity providers, resolvers, and other ecosystem contributors.
- A mechanism for linking protocol activity with token demand through buybacks and burns.
The extent to which all governance and administrative functions are fully decentralized as of September 2026 remains unclear. The project has reported DAO-executed activity, but the Foundation and other administrative components remain relevant to the protocol’s operation.
Market profile and supply data
Market data supplied for September 1, 2026 reports the following figures:
| Metric | Reported value | |
|---|---|---|
| Price | $0.016743141178411195 | |
| Market capitalization | $11,873,795,234 | |
| 24-hour volume | $30,035,634 | |
| Circulating supply | 709,195,093,197 RAIN | |
| Total supply | 1,142,408,564,124 RAIN | |
| Fully diluted valuation | $19,126,930,648 | |
| 1-hour change | -0.2% | |
| 24-hour change | +0.26% | |
| 7-day change | +12.4% | |
| Risk score | 44.79 | |
| Liquidity score | 49.91 | |
| Volatility score | 15.21 |
At the reported figures, approximately 62.1% of total supply was circulating, leaving roughly 433.2 billion tokens outside the reported circulating supply. This gap may reflect treasury holdings, reserves, vesting allocations, locked tokens, or differences in data-provider methodology.
Other market-data sources report circulating supply estimates of approximately 709 billion to 716 billion RAIN. CoinGecko reportedly listed approximately 709.193 billion available tokens, while CoinMarketCap reported approximately 716.57 billion circulating tokens in the gathered results. These differences mean that circulating supply should be treated as a dated estimate rather than an immutable protocol fact.
The supplied CoinStats data did not include verifiable all-time-high or all-time-low prices. Those figures are therefore unverified here.
Tokenomics
Initial and total supply
Rain’s Version 2 whitepaper describes an initial supply of approximately 1.15 trillion RAIN. Arbiscan reported an on-chain total supply of approximately:
1,142,408,564,124.270468950274575405 RAIN
The lower current total relative to the initial figure is consistent with reported token burns. No explicit hard maximum supply was confirmed in the supplied CoinStats data. Rain’s earlier documentation also indicates that the supply model can include both deflationary and inflationary mechanisms, so the initial supply should not automatically be treated as a permanent maximum.
Distribution and vesting
A complete, independently verified allocation table was not available in the research results. Precise percentages for treasury, community, investors, strategic partners, ecosystem incentives, public sale, and liquidity allocations therefore remain unverified.
The earlier whitepaper does identify a 10% team allocation, subject to:
- A one-month cliff.
- Twenty-four-month linear vesting.
- No team tokens released at launch.
Team, strategic-partner, and presale allocations may be locked or released over time. Future unlocks could increase circulating supply and create selling pressure, depending on recipient behavior and market liquidity.
Buyback-and-burn mechanism
Rain’s token documentation states that 2.5% of each market’s trading volume is used to buy back and burn RAIN. The intended economic effect is to connect protocol usage with token demand and supply reduction:
- Trading activity generates protocol-related fees.
- A defined portion is used to purchase RAIN.
- Purchased tokens are permanently removed from circulation.
- Higher trading volume could therefore increase potential buyback activity.
Some later 2026 announcements describe 100% of protocol trading fees as being allocated to automatic buybacks and burns. The public materials do not reconcile this wording with the documented 2.5%-of-trading-volume mechanism. The discrepancy could reflect different definitions of “fees,” an updated policy, or promotional shorthand. The conservative interpretation is that the formal token documentation establishes the 2.5% trading-volume mechanism, while the later 100% fee-allocation claim requires confirmation from current contracts or fee documentation.
Dynamic inflation
Rain’s earlier whitepaper describes a mixed supply model in which 10% of tokens burned through the buyback mechanism may be dynamically minted and allocated to the Foundation for ecosystem-related purposes.
This means the token is not purely deflationary in the strictest sense. Its net supply change depends on:
- The amount of RAIN purchased and burned.
- The amount potentially re-minted under the inflation mechanism.
- Governance or Foundation decisions.
- Future protocol activity and fee generation.
Reported burns
Rain reported more than 100 million RAIN burned by April 27, 2026.
In August 2026, the project reported a substantially larger DAO-related burn:
| Event | Reported details | |
|---|---|---|
| DAO-related burn | 7,419,354,838 RAIN | |
| Approximate circulating-supply impact | About 1% at the time | |
| Reported value at the time | Approximately $108 million | |
| Associated Foundation commitment | $23 million in USDT | |
| Governance context | First reported settlement executed through Rain DAO |
The Foundation, team wallets, and vesting allocations reportedly abstained from the vote. The burn demonstrates that governance has moved beyond a purely prospective feature, although it does not by itself establish that every protocol function is fully decentralized.
Consensus mechanism and security model
RAIN does not operate its own independent blockchain and therefore does not use a separate proof-of-work or proof-of-stake consensus mechanism.
Its security model has four primary layers:
Arbitrum and Ethereum
Token transfers and Rain smart-contract interactions occur on Arbitrum One. Arbitrum’s rollup architecture ultimately anchors settlement and security to Ethereum. This provides stronger infrastructure assurances than a standalone, newly launched blockchain would typically have, but users remain exposed to Layer 2 bridge, sequencing, smart-contract, and upgrade risks.
Smart-contract security
Rain’s market, liquidity, trading, and settlement logic is implemented in smart contracts. The project stated that Hacken reviewed its smart contracts and resolution/dispute logic, and an August 2026 update reported completion of a security audit of the Arbitrum One contracts.
The available research does not include:
- The complete audit report.
- Severity classifications.
- A full list of findings.
- Remediation status.
- The scope of every reviewed contract.
An audit is therefore evidence of review, not proof that the contracts are risk-free.
Oracle and dispute security
Prediction markets require a reliable method for determining whether an outcome occurred. Rain describes a decentralized oracle and dispute framework referred to as Olympus AI.
The intended model includes:
- Automated collection and interpretation of event information.
- On-chain resolution records.
- A process for disputing incorrect outcomes.
- Escalation to human or decentralized oracles where required.
The available public documentation does not establish the precise validator set, staking requirements, challenge windows, penalties, or level of operational decentralization. Oracle performance is consequently a central unresolved technical and economic risk.
Governance and economic security
The Rain DAO is intended to govern protocol parameters and decisions, while incentives are designed to encourage participation by liquidity providers, market creators, resolvers, and other contributors.
The DAO’s reported first settlement and token burn show progress toward community governance. However, the historical role of the Rain Foundation, the proxy-contract architecture, vesting allocations, and administrative controls mean that the practical distribution of control should be evaluated separately from the project’s governance objectives.
Founding team and organization
Rain Protocol is reported as founded in 2024. The project appears to operate with a small, globally distributed team of approximately one to ten employees, with personnel associated with Pakistan, the United States, and Israel.
| Person | Reported role and background | |
|---|---|---|
| Lorena Del Carmen Diaz Moreira | Identified in the regulatory whitepaper as founder | |
| Roy Shaham | Chief executive officer and public-facing executive; appointed CEO in November 2025; based in Tel Aviv, Israel | |
| Muhammad Wasif | Chief technology officer; appointed in January 2025; based in Pakistan; reported background in DeFi and prediction-market engineering | |
| Ana Gabriela De Leon Macias | Identified as president of the Rain Foundation | |
| Rebeca Isabel Munoz Arosemena | Identified as secretary of the Rain Foundation |
Roy Shaham is reported to have approximately 20 years of professional experience and has emphasized Rain’s positioning as neutral infrastructure rather than a centrally curated prediction-market application.
Muhammad Wasif is described as a blockchain engineering lead with more than five years of experience building DeFi and prediction-market products. Public project statements credit the technical team with growing the protocol from approximately $0 TVL to a position described as among the top three prediction markets globally by TVL, although the underlying ranking methodology was not provided.
The available public record does not provide a comprehensive list of smart-contract developers, detailed biographies for all key contributors, or a fully documented history of prior large-scale exits. This limited team transparency is relevant when assessing a young protocol with upgradeable contracts and complex oracle infrastructure.
Project history and development milestones
Rain’s timeline includes the following reported milestones:
| Date | Milestone | |
|---|---|---|
| 2024 | Rain Protocol founded, according to its LinkedIn profile | |
| March 24, 2025 | Date recorded in the whitepaper for the token’s public offer or admission to trading | |
| 2025 | Development of the prediction-market platform and initial ecosystem formation | |
| November 6, 2025 | Public beta launch date reported by an industry overview | |
| December 2025 | Availability through Arbitrum Portal and reported exchange listings including LBank and XT | |
| March 26, 2026 | Version 2.0 whitepaper published | |
| March 2026 | OpenClaw and AI-agent market-creation interface announced | |
| April 2026 | More than 29,000 users and more than 100 million RAIN burned reported | |
| May 2026 | $100 million liquidity commitment announced | |
| June 2026 | More than $200 million in ecosystem commitments reported; Version 2 expansion strategy outlined | |
| July 2026 | First DAO-executed buyback-and-burn settlement announced | |
| August 2026 | 7.419 billion RAIN burn, SDK v2 activity, and Hacken audit completion reported |
The differing March and November 2025 dates likely refer to separate events: the first concerns the token’s public offering or trading admission, while the second concerns the prediction-market platform’s public beta.
Rain’s website reportedly displayed approximately 36,980 active users, while an Enlivex filing cited more than 29,000 users as of April 27, 2026. These figures are not directly comparable because they may use different dates, definitions, or measurement methods.
Funding, treasury activity, and partnerships
Enlivex
The most prominent disclosed relationship is with Enlivex Therapeutics, a Nasdaq-listed company that adopted a digital-asset treasury strategy centered on RAIN.
Reported Enlivex activity includes:
- Additional RAIN purchases at a stated price of $0.0033 per token.
- An option to acquire up to approximately 272.121 billion additional tokens between November 30, 2026, and December 31, 2027.
- Approximately 79.57 billion RAIN held as of May 27, 2026.
- A reported $100 million liquidity commitment.
- More than $200 million in broader ecosystem commitments described by Rain in June 2026.
- A reported $212 million private financing intended to acquire RAIN tokens.
These figures represent token accumulation, treasury exposure, and ecosystem or liquidity commitments. They should not automatically be characterized as a conventional venture-capital investment into Rain Protocol itself. No clearly documented traditional venture round for the protocol was identified.
Arbitrum
Arbitrum is Rain’s principal blockchain ecosystem integration. The token and core contracts are deployed on Arbitrum One, and Rain reported availability through the Arbitrum Portal in December 2025.
Cross-chain access
Rain’s materials identify support for user deposits or interaction involving:
- Ethereum.
- Base.
- BNB Chain.
This expands the potential user base while keeping Arbitrum as the protocol’s principal execution environment.
Exchanges and developer ecosystem
RAIN trading listings were reported on LBank and XT in December 2025. Rain also promotes its own developer ecosystem through SDKs, APIs, documentation, Discord, Telegram, and related builder resources.
A reported $5 million grants program is intended to attract developers, creators, and ecosystem teams.
Hacken
Hacken reportedly reviewed Rain’s smart contracts and resolution/dispute logic. The review is a positive development from a due-diligence perspective, but the absence of a full public audit report in the gathered results limits the ability to evaluate its scope and findings.
Competitive advantages and differentiation
Rain’s claimed advantages are primarily architectural rather than based on being a single dominant consumer application.
| Differentiator | Why it matters | |
|---|---|---|
| Permissionless market creation | Allows creators to launch markets without centralized listing approval | |
| Public and private markets | Supports both open markets and organizational or community-specific forecasting | |
| Protocol-level infrastructure | Lets developers build independent applications rather than relying only on Rain’s front end | |
| SDKs and APIs | Reduces the cost and time required to launch prediction-market products | |
| AMMs and order books | Combines automated liquidity with more conventional trading functionality | |
| AI-assisted creation and resolution | Could increase the number of markets and reduce manual operational work | |
| Arbitrum deployment | Offers Ethereum compatibility and lower-cost execution | |
| Cross-chain access | Allows users to access the application from multiple networks | |
| Buyback-and-burn economics | Attempts to connect protocol activity with token demand and supply reduction | |
| Builder incentives | Grants and revenue-sharing mechanisms are intended to attract third-party developers |
Compared with centralized platforms such as Kalshi, Rain emphasizes on-chain settlement and permissionless infrastructure. Compared with single-application decentralized prediction platforms such as Polymarket, its stated differentiation is that it provides an underlying protocol on which multiple applications can be built.
The most significant execution challenges are also connected to these differentiators. Permissionless markets require reliable safeguards against poorly designed or manipulative markets. AI-assisted resolution requires robust data sources and dispute handling. A multi-application protocol needs sustained developer adoption, not merely token liquidity. Finally, the token’s value proposition depends partly on whether RAIN governance, Trading Power, ecosystem rewards, and buyback mechanisms create durable demand beyond speculation.
Current roadmap and development activity
As of September 1, 2026, the primary development focus is Rain Version 2. Announced or documented priorities include:
- Permissionless market creation.
- Automated market makers.
- On-chain order books.
- AI-assisted market resolution.
- Expanded liquidity infrastructure.
- Broader third-party application support.
- SDK v2 and improved developer tooling.
- DAO governance expansion.
- Growth around major global events, including the 2026 FIFA World Cup.
- Increased support for AI agents and natural-language market creation.
Rain SDK v2 is described as supporting typed access to market creation, AMM trading, order-book trading, liquidity management, market resolution, disputes, winnings claims, REST APIs, and real-time APIs.
The first reported DAO-executed settlement and the August 2026 burn suggest that governance has progressed from a roadmap objective to at least limited operational use. The project’s reported liquidity commitments and Enlivex relationship provide financial support for expansion, although the long-term sustainability of those commitments and their effect on actual market liquidity remain to be demonstrated.
Overall assessment
Rain is an Arbitrum-based prediction-market infrastructure protocol, and RAIN is its governance and ecosystem token. Its central thesis is that prediction markets should be deployable as reusable infrastructure for developers, communities, enterprises, and AI agents rather than controlled exclusively by a single application.
The project’s strongest documented characteristics are:
- Arbitrum-based ERC-20 architecture.
- Permissionless public and private market creation.
- SDK, API, AMM, and order-book infrastructure.
- AI-assisted market generation and resolution.
- A reported buyback-and-burn mechanism.
- Initial DAO-executed governance activity.
- Significant reported liquidity and ecosystem commitments.
- A small but technically focused team.
The main areas where public information remains incomplete are:
- The full token allocation and vesting table.
- The precise implementation of the inflation mechanism.
- The discrepancy between the 2.5% trading-volume burn description and later 100% fee-allocation statements.
- The complete Hacken audit findings and remediation status.
- The technical details of Olympus AI, including validators, challenges, and penalties.
- The degree of decentralization across the Foundation, DAO, oracle, and proxy-contract administration.
- A comprehensive record of conventional protocol funding.
- A complete roster of core developers and their prior track records.
The token’s reported market capitalization and daily volume indicate substantial market participation, but those figures do not by themselves validate the protocol’s long-term utility. The key indicators to monitor are Version 2 delivery, actual third-party builder adoption, sustained prediction-market volume, oracle performance, token unlocks, DAO participation, and whether buybacks and burns are funded by recurring protocol activity rather than one-time treasury or Foundation actions.