Rain 백서

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 3쪽 중 2쪽

rce allocation: Financial and operational resources allocated to the project to date include expenditures for software development, marketing services, technical infrastructure, and external audits. These allocations have been directed 19 toward maintaining the protocol, expanding its functionality, supporting user growth, and ensuring the security and integrity of the system. ● D.10 Planned use of Collected funds or crypto-assets: Not applicable - The issuer does not intend to collect funds or crypto-assets in relation to the admission to trading of RAIN. No funds are being collected under this white paper. Part E - Information about the offer to the public of crypto-assets or their admission to trading ● E.1 Public offering or admission to trading: ATTR - admission to trading. ● E.2 Reasons for public offer or admission to trading: The RAIN token has already been admitted to trading via a launchpad. The purpose of this admission is to enable secondary market trading and price discovery for the governance token. The token is intended to be used for participation in protocol governance once the DAO is activated. In accordance with the token distribution and inflation schedule, any funds or value generated through the protocol are allocated to ecosystem growth, staking incentives, development, marketing, strategic partnerships, and community contributor rewards. ● E.3 ● E.4 ● E.5 ● E.6 ● E.7 ● E.8 ● E.9 ● E.10 ● E.11 ● E.12 Total number of offered/traded crypto-assets: 1,150,000,000,000. ● E.13 Targeted holders: ALL. 20 ● E.14 ● E.15 ● E.16 ● E.17 ● E.18 ● E.19 ● E.20 ● E.21 ● E.22 ● E.23 ● E.24 ● E.25 ● E.26 ● E.27 ● E.28 ● E.29 Purchaser's technical requirements: A purchaser must have a self-custodied blockchain wallet compatible with the Arbitrum network (e.g. an Ethereum-compatible EVM wallet such as MetaMask or WalletConnect) and must be able to interact directly with decentralized exchanges or other trading venues on that network. The purchaser is responsible for managing their own private keys and on-chain transaction fees (gas). ● E.33 Trading platforms name: Kraken, KuCoin, MEXC,, BingX, BitMart, WhiteBit, Lbank, XT, Bitrue, BloFin, Gems Trade. No new admission to trading is being sought under this white paper. Part F - Information about the crypto-assets ● F.1 Crypto-asset type: Governance token. 21 ● F.2 Crypto-asset functionality: RAIN is a governance token intended to be used for participation in the decentralized governance of the Rain protocol once the DAO governance is activated. It does not grant access to the platform's core prediction market functionalities, and is not required to trade, deposit, or create markets on the protocol, nor does it provide any ownership or redemption rights. ● F.6 Crypto-asset characteristics: Name: RAIN. Type: Governance token (crypto-asset other than an asset-referenced token or e-money token). Blockchain: Arbitrum Network (Ethereum Layer-2, ERC-20 standard). Contract Address: 0x25118290e6A5f4139381D072181157035864099d. Total Token Supply: 1,150,000,000,000 $RAIN (1.15 trillion). Transferability: Freely transferable between self-custodied wallets compatible with Arbitrum; no issuer-imposed restrictions apply. ● F.8 Website of the issuer: https://www.rain.one/ ● F.9 Starting date of offer to the public or admission to trading: 2025-03-24. ● F.10 Publication date: 2026-03-26. Part G - Information on rights and obligations attached to crypto-assets ● G.1 Purchaser rights and obligations: Purchasers of the RAIN token do not obtain any redemption rights, claims to profits, ownership rights, or rights to receive refunds under this crypto-asset. The RAIN token does not entitle purchasers to access, use, or operate the Rain protocol. Governance participation rights will apply only once the DAO governance framework is activated. Purchasers remain fully responsible for holding and securing the token in a self-custodied blockchain wallet compatible with the Arbitrum network and for complying with any applicable legal and tax obligations in their jurisdiction. ● G.2 Exercise of rights and obligations: At the time of this admission to trading, no governance or other functional rights are yet exercisable by RAIN token holders. Governance functionality will become accessible only upon activation of the Rain DAO, at which point token holders will be able to participate in governance processes through a decentralized on-chain voting mechanism accessible via a compatible self-custodied Arbitrum wallet. Any such participation will be subject to 22 the governance rules adopted by the DAO at that time. Purchasers are responsible for monitoring future protocol updates to determine when governance rights become exercisable. ● G.3 Conditions for modifications of rights and obligations: Until DAO governance is activated, the Rain Team may modify the rights or conditions associated with the RAIN token in accordance with the protocol's development roadmap. Any future modifications of token-related rights or obligations may occur only following the activation of decentralized governance mechanisms. The timing, scope, and governance procedures for such modifications are not finalized and will be determined through on-chain governance processes, subject to the governance rules adopted at that time. ● G.4 Future public offers: No future public offers are currently planned. This white paper relates solely to the prior public offer and subsequent admission to trading of the RAIN token. Should any new public offer be conducted in the future, a separate or modified white paper will be submitted in accordance with Article 4 of Regulation (EU) 2023/1114. ● G.5 Issuer retained crypto-assets: 157,000,000,000. ● G.6 Utility token classification: False. ● G.7 Key features of goods/services of utility tokens: Not applicable. ● G.8 Utility tokens redemption: Not applicable. ● G.9 Non-trading request: True. ● G.10 Crypto-assets purchase or sale modalities: Not applicable. ● G.11 Crypto-assets transfer restrictions: The RAIN token is freely transferable on secondary markets, and there are no transfer restrictions imposed on users trading the token once it is in circulation. However, certain token allocations (such as team, strategic partners, and presale participants) are subject to predefined lockup and linear vesting schedules to ensure long-term alignment, as publicly disclosed in the tokenomics. These vesting conditions apply only to allocated tokens not to general market participants. ● G.12 Supply adjustment protocols: False. 23 ● G.13 Supply adjustment mechanisms: Not applicable. ● G.14 Token value protection schemes: False. ● G.15 Token value protection schemes description: Not applicable. ● G.16 Compensation schemes: False. ● G.17 Compensation schemes description: Not applicable. ● G.18 Applicable law: Panama Law. ● G.19 Competent court: Competent courts of Panama. Part H - Information on the underlying technology ● H.1 Distributed ledger technology (DTL): The RAIN token is deployed on the Arbitrum network, a Layer-2 rollup built on the Ethereum blockchain. Arbitrum utilizes Ethereum's distributed ledger infrastructure and inherits its security model through optimistic rollup technology. The protocol leverages the Ethereum mainnet for settlement, ensuring decentralization, transparency, and verifiability. Cross-chain compatibility with Ethereum, BNB Chain, and Base is supported through standard bridging mechanisms. ● H.2 Protocols and technical standards: RAIN is an ERC-20-compliant token deployed on the Arbitrum network, which operates as an Ethereum Layer-2 rollup. The project follows widely adopted Ethereum standards, including ERC-20 for fungible tokens and standard bridging interfaces for interoperability with other EVM-compatible networks such as Ethereum, BNB Chain, and Base. Smart contracts are written in Solidity and verified on Arbiscan. The token contract is non-upgradeable, and the protocol architecture adheres to established DeFi security and interoperability best practices. ● H.3 Technology used: The Rain protocol operates on the Arbitrum Layer-2 network, leveraging Ethereum's base layer for settlement and security. Arbitrum utilizes optimistic rollup technology to aggregate and compress transactions off-chain before finalizing them on the Ethereum mainnet, providing scalability and cost efficiency while maintaining decentralization. The Rain ecosystem incorporates smart contracts written in Solidity, decentralized oracle integrations for market 24 resolution, and cross-chain bridging for compatibility with Ethereum, BNB Chain, and Base networks. All deployed contracts are publicly verifiable on Arbiscan, ensuring transparency and auditability. ● H.4 Consensus mechanism: RAIN operates on the Arbitrum network, which inherits its consensus security from the Ethereum blockchain. Ethereum currently uses a Proof-of-Stake (PoS) consensus mechanism, whereby validators stake ETH to propose and attest to new blocks. Arbitrum employs an optimistic rollup model that assumes transactions are valid by default and relies on fraud proofs to resolve disputes, anchoring final transaction data to Ethereum's PoS consensus layer. This architecture ensures decentralization, immutability, and security consistent with the Ethereum mainnet. ● H.5 Incentive mechanisms and applicable fees: Transactions involving the RAIN token are secured through the underlying Arbitrum and Ethereum networks, which use validator incentives under Ethereum's Proof-of-Stake consensus model. Validators earn gas fees paid in ETH for securing and finalizing transactions. The Rain protocol itself does not introduce additional consensus incentives. Users interacting with Rain markets pay standard network gas fees on Arbitrum, which are significantly lower than those on Ethereum mainnet. The protocol may apply minimal functional fees for specific market operations or interactions, as described in the Rain documentation, to support ongoing development and buyback-and-burn mechanisms, but no additional fees are charged for basic token transfers. ● H.6 Use of distributed ledger technology: False. ● H.7 DLT functionality description: Not applicable. ● H.8 Audit: True. ● H.9 Audit outcome: The RAIN token smart contract successfully passed a full security audit conducted by Hacken. The audit confirmed that the token's code is secure, functions as intended, and complies with industry best practices for ERC-20 token standards. No critical or high-severity vulnerabilities were identified. Minor informational observations were resolved prior to deployment. The audit report is publicly available on the Hacken website at https://hacken.io/audits/rain/ . 25 Part I - Information on risks ● I.1 Offer-related risks: The RAIN token has already been admitted to secondary-market trading, and no new public offer is being made under this white paper. Accordingly, there are no subscription-stage or fundraising-related risks. However, secondary-market participants remain exposed to the general risks associated with trading crypto-assets, including high price volatility, limited liquidity, and potential loss of capital. The value of RAIN may fluctuate significantly based on market conditions, protocol adoption, or external events affecting the DeFi sector. Exchange listings and liquidity provisioning are managed by independent third parties and are outside the control of the Rain Team. Purchasers should carefully evaluate their risk tolerance before engaging in secondary-market transactions. ● I.2 Issuer-related risks: The issuer of the RAIN token is a non-EU entity domiciled in Panama. As such, it is not subject to EU prudential or conduct supervision. Any legal claims relating to the issuance of the RAIN token would fall under the jurisdiction of Panamanian courts and the applicable laws of Panama, which may differ materially from those of EU Member States and may offer limited investor protection. The issuer's ability to support the Rain protocol depends on its continued operational, technical, and financial capacity. Changes in regulatory treatment, local law, or the issuer's structure could impact its ability to fulfil its intended role. ● I.3 Crypto-assets-related risks: * Market risk: RAIN is subject to high volatility and limited liquidity, and its value may fluctuate significantly on secondary markets. o Smart contract risk: Despite external audits, vulnerabilities or operational bugs may exist and could impact protocol integrity. o Governance risk: DAO governance is planned for Q4 2025; until then, the Foundation controls protocol parameters and upgrades. o Oracle and market-resolution risk: Errors or disputes in oracle outcomes could delay or affect prediction-market results. o Tokenomics risk: Locked or vested allocations may unlock over time and influence circulating supply and token price. 26 o Deflationary mechanism risk: The buyback-and-burn mechanism is discretionary, depends on protocol parameters and governance decisions, and does not guarantee price support, liquidity, or token value. The mechanism may be modified, suspended, or discontinued in the future in accordance with protocol rules. o Network and custody risk: Operation depends on Arbitrum and Ethereum networks; users are responsible for secure self-custody of private keys. o Regulatory risk: The issuer is domiciled outside the EU; legal or policy changes may affect trading access or compliance obligations. ● I.4 Project implementation-related risks: * Development and delivery risk: The Rain protocol and its future components (e.g., DAO governance, additional integrations) are still under development and may be delayed or implemented differently from current plans. o Technical integration risk: Cross-chain functionality and oracle integration depend on third-party infrastructure and may experience interruptions or incompatibility with future updates. o Resource dependency: The project's progress relies on the continued availability and expertise of key contributors within the Foundation and Rain Team. o Governance transition risk: The shift from Foundation-led management to planned DAO governance may introduce operational uncertainty or coordination challenges. o Security and upgrade risk: Protocol upgrades or contract deployments may encounter unforeseen technical or security issues despite audits and testing. o Partnership and ecosystem risk: The project's success depends on continued community participation, market-maker support, and third-party service collaboration. ● I.5 Technology-related risks: * Smart-contract vulnerabilities: Even after successful audits, bugs or exploits could be discovered that compromise contract behavior or funds. 27 o Upgrade and deployment risk: The protocol's upgradable contracts and ongoing development may introduce implementation or configuration errors. o Oracle and data-feed reliability: Prediction-market outcomes depend on decentralized oracle inputs; any oracle malfunction or manipulation could affect results. o Network dependency: Operation relies on the Arbitrum Layer-2 and Ethereum base layer; congestion, outages, or protocol changes on either network could disrupt service. o Bridge and interoperability risk: Cross-chain transfers between Arbitrum, Ethereum, BNB Chain, and Base use third-party bridges that may be exposed to security or operational failures. o Custody and key management: Users must safeguard private keys in self-custodied wallets; loss or compromise results in irreversible loss of tokens. o Third-party dependency: The project depends on external infrastructure providers (RPC nodes, indexers, data oracles) whose availability or reliability cannot be guaranteed. ● I.6 Mitigation measures: * Independent audits: The RAIN token smart contract has undergone an external security audit by Hacken, and a protocol-level audit is underway to identify and address vulnerabilities before full deployment. o Code transparency: All smart contracts are verified and publicly viewable on Arbiscan, allowing community and third-party review. o Multisig governance: Protocol upgrades and treasury actions are managed through a multisignature structure controlled by the Foundation, reducing single-point-of-failure risks. o Progressive decentralization: Governance is intended to transition toward a DAO to distribute protocol decision-making over time. This transition does not affect the Rain Foundation's responsibility for this white paper or its regulatory obligations. o Standardized development practices: Smart contracts are written in Solidity and follow widely adopted ERC-20 and DeFi security standards. 28 o Oracle and infrastructure review: The project continuously evaluates its oracle systems and external infrastructure providers to mitigate reliability and data-feed risks. o User education: Participants are encouraged to follow wallet-security best practices and self-custody guidelines to prevent key-management losses. Part J - Information on the sustainability indicators ● J.1 Adverse impacts on climate and other environment-related adverse impacts: The Rain protocol operates on the Arbitrum network, which relies on the Ethereum Proof-of-Stake (PoS) consensus mechanism. PoS consumes significantly less energy than Proof-of-Work systems, resulting in a minimal environmental footprint compared to earlier blockchain models. The Rain Team does not operate any independent infrastructure that materially contributes to energy consumption or greenhouse-gas emissions. No ad
프로젝트로 돌아가기