-
Notifications
You must be signed in to change notification settings - Fork 798
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
Update confirmation_info RPC call to include representatives final votes for monitoring purposes #3734
Update confirmation_info RPC call to include representatives final votes for monitoring purposes #3734
Conversation
The code changes look good to me except that previously the list of representatives was sorted whereas after this change it will not be sorted anymore. The documentation does not mention sorting but there might be services that empirically learned that it is sorted and expect it to be sorted. So if we want to be backwards compatible, we should sort the list of representatives. If we decide to sort, or not, we should update the documentation to reflect that. However, from a conceptual point of view, this change is not as good as it could be. What do you guys think? |
To clarify, I am saying let's not change the response to representatives option. |
I am in favor of the suggestions for a new |
Change looks good, but I also agree that a |
Test Results for Commit dfc3d9aPull Request 3734: Results Test Case Results
Last updated: 2025-03-27 19:37:28 UTC |
e5141e7
to
8e28d7b
Compare
8e28d7b
to
dfc3d9a
Compare
Restored sorting and added tests. Merging. |
This is the same as #3618 without the unrelated commits.
This PR adds a list of representatives_final to the confirmation_info RPC which are representatives which have voted with final votes.
It's backwards compatible. This also adds a check for final_tally in the tests which was already implemented on the RPC previously.