-
Notifications
You must be signed in to change notification settings - Fork 9
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
Wrong blocksizes and fees calculations for Monero #2
Comments
Thanks @HardenedSteel for the report. Indeed prediction calculations for Monero seem wrong on various levels. I just watched 2 consecutive blocks (3100761 and 3100762) being filled and confirmed, with wrong sizes, number of transactions and fees distribution. Both showed ~670 KB and ~70 transactions, with varying fees around the 20-320 Nanomonero range). That said, buses being all fully loaded, does seem correct despite their contents being wrong. Though there should be a third as many lined up. Suggestions, ideas or PRs are welcome 🙏 Other reports of flawed calculation: |
This Python code can help: https://github.com/spackle-xmr/Dynamic_Block_Demo |
Nice, thanks! Another cool project with charts: https://xmr-tw.org/xmr-eta/ (from a Reddit comment) |
Thanks I looked up but they also have same issue with Txstreet, opened an issue at their repo. If the issue isn't clear enough; Txstreet needs to calculate block size using dynamic block size algorithm. At this moment it simply just assumes block size is |
This sort of visualization is a bit more art than science. I am no great artist, but I have a few ideas on what could be done... Assuming:
I might propose:
I can offer my input on calculations if you want the buses to change size dynamically as transactions come in (or something similar). That would be a fairly perfect representation of what is happening. I have not looked at the code and I do not know how difficult such a change would be. |
Changing the percentage values would be helpful; median block size should be 100% (instead 50%) and maximum allowed blocksize should be 200% (instead 100%). as a result the user can understand blocks are getting bigger when they see the bus load is over 100%. |
[Cross-posting from this txstreet/txstreet issue by @HardenedSteel]
The text was updated successfully, but these errors were encountered: