Limit the timeframe for created blocks to be accepted about rivine HOT 8 OPEN

Proposed timeframe ?! Is still still safe to do with a live chain? if so, how?

cc @robvanmieghem, @LeeSmet

from rivine.

Current time frame on launched standard (network) is:

• FutureThreshold: 1 hour
• ExtremeFutureThreshold: 2 hours

This is not limited enough?!

from rivine.

Need to write down a motivation to why big time limits would ever be desired. Same for shorter ones.

from rivine.

I think we can simply close this as wontfix, @robvanmieghem agree or disagree?

from rivine.

FutureThreshold can't be set to high, since the block creator only calculates 10 seconds up front. But anyone with block stakes can just manually compile the daemon and set this value to the same as futurethreshold, giving them an advantage. So this should ideally be limited to these 10 seconds, while allowing a small window for clock skew between different nodes, since we can't assume that their clocks are perfectly in sync.

At the same time, we need to consider that it is currently possible to try and find a block for a timestamp which has already come to pass.

from rivine.

@robvanmieghem can you please do some research and tests, as to define the missing info for this issue.

from rivine.

Any thoughts what to do with this issue @robvanmieghem? Any leads that we could perhaps look into, if you have no time to do it. As it's one of those issues that seems to keep being moved from one milestone to another.

from rivine.

This is needed until blockcreators are not to be trusted, moved it to backlog until depending projects need it.

from rivine.