// Derived fields. These fields are filled in by the node // but not secured by consensus. ... // index of the log in the block Index uint `json:"logIndex" gencodec:"required"`
So next time I am looking at
eth_getLogs the particular
transfer could appear with different
I am looking for a way to uniquely identify a particular incoming transfer, many transfers can appear in the same transaction and I need a way to store them and make sure there is no duplicates when worker goes through backlog again.
Simple guess is to use unique composite index for fields: (txid, to, logIndex), but that comment in
log.go is confusing me.
Parity returns is as
transactionLogIndex, so may I assume it will always be the same in further responses and even if chain reorganises and tx will be included in another block?