-
-
Notifications
You must be signed in to change notification settings - Fork 121
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
Reduce the number of requests to poll a Monero daemon [$800] #110
Comments
There is a bounty on this issue, the amount is in the title. The bounty will be awarded to the first person(s) who resolves this issue. Read the full conditions in the 'bounties.md' file. If you are starting to work on this issue, please write a comment here, so that we can assign the issue to you and avoid duplicated work. |
I will make a serious attempt to implement this, over the next 3 calendar weeks or so because working on spare time. First looks into the existing code of the RPC calls to be replaced by this single new call and their use in |
Thanks for the assignment! A very first question: Where do I best place questions that I run into with this? Right here, or in some Haveno IRC / Matrix channel? |
Thank you for working on this :) |
This was merged into the release branch of monero-project with monero-project/monero#8800 by @rbrunner7. |
Thank you very much, @woodser, for paying out that bounty! Just received it. It was nearly 2 years ago that I took on this work, and I am grateful that the bounty was honored nevertheless. I am also glad that I could made a small contribution towards making Haveno a success. |
"Currently, wallets make up to 4 requests each time a wallet polls a daemon: get_info, get_transaction_pool_hashes, get_transactions, and get_blocks.bin.
As a result, daemons must service up to 4 requests for each client poll, and the user may experience a noticeable delay before their wallet even starts to sync blocks if their connection is slow."
See the issue on the Monero repo for the full details: monero-project/monero#7571
The text was updated successfully, but these errors were encountered: