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
Currently BlockHeader. first_transaction_consensus_time is set in startRound. It looks only at the uiser transactions in the Round and sets the field.
But that field should represent the first transaction in the block, which could be a preceding child transaction or TSS transaction or staking transaction.
Solution:
Set the field lazily after the first transaction that will be written to the block is decided
Testing:
Unit tests
Improve validator to see if this value is set on each block that has user transactions. Also validate if that is same timestamp as the first transaction inside the block
The text was updated successfully, but these errors were encountered:
Neeharika-Sompalli
changed the title
Set the BlockHeader. first_transaction_consensus_time lazily
Set the BlockHeader.first_transaction_consensus_time lazily
Jan 13, 2025
Currently
BlockHeader. first_transaction_consensus_time
is set instartRound
. It looks only at the uiser transactions in theRound
and sets the field.But that field should represent the first transaction in the block, which could be a preceding child transaction or TSS transaction or staking transaction.
Solution:
Testing:
The text was updated successfully, but these errors were encountered: