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
{{ message }}
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
If two identical transactions are in the pool it may be possible to switch the order in which they are "mined" depending on how many times the pool is sorted.
We may need to sort by a secondary key, the from address may work without adding any additional properties to the transaction -- though this would bias transaction ordering based on the address' lexicographic sort order -- unless we hash the address first, which seems like unnecessary extra work ... or we could used an FIFO-based sort index for this.
The text was updated successfully, but these errors were encountered:
If two identical transactions are in the pool it may be possible to switch the order in which they are "mined" depending on how many times the pool is sorted.
We may need to sort by a secondary key, the
from
address may work without adding any additional properties to the transaction -- though this would bias transaction ordering based on the address' lexicographic sort order -- unless we hash the address first, which seems like unnecessary extra work ... or we could used an FIFO-based sort index for this.The text was updated successfully, but these errors were encountered: