-
Notifications
You must be signed in to change notification settings - Fork 117
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
8. feat(state): add a query function for transparent address balances #4097
Conversation
e69c70a
to
a557a55
Compare
b8cdc92
to
1059362
Compare
dc3050b
to
ef50f8b
Compare
ef50f8b
to
bf7e4ae
Compare
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.
Looks great! 🎉
Full validation sync failed due to #3991, but we stopped requiring that check due to #4114: |
@Mergifyio update |
Mergify hung on "evaluating rules" for 90 minutes: |
@Mergifyio refresh |
It has already been cloned by the watch receiver
bf7e4ae
to
70bb253
Compare
Full validation sync failed due to #3991: I'll re-run the job. |
Now it's failing with #4114, sigh At least that job isn't required any more. |
Motivation
This PR adds a state query function for the
get_address_balance
RPC in ticket #3157.We still need to add a state request and a RPC method.
Specifications
RPC:
But only the arguments and fields in ticket #3157.
Designs
There are a few tricky parts of this PR:
We could try to hold a database read snapshot, but that could cause locking issues. Instead, I just retry a few times if the balance might have changed. (If the query fails for this reason, Zebra is still syncing, and the results would probably be wrong anyway.)
Solution
Related changes:
Review
I think @jvff is writing the RPC side of this query.
Reviewer Checklist
Follow Up Work
Do the state queries for the other address RPCs.