Rain Protocol has completed the final stage of a Credit Refund settlement that will permanently remove 7,419,354,838 $RAIN tokens from circulation.
The settlement followed an investigation by the Rain Foundation into coordinated activity involving multiple wallets.
According to the Foundation, a group of participants used several wallets in an attempt to get around the Credit Refund program's $5,000 allocation limit for individual users.
Rather than resolving the issue exclusively through an internal process, Rain brought the proposed solution to the protocol's decentralized autonomous organization.
$RAIN holders were allowed to vote on how the remaining locked Credit Refund allocations should be handled. Foundation-controlled wallets, team wallets and team vesting allocations did not participate, leaving the decision to the wider token-holder community.
Token burn completes the settlement
Under the approved arrangement, the Rain Foundation committed $23 million in USDT to purchase eligible remaining locked Credit Refund allocations at a fixed price of $0.0031 per $RAIN.
Participants who qualified for the settlement could claim USDT in exchange for their outstanding locked allocations during a defined claim period. Once the window closed, the tokens acquired through the program were permanently removed from circulation.
The process resulted in a burn of exactly 7,419,354,838 $RAIN tokens. Rain said the amount represents approximately 1.035% of the token's circulating supply, leaving 709,173,225,165 $RAIN in circulation following the transaction.
Based on the market price at the time of the burn, the tokens removed from circulation had a value of approximately $108 million.
The transaction is publicly recorded on the Arbitrum blockchain, allowing the completion of the burn to be independently verified.
View the burn transaction on Arbiscan
The burn is significant not simply because of the number of tokens involved, but because it represents the execution of a decision made through Rain's governance system. The Foundation supplied the capital for the settlement, while token holders determined whether the proposed resolution should proceed.
Once burned, the tokens cannot be returned to circulation. This provides an on-chain resolution to a process that began with the identification of activity designed to circumvent the program's allocation restrictions.
The structure also separates several aspects of the settlement. Eligible participants received USDT rather than newly issued tokens, while the $RAIN acquired by the Foundation was not retained as treasury inventory or made available for future distribution. Instead, those tokens were permanently destroyed.
For participants, this offered a defined exit for remaining locked allocations. For the protocol, the arrangement offered a way to resolve the dispute without increasing the token supply or leaving the affected allocations outstanding.
The outcome also provides an early example of how Rain intends to use token-holder governance when decisions have direct financial consequences for participants.
"Governance matters most when a decision has real consequences for the people participating in a protocol," said Roy Shaham, CEO of Rain Protocol. "The community made the decision, the Foundation committed the capital, and this burn completes that decision transparently on-chain for anyone to verify."
The completion of the Credit Refund settlement comes as Rain prepares for its next development phase, referred to by the project as V2. The Foundation's decision to exclude its own voting power from the settlement vote was intended to leave the final decision with the community rather than project insiders.
With the claim period now closed and the acquired tokens permanently burned, the Credit Refund process has reached its final stage. The blockchain transaction provides a public record of the outcome, while the DAO vote establishes the governance basis for the settlement.
For Rain, the episode could also serve as a reference point for future governance decisions as the protocol develops.
It demonstrates a model in which a contentious allocation issue can be presented to token holders, resolved through a community vote and ultimately implemented through an independently verifiable on-chain transaction.
