RFC: Standardized + Gov-Friendly Collator Staking/Deposit through EVM+ Smart Contracts #1481
Replies: 3 comments 2 replies
-
I really like the direction of this RFC and I know many of us have been waiting to be able to vote with our staked and deposited RING. I do have a couple questions and thoughts around what is being considered.
Very excited for this change over all. |
Beta Was this translation helpful? Give feedback.
-
Love it. Governance participantion first. Second very good imho to prepare for liquid staked asset. My questions:
Will we now be able to nominate to more collators then one?
According to this paragraph there seem to be two tokens:
My question is how will this play out to already locked Ring? For example I have just locked a month ago some Ring for three years? I have over 1M Ring locked so will this automaticly be put under Collator staking contract?
This one was already asked by Jesse. But we will still mint Kton for deposit lock? And time periods 1-36 months will remain? Thank you for your hard work on this🏆 |
Beta Was this translation helpful? Give feedback.
-
This proposal aims to reimplement Collator Staking and Deposit functionalities through EVM+ smart contracts to achieve two significant objectives:
Standardize Collator Staking and Deposit to ensure better compatibility with ERC20 and ERC721 standards. This integration will enhance our infrastructure and ecosystem interactions, for instance, making the system more accommodating to Liquidity Staking Tokens (LSTs). Additionally, it allows transforming deposits into NFTs, which can be transferred and traded in the NFT market.
As prerequisite to the next-generation governance system, transitioning Collator Staking and Deposit to smart contracts will facilitate the adoption of standardized governance models like those provided by Tally/OpenZeppelin Governor contracts. This shift will make on-chain governance more intelligent and standardized.
For Collator Staking, a critical step during runtime is the collator selection and ordering for new sessions, which can now be managed within a smart contract. At the beginning of a new session, the runtime pallet will directly retrieve information from the configured Collator Staking smart contract(Note: When implementing, fallback to previous/backup set is necessary if new set reading is empty or error).
Following DIP-6, Collator Staking has been simplified; however, it still involves RING and Deposit components. To simplify implementation, encapsulating them within smart contracts is advantageous. Similar to DIP-5, a migration phase of 30 to 60 days should be established to ensure a smooth transition, allowing users to migrate their existing staking to the new system.
More specifically, we will first implement a Collator Staking contract where users can stake/unstake RING and nominate collators.
Additionally, a Deposit contract will replicate the functionality of the original deposit module, where deposits are converted into an ERC721 NFT Token. Users can then use this NFT for further staking/unstaking in the Collator Staking contract.
Support for LSTs will align with standard practices in other ecosystems, such as implementing a Liquid RING Collator Staking contract. Users can engage in staking and unstaking through this contract, which will issue an ERC20 stRING token upon staking. This token can be transferred, traded, or used to add liquidity in DEXes. Developers within the ecosystem can also create customized versions.
Similarly, a Liquid Deposit Collator Staking version will be developed for deposit staking, allowing users to obtain an NFT voucher that can be transferred or traded while staking.
For participation in the next-generation governance system, the Liquid RING Collator Staking Token and Liquid Deposit Collator Staking Token will be highly conducive, merely requiring configuration of voting weights in the Governor contract.
Please have @AurevoirXavier @hujw77 @wuminzhe @boundless-forest attentions to this RFC and prepare for subsequent DIPs, engineering implementations, docs and education. Thank you.
Beta Was this translation helpful? Give feedback.
All reactions