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 a transaction is issued, it includes a block hash. The chain checks that the transaction's block hash is at most transaction_validity_period blocks old. This check requires BlockHeader to exist for the hash (not guaranteed by epoch sync currently), and requires BlockHeight to exist for the height (to check for canonical-ness).
In a case I saw, the former exists somehow (even though it was before the epoch sync boundary) but the latter does not. Not sure why that is the case - I'm confused why the header existed in storage at all.
When a transaction is issued, it includes a block hash. The chain checks that the transaction's block hash is at most
transaction_validity_period
blocks old. This check requiresBlockHeader
to exist for the hash (not guaranteed by epoch sync currently), and requiresBlockHeight
to exist for the height (to check for canonical-ness).In a case I saw, the former exists somehow (even though it was before the epoch sync boundary) but the latter does not. Not sure why that is the case - I'm confused why the header existed in storage at all.
Either way, this needs to be properly addressed.
@bowenwang1996 Any ideas?
The text was updated successfully, but these errors were encountered: