refactor: send block transactions before sending the blocks #12
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 is needed so we can recover from a forced restart (on daemon service upgrade for instance)
If we send the blocks first as we were doing and the service crashed or were killed by an update before the transactions it confirmed were sent to the wallet-service, the next time the service starts would start from the next block, ignoring the transactions from the latest one.
With this PR, we will send the transactions before sending the blocks, this way, the next time the daemon starts after a crash/upgrade, it will re-send the transactions from the latest block (they will be ignored from the wallet-service as they are already on the database).