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
The amount of consumed block gas is used here to uniquely identify the position of a transaction in a block.
Is it possible that a transaction could consume zero gas, leading to a collision (that tx and the tx that follows will have the same "absolute index")?
The text was updated successfully, but these errors were encountered:
In theory that is possible, but a zero gas transaction is inherently problematic, since it can be used for spamming and potentially a DoS, so transactions shouldn't be zero gas in the first place.
Also, this is just used for metadata on the contract history, so it's not critical if this were to happen.
Looks like a better method to get a transaction index was introduced at some point.
Let's use this as an opportunity to explore switching the contract history over to that too.
The amount of consumed block gas is used here to uniquely identify the position of a transaction in a block.
Is it possible that a transaction could consume zero gas, leading to a collision (that tx and the tx that follows will have the same "absolute index")?
The text was updated successfully, but these errors were encountered: