(VDB-1286) Add LogMake event transformer#161
Conversation
| header_id integer not null references public.headers (id) on delete cascade, | ||
| address_id integer not null references public.addresses (id) on delete cascade, | ||
| offer_id numeric, | ||
| pair character varying(66), |
There was a problem hiding this comment.
pair on LogKill is the same as it is here on LogMake where it's pay_gem and buy_gem packed together. Storing it as is as a varchar makes sense to me, but was just curious if you were knew why pair was stored like that, since we have pay_gem and buy_gem already on this event. 🤔
There was a problem hiding this comment.
My only thought is maybe a user would want to filter logs by the pair and hashing provides a consistent data structure that's easy to reproduce in various clients/ecosystems but I'm not sure 🤔
| ) | ||
|
|
||
| const OfferId event.ColumnName = "offer_id" | ||
|
|
| Data: hexutil.MustDecode("0x000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc20000000000000000000000006b175474e89094c44da98b954eedeac495271d0f0000000000000000000000000000000000000000000000037d73b4e66fa60000000000000000000000000000000000000000000000000304f0cf4f5072f08000000000000000000000000000000000000000000000000000000000005e3e55fc"), | ||
| BlockNumber: 9440502, | ||
| TxHash: common.HexToHash("0xb2f2f13a6ef0d1d6dd153d1a019929a31799498dcb1c100e04695fc0e95b9e58"), | ||
| TxIndex: 1772, |
There was a problem hiding this comment.
Silly question, but where did you find the TxIndex and the log Index? I think I used to find them on etherscan but didn't see them recently.
There was a problem hiding this comment.
Yeah same found on Etherscan but think I'm doing it wrong 😅
The transaction has a Nonce | Position field and I think we want to use Position for tx index (but I used Nonce, whoops!).
And then the events on the transaction have a green circle to the left that I think is the log index:
2f98c69 to
20e4246
Compare
20e4246 to
dc0ec99
Compare
No description provided.