Separate KTON Staking from Collator Staking while keeping incentive for ring pool and kton pool unchanged. #1393
Replies: 8 comments 5 replies
-
Very interesting suggestion, I have a few questions how this would work and if I understand it well. How will new KTON be minted? Will original collator staking remain the same? With 1-36 months locking and this will still influence the ammount of minted KTON but have no influence on getting more Ring? And if I understand correctly independant Kton staking will share its Ring rewards in way already discussed economic incentives excluding collators share. My only doubt is if it will be worth for collators and if their commisions will cover the costs and really be entierly sufficient. But it is up to them to share their opinion here. Other then that this is good idea to remove POWER and this will be really rewarding for KTON holders. |
Beta Was this translation helpful? Give feedback.
-
depositing ring into a term lock,to get kton isnt staking, its just agreeing to lock it down for a term period.so this recommendation he is making shouldn't have any impact on the creation of additional KTON. I like this suggestion. would be interested to hear other viewpoints on this. |
Beta Was this translation helpful? Give feedback.
-
I really like this change as I have found over the years that Power can be confusing to new users. Doing this will bring more clarity to staking. Would it be possible to add to the staking dashboard the total number of RING staked and total number of KTON staked? This would help users understand their expected rewards and returns using a spreadsheet I am working on. With respect to RING rewards would a delegators ratio be based on total number of RING staked or the number of RING staked on the collator they are delegating to? |
Beta Was this translation helpful? Give feedback.
-
not only for new users, ive been staking since mainet lauch,and i still
dont have a firm grasp on it.I dont really think a spreadsheat here would
be much helpful. power seems to be such a fluid thing,a new person coming
in and staking,or someone unbonding, it changes the numbers. and theres no
counting blocks befor they hit them.
…On Wed, Jan 31, 2024 at 1:11 PM JDubs ***@***.***> wrote:
I really like this change as I have found over the years that Power can be
confusing to new users. Doing this will bring more clarity to staking.
Would it be possible to add to the staking dashboard the total number of
RING staked and total number of KTON staked? This would help users
understand their expected rewards and returns using a spreadsheet I am
working on. With respect to RING rewards would a delegators ratio be based
on total number of RING staked or the number of RING staked on the collator
they are delegating to?
—
Reply to this email directly, view it on GitHub
<#1393 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJDNSYRFBKUJHX2U6S5ZHHLYRKJMZAVCNFSM6AAAAABCLNZTJ2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGMRVHAZDE>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
Switching from the old Collator KTON Staking to the new KTON Staking will undergo a 30-day transition period. During this period, the Power of KTON will linearly decrease to zero. The incentives for the old KTON Pool in Collator Staking will also be reduced accordingly. The reduced portion will be transferred to the new KTON Staking until the transition period is complete. The old Collator Staking will then undergo a Runtime Migration to return the KTON in the old KTON Pool to the users, completing DIP-5. darwinia-network/DIPs#15
|
Beta Was this translation helpful? Give feedback.
-
Could there be a mechanism integrated into staking to enable automatic locking of rewards for a specified time period, with the option for KTON rewards to be automatically added to our stake, eliminating the need for manual intervention each time? It would be convenient to have the choice to put staking on autopilot. The ability to accumulate rewards and trigger automatic locking when they reach a predetermined amount, with KTON rewards seamlessly staked, would save considerable time. Not everyone can regularly check and manage their staking activities. Having the option to periodically check in to adjust delegation if necessary would be beneficial. |
Beta Was this translation helpful? Give feedback.
-
Generally, a system can have multiple Staking mechanisms coexisting, each with its own incentive purposes. However, Darwinia's current Collator hybrid Staking system has introduced many problems. By mixing different incentive goals together, the system becomes difficult to understand. It also forces these incentives to be bound together, leading to constrained actions, which is a poor design.
The current Collator Staking consists of the ring pool and kton pool, each sharing 50% of the power. While they help in selecting the Collator List, they also share a total of 40% of the new issuance RING incentives, which means 20% each from the new issuance RING.
It is suggested to separate the KTON pool from the Collator Staking, creating an independent KTON Staking module that directly shares 20% of the new issuance RING incentives. The original Collator Staking would then be entirely made up of the RING pool, helping to select the collator list while also sharing the same 20% of the new issuance RING incentives as before. With these changes, KTON Staking will gain more visibility than before, enhancing the effectiveness of incentives. Collators will no longer share commissions from the KTON pool, but considering their role in the system is primarily to maintain liveness, the commission incentives from the RING pool should be entirely sufficient. Additionally, the confusing and hard-to-communicate concept of Power in the current Collator Staking can be dismissed. Clarity in naming and concepts is crucial and will aid in community discussions and in clarifying viewpoints. It’s also worth re-emphasizing that the economic incentives for both the ring pool and kton pool are intended to remain the same as they currently are, to avoid discussions related to the amount of incentives.
Note: Engineers should be reminded to pay attention to the code related to account migration from 1.0 to 2.0, ensuring proper handling and awareness of the above changes.
Beta Was this translation helpful? Give feedback.
All reactions