-
Notifications
You must be signed in to change notification settings - Fork 19
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
Feature: Bulk update ValidatorHistoryAccounts more efficiently #4
Labels
good first issue
Good for newcomers
Comments
buffalu
changed the title
Find the most efficient way to update vote accounts in the smallest number of transactions
Bulk update ValidatorHistoryAccounts more efficiently
Dec 19, 2023
buffalu
changed the title
Bulk update ValidatorHistoryAccounts more efficiently
Feature: Bulk update ValidatorHistoryAccounts more efficiently
Dec 19, 2023
Hey @buffalu, I can take a look at this. Regarding an address lookup table integration, I'll need to know how many validator_history_account/vote_account are currently in use and what the expected evolution of the number of those accounts is. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Running a keeper for StakeNet isn't as efficient as it could be. There are likely too many transactions being sent on-chain.
Describe the solution you'd like
Find a better way to upload transactions by bulk writing transactions or potentially leveraging address lookup tables.
Note
Please comment below in the issue to claim this task.
The text was updated successfully, but these errors were encountered: