Internal: store tx_hash in rejected messages table #459
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
odesenfans
force-pushed
the
od-include-tx-hash-in-rejected-messages
branch
from
f89162b
to
eb6e49a
Compare
Problem: if a confirmed message is rejected, we lose the tx hash information. Solution: store the tx hash as a separate column.
odesenfans
force-pushed
the
od-include-tx-hash-in-rejected-messages
branch
from
eb6e49a
to
7e6118a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem: if a confirmed message is rejected, we lose the tx hash information.
Solution: store the tx hash as a separate column.