-
Notifications
You must be signed in to change notification settings - Fork 4
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
FIP 003: Lowering the staking requirements. #3
Comments
|
No, the maximum will be also 100K. This is until FIP4.
See answer 1, no, there is no benefit because you cannot stake more than 100K, That is untill FIP4.
24 hours
There is a limit on how many validators we can run since we have to iterate over them in the solidity code is several places and it uses gas. Although gas is free for the validators who runs the code, there is a maximum gas limit per block enforced by parity.
Each circle a set of validators is chosen, if there is less than a 100 validators all of them get to be chosen to the validator set of the next cycle, if there is more, a random 100 are chosen to the validator set of the next cycle. |
So I'm understanding this as:
*** Each node can only have 100k - no more, no less. If more tokens added, there is no benefit. |
What will happen to nodes that already have more than 100k staked/delegated? i.e. current nodes have 3M tokens. 2.9M delegated by Fuse. Will Fuse remove this delegation as it is not required anymore?
Am I correct in my understanding that this means you can still only stake 100k per node, but can run multiple nodes via the 'validator account' idea, and there is no limit to how many validators one can run? |
Doesn't seem all that random to me if you need 100 validators and there are only 100 validator nodes. |
@CrackerHax we select 100 max each cycle, but there can be more. See examples on the FIP description |
This sounds like there will only ever be 100 validators all together in the fuse network. |
Yes, there will be only 100 validators. |
See I don't think that is what he is saying. I think there will be unlimited amounts of validators but only 100 will be used each cycle. |
Yes, that sounds about right. |
This is what I also am saying... |
My point is if we are voting on a FIPS it needs to be written to be 100% clear and leave nothing to interpretation. |
We will pull our delegations after FIP3 so there not supposed to be a more than 100K delegation node, if there are, the consensus contract will see them as a 100K stake node.
This is FIP4 that you are talking about, and yes, you will be able to retake and basically create multiple 100K nodes. |
I'm not clear on what this means.
|
@fileflume no, the staker is who sends tokens to the contract (delegates to himself). |
@LiorRabin OK - the staker remains the staker, thats good. I'm not sure what this means.
|
That means that even if we don't pull the delegation, nodes with more than 100k total stake will be considered as 100k nodes. |
Ah, ok, I understand. Consensus contract has a max limit of 100k, so extra tokens just sit there doing nothing. As an example validator node: Reward is split: The 'extra' 50k tokens from the delegator don't count for anything. |
This should be the case, but only in the current situation which is a special one because we a higher min stake amount. After FIP-3 deployed there won't even be such an option because trying to stake/delegate over 100k will make the transaction fail. |
OK - that's clearer. Thanks. |
FIP 003: Lowering the staking requirements.
Motivation
We want to give the validator a way to actually benefit from having a lot of delegators. But for this to happen FIP4 needs to be implemented and it can take some time. FIP2 is just around the corner and it will reduce the massive rewards that validators are getting by splitting them with its delegators. So in the meantime, we want to lower the minimum staking requirements to 100K from 3M so validators won’t need delegations to stake and validate.
Suggestion
As mentioned already, lowering the staking requirements to 100K FUSE tokens exactly (no more no less). It can still be split between validator its delegates.
To do so, we need to strictly limit the number of validators to 100, and to choose randomly each cycle up to 100 validators from the eligible validators. Also, we need to keep in mind that if someone has more than 200K FUSE tokens and he wants to validate more, he needs to set up two or more validator machines by himself with a different address. This will be solved in FIP4.
Examples
The text was updated successfully, but these errors were encountered: