• © Goverland Inc. 2026
  • v1.0.1
  • Privacy Policy
  • Terms of Use
Ricochet ExchangeRicochet Exchangeby0x3226C9EaC0379F04Ba2b1E1e1fcD52ac26309aeA0x3226…9aeA

RIC to REX Token Transition

Voting ended over 2 years agoSucceeded

This is a proposal to convert the Ricochet (RIC) SuperToken to a regular ERC20 token called REX Protocol Token (REX). A new ERC20 contract using OpenZepplin’s ERC20 contract with a custom function for burning RIC tokens for REX tokens one for one (1:1). Moving from a SuperToken to a standard ERC20 token removes a significant amount of attack surface from the protocol. REX is more secure since it removes the SuperToken logic and the upgradability from the RIC token.

Proposed REX Protocol Token (REX) Contract


import "@openzeppelin/contracts/token/ERC20/ERC20.sol";

contract REXProtocolToken is ERC20 {

    ERC20 public constant RICOCHET_TOKEN = ERC20(0x263026E7e53DBFDce5ae55Ade22493f828922965);

    constructor() ERC20("REX Protocol Token", "REX") {
        
    }

    function supportREX(uint amount) external {
        // Burn the SuperToken
        require(RICOCHET_TOKEN.transfer(address(0), amount), "burn failed");

        // Mint the new REX token to 1:1
        _mint(msg.sender, amount);
    }

}

Since RIC has a max supply of 10M, REX will also have a max supply of 10M too.

Off-Chain Vote

Yes, transition RIC to REX
379.94K RIC100%
No, take no action
0 RIC0%
Quorum:152%
Download mobile app to vote

Timeline

Jun 02, 2023Proposal created
Jun 02, 2023Proposal vote started
Jun 05, 2023Proposal vote ended
Oct 26, 2023Proposal updated