Implement dynamic block time #27

Closed
opened 2025-12-28 17:07:41 +00:00 by sami · 1 comment
Owner

Originally created by @roman-khimov on GitHub (Jun 23, 2025).

See https://github.com/neo-project/neo/issues/4018. The only thing I'd like to note as an implementation detail is that we don't need a full subscription to memory pool events. Rather a special channel that is closed once is sufficient for the purpose (or a stable channel between two components that accepts a single event per request (passed to mempool once and requested as needed), depends on which one is easier to implement for mempool/consensus sync).

Originally created by @roman-khimov on GitHub (Jun 23, 2025). See https://github.com/neo-project/neo/issues/4018. The only thing I'd like to note as an implementation detail is that we don't need a full subscription to memory pool events. Rather a special channel that is closed once is sufficient for the purpose (or a stable channel between two components that accepts a single event per request (passed to mempool once and requested as needed), depends on which one is easier to implement for mempool/consensus sync).
sami 2025-12-28 17:07:41 +00:00
Author
Owner

@roman-khimov commented on GitHub (Jun 24, 2025):

And MinTime is not really needed as a name, old one works fine for it (for compatibility).

@roman-khimov commented on GitHub (Jun 24, 2025): And `MinTime` is not really needed as a name, old one works fine for it (for compatibility).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/dbft#27
No description provided.