-
Notifications
You must be signed in to change notification settings - Fork 37
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
feat: Make sync compatible with node's next
#758
Conversation
5485737
to
5176cf7
Compare
The new |
.unwrap() | ||
.try_into() | ||
.unwrap(), |
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.
Can this unwrap
s be replaced with RpcConversionError
s? Thought I don't know if is worth considering that this will not last long.
async fn apply_nullifiers( | ||
&self, | ||
note_updates: NoteUpdates, | ||
transactions_to_discard: Vec<TransactionId>, | ||
) -> Result<(), StoreError>; |
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.
We could use a comment here, saying that this is temporary
CHANGELOG.md
Outdated
@@ -12,6 +12,7 @@ | |||
* [BREAKING] Refactored authentication out of the `Client` and added new separate authenticators (#718). | |||
* Re-exported RemoteTransactionProver in `rust-client` (#752). | |||
* Moved error handling to the `TransactionRequestBuilder::build()` (#750). | |||
* [BREAKING] Added starting block number parameter to `CheckNullifiersByPrefix` (#749). |
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.
Maybe mention that nullifiers were removed from SyncState? Also this references a closed PR
Makes the sync process compatible with
next
until the core changes are updated through #650 and #751