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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reserved address pool #531
Reserved address pool #531
Changes from all commits
c05dba3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NIT: Not sure what's the best way to delete data in the context of real-type sync.
IMO
DELETE
statements could lead to edge-cases when 2 SDK instances sync, one has the data (here, thereserved_address
row) and the other doesn't. Depending on the ordering and timing, it could be that one or the other is treated as "the truth".In contrast, sync would be more resilient if we delete by setting a flag, i.e.
reserved = false
. Any such conflict during synchronization could then be resolved simply: if any of the two havereserved = false
, then its false.@roeierez @hydra-yse what do you think, does this matter? Or it makes no difference for real-time sync?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reserved address table currently only stores MRH addresses used in receive swaps. These are the two cases where a delete would occur:
Also to note is that the
last_derivation_index
from the cache needs to be synced.Maybe it's best to add this as a task of the real-time sync tracking issue