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
000003 - this is the event (/log) index within that transaction
However, what I observe is that the value in this segment increases across transactions and only resets to 0 on a new block. So itsems to be the event /log index within a block.
e.g. when I have 1 event per transaction, 2nd segment and 3rd segment are always equal.
According to different sources including web3js states that logIndex: Number - integer of the log index position in the block. null when its pending log. which means that the behaviour is correct but the documentation seems wrong. Since Firefly has a pluggable architecture to support other blockchain protocols, this value might be different.
Better source is the Ethereum documentation https://ethereum.org/en/developers/docs/apis/json-rpc which states the same logIndex: QUANTITY - integer of the log index position in the block. null when its pending log.
Coupling this with the transaction index allows a user to have a unique ID for an event.
docs say
However, what I observe is that the value in this segment increases across transactions and only resets to 0 on a new block. So itsems to be the event /log index within a block.
e.g. when I have 1 event per transaction, 2nd segment and 3rd segment are always equal.
If I have 2 events per transaction, then I see segment 3 increase sequentially on every event and segment 2 increases by one on every other event
Curious if the docs are wrong or whether this is a code bug.
The text was updated successfully, but these errors were encountered: