enhancement: store raw data for unknown transaction kinds in order to capture them so they can be parsed later #183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes the behavior for
unknown
transaction kinds so that they capture the underlying raw data into thedata
column, allowing later analysis & possible parsing in the future without losing necessary data that might get pruned from the node.Additionally, I've added all existing wasms from the
namada-sdk
to the checksums, so that even if they aren't supported yet in thetransaction
indexer as a known kind, they will at least identify theirname
.Finally, here I've introduced
on_conflict
when insertinginner_transactions
andwrapper_transactions
to make it quite a bit easier to perform some maintenance on an indexer database by simply updating thelast_processed_block
incrawler_state
and runningtransactions
to re-crawl them. (In the future, this could be improved even more by offering a command-line option to re-crawl specific blocks.)