Decouple registrar actions id from Ponder
related to: #1742
Right now, the SQL table for registrar actions uses Ponder-specific checkpoint ID encoding as its primary key.
Ponder checkpoint IDs are 75 characters long:
[blockTimestamp: 10][chainId: 16][blockNumber: 16][transactionIndex: 16][eventType: 1][eventIndex: 16]
All components except eventType are general descriptors of registrar actions, while eventType is the only Ponder-specific part. To decouple it from Ponder, we want to change the ID column to remove eventType and therefore be of the following format:
[blockTimestamp: 10][chainId: 16][blockNumber: 16][transactionIndex: 16][eventIndex: 16]
This would require introducing changes to ENSIndexer to transform Ponder data appropriately.
Decouple registrar actions
idfrom Ponderrelated to: #1742
Right now, the SQL table for registrar actions uses Ponder-specific checkpoint ID encoding as its primary key.
Ponder checkpoint IDs are 75 characters long:
[blockTimestamp: 10][chainId: 16][blockNumber: 16][transactionIndex: 16][eventType: 1][eventIndex: 16]All components except
eventTypeare general descriptors of registrar actions, whileeventTypeis the only Ponder-specific part. To decouple it from Ponder, we want to change the ID column to removeeventTypeand therefore be of the following format:[blockTimestamp: 10][chainId: 16][blockNumber: 16][transactionIndex: 16][eventIndex: 16]This would require introducing changes to ENSIndexer to transform Ponder data appropriately.