- Edited
Disponible dans le 2ème post
Proposal Summary:
This proposal aims to approve modifications to the RealToken Wrapper on RMMv3 and transfer the responsibility for executing new functions to the Realtoken DAO. These changes will allow managing special cases related to RealTokens while ensuring decentralized control to prevent abuse and total transparency.
The vote on this proposal therefore aims to validate that the DAO will take control of the execution of the RealTokens recovery functions on the RMM Wrapper, the DAO will have a verifier/security role, but cannot refuse execution if it complies with the planned process.
Motivation:
- Address specific requirements of different types of RealTokens in RMMv3
- Ensure the restitution and recovery of RealTokens in special cases (regulatory requirements, etc.)
- Guarantee the proper functioning of processes related to the life of RealTokens
- Establish decentralized control to prevent manipulation and abuse
- Total transparency on processes related to RealTokens on RMMv3
Context:
RealT offers several types of RealTokens, each with specific requirements. In order to benefit from RMMv3 with a maximum of RealToken types and meet regulatory requirements, we must be able to safely extract RealTokens from RMMv3 in cases where the investor cannot do it by their own means.
For example, DEBT tokens will need to be partially or fully burned at some point. If they are on RMMv3, we cannot burn them without creating uncollateralized debt problems.
This is why the RealToken Wrapper needs to be updated with new functionalities that allow the DAO governance to repay a user's debt in the same transaction as withdrawing the concerned realtokens.
Modifications to the RealToken Wrapper contract:
- Removal of redundant
_isRealTokenWhitelisted
verification - Gas usage optimization with a cached user token array
- Addition of new functions
repayForRecover
andrecoverByGovernance
- Removal of redundant
Transfer of execution responsibility to the DAO:
The DAO will be responsible for executing new functions on RealT's proposal
These functions will be limited to addresses with the
GOVERNANCE_ROLE
Applicable only to RealTokens, not to other RMMv3 assets (USDC and XDAI)
Control process:
- RealT will submit proposals to the DAO for executing these functions
- The DAO will review and vote on these proposals to validate execution
Implementation Steps:
- Audit of modified code by an independent third party (already completed)
- DAO vote to approve modifications and transfer of responsibility
- Update of the RealToken Wrapper contract on RMMv3
- Configuration of governance roles for the DAO
- Comprehensive testing of new functionalities
- Training of DAO members on the review and execution process
Roadmap:
- Code audit: 2-3 weeks (already completed)
- Discussions on the governance forum: 7 days
- DAO vote: 7 days
- Queue: 2 day
Budget:
No additional costs for the DAO except for transaction fees.
Financial Implications:
- Audit and development costs
- Potential increase in gas fees for certain operations
- No penalties or fees for investors who use these functionalities (possibility in the future to add fees with a new contract update)
Team:
- RealT technical team for implementation
- External auditors for code verification
Success Metrics:
- Successful implementation of contract modifications
- Absence of security issues after deployment
- Efficient and responsible execution of new functions by the DAO
- Successful resolution of special cases related to RealTokens
Alignment with Mission:
This proposal aligns with the Realtoken DAO's mission by ensuring efficient management of RealTokens while strengthening the decentralization and transparency of the ecosystem.
By controlling the execution of functions, governance demonstrates transparency and ensures that RMMv3 remains a secure and reliable ecosystem.
Key Terms:
- RMMv3: Realtoken Money Market v3
- RealToken Wrapper: Contract allowing interaction of RealTokens with RMMv3
- GOVERNANCE_ROLE: Specific role assigned to addresses authorized to execute governance functions
Points to Discuss Before Creating the Final Proposal:
- Detailed process for submission and review of proposals by RealT
- Evaluation criteria for proposals by the DAO
- Security mechanisms to prevent abuse in function execution
- In-depth training of DAO members on the implications of new functions
- Emergency procedure in case of need for rapid action
- Frequency and method of reviewing this process
- Process for communicating these changes to the community
- Reporting and transparency mechanisms for the use of these functions
CHECK-LIST: (
: under discussion /
: finalized /
: not applicable )
Proposal Summary
Motivation
Context
Implementation steps
Team
Budget / Allocation
Roadmap
Objectives
Key terms
What is your feeling about the proposal?
You can choose an option to indicate your state with respect to the proposal, this allows us to measure the general feeling, this will help to know when progress has been made If your feeling changes, for example you had questions and now the proposal is correct, you can edit your selection this allows us to visualize the progress