-
Notifications
You must be signed in to change notification settings - Fork 30
SWIP-41: Stake Registry Update Queue #79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
this lgtm and a very nice SWIP one wrinkle is that the height decreases may not exactly work like this within the neighbourhood balancing SWIP itself, and also that without that there will not be any coherent signal of whether height would vary. this is dependent on a current valid chunk count which is not visible onchain in the current incarnation. i would argue for the height aspect to be removed from this initial implementation as it would remove some unusable complexity and that is always a good thing @zelig wdyt? other than that gtg from my corner pending final check and wrangle over the details |
|
As discussed with @0xCardiE I'm now planning to adjust this to make it co-dependent with SWIP-40, which simplifies some things.
Also need to think a little bit about a "principled" approach to setting the parameters. |
|
ok! suggest we close this and move into 40 if you concur? |
I think I can structure this so 40 and 41 are cleanly and logically separated. It may be useful to keep them as separate documents since they are conceptually different and may have different upgrade trajectories. Give me a week to figure this out. |
…. Factor parameter setting into separate SWIP.
Seeking feedback from SC and bee eng team on implementation and interface.
The main reason for prioritising this SWIP is to provide a delay/queue functionality for stake position changes wanted by withdrawable stake (#77). This SWIP can be introduced as a dependency for the latter in order to institute a delay.