-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Decrease block time threshold #1232
Comments
Maybe the formula should be related to the number of verificators and the time per block, what do you think? @neo-project/core @neo-project/ngd-shanghai @erikzhang |
@shargon, for me this is expected. Not a bug. If this happens, NEO holders should vote against. |
A malicious CN can send the chain to 2020 in 2019, this is not expected.
Vote is not a solution, the protocol must protect the network if is possible. |
Isn't this one kind of metric that we can use to judge node health? I agree that we should not let nodes create blocks too much in the future. |
But what do you propose, watch and monitoring the CN in order to force a vote if this happens? |
Summary
Currently the threshold for PrepareRequest is 10 minutes, if a malicious CN propuse a block that come from the near future (10 minutes more), it will be accepted. Next blocks will be proposed by the others trusted CN from the future too
neo/neo/Consensus/ConsensusContext.cs
Line 286 in f1d6434
So next round, this malicious CN could propose another block, and step by step move the chain to the future
For 7 CN this should be the scenario (CN1 malicious one):
First round:
Second round
Do you have any solution you want to propose?
Reduce the threshold to 1 or 2 minutes.
Where in the software does this update applies to?
The text was updated successfully, but these errors were encountered: