near-indexer-for-explorer
near-indexer-for-explorer copied to clipboard
Expose information about genesis records
Currently, we index genesis into the regular tables, but then it is hard to reason whether the data was initially included in the genesis.
For example, we store genesis accounts into accounts
table with created_by_receipt_id
set to NULL, but if later the account gets re-created (deleted and created once again), we lose that created_by_receipt_id IS NULL
characteristic. Well, the same problem is applicable to all the re-creation events since we lose track of the previous create/delete checkpoints, so we do not represent the history correctly. One of the solutions is to have an extra table as we had access_keys
in the indexer-for-wallet, where we recorded each add/delete event independently.
@khorolets How do you feel about having the "events" tables for accounts, access keys, and contracts (deploy contract / delete account)?