REP stands for Ronin Evolution Proposal. Each REP will be a proposal document providing information to the Ronin ecosystem and community.
Here is the list of subjects of REPs:
Number | Title | Type | Status |
---|---|---|---|
REP-0001 | REP Purpose and Guidelines | Process | Living |
REP-0002 | Move Bridge into a standalone application | Standard | Executed |
REP-0003 | Optimistic Fast Finality | Standard | Executed |
REP-0004 | Profile Contract | Standard | Executed |
REP-0005 | Node discovery via DNS | Network | Executed |
REP-0006 | NFT bridge | Bridge | Approved |
REP-0007 | Implement EIP-2718 (Typed Transaction Envelope) | Standard | Executed |
REP-0008 | Sponsoring transaction | Standard | Executed |
REP-0009 | Ether staking on Ronin Network | Bridge | Approved |
REP-0010 | Introducing Rotating Validators | Standard | Executed |
REP-0011 | Ronin Buyback and Burn Proposal | Standard | Stagnant |
REP-0012 | Early exit in maintenance mode | Standard | Executed |
REP-0013 | Propose Berlin EIPs on Ronin | Standard | Executed |
REP-0014 | Propose London EIPs on Ronin | Standard | Executed |
REP-0015 | Ownership Delegation and Context for ERC-721 | Standard | Draft |
REP-0016 | Hard fork Ronin chain to upgrade the Axie and Land smart contracts | Standard | Executed |
REP-0017 | Propose New Slashing Rules | Standard | Approved |
REP-0018 | Node Discovery ENR Filtering | Network | Approved |
REP-0019 | Implement EIP-4844: Shard Blob Transactions on Ronin | Standard | Approved |
REP-0020 | Propose Shanghai EIPs on Ronin | Standard | Approved |
REP-0021 | Propose Cancun EIPs on Ronin | Standard | Approved |