You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When collecting ClientTransactions the routine makes sure that the block doesn't get too big. For this to work it applies one ClientTransction after another to the current. However, two things are not done properly:
Every ClientTransaction is applied to a clean state, not taking into account eventually queued up ClientTransactions
It uses the wrong timestamp for the block, now, where it should be the time set by the leader later
This means that the size of the final block might be off:
a ClientTransaction that depends on another ClientTransaction in the same block might produce fewer or more StateChanges
a ClientTransaction that creates a different set of StateChanges depending on the time will produce fewer or more StateChanges
Anyway, the attack surface is deemed very little, but it's still written down here...
The text was updated successfully, but these errors were encountered:
When collecting
ClientTransaction
s the routine makes sure that the block doesn't get too big. For this to work it applies oneClientTransction
after another to the current. However, two things are not done properly:ClientTransaction
is applied to a clean state, not taking into account eventually queued upClientTransaction
snow
, where it should be the time set by the leader laterThis means that the size of the final block might be off:
ClientTransaction
that depends on anotherClientTransaction
in the same block might produce fewer or moreStateChange
sClientTransaction
that creates a different set ofStateChanges
depending on the time will produce fewer or moreStateChange
sAnyway, the attack surface is deemed very little, but it's still written down here...
The text was updated successfully, but these errors were encountered: