-
Notifications
You must be signed in to change notification settings - Fork 790
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
Rebalancing buckets the reflect natural transaction ranges. #3980
Conversation
…^88-2^120 raw. Testing min/max bounds of amount and removing logging message.
It would be nice to have a graph that showed the distribution. |
Not a graph, but here's a table that may help future readers:
Created with the following Python3 script:
|
@dsiganos Here's a graph of the distribution (the y-axis section below 1E-4 nano of bucket 0 is not shown for clarity) |
* Update protocol-reference.md with V24 bucket info Updating from 129 to 62 buckets, per: nanocurrency/nano-node#3980 Updating from current block balance to max of current or previous, per: nanocurrency/nano-node#4022 * Update protocol-reference prioritization notable functions Update protocol-reference.md Election Scheduler section with election_scheduler::activate notable function & adjust wording for pre vs post V24 clarity * Update protocol reference link to tagged vs develop Update protocol reference link to a more static tagged release instead of the develop branch (which can change)
@1401Ger damnt this is impressive, would be hilarious to have a grahic with the same scale and all that shows the old bucket distribution to show just how comically sized the old system is. |
wait is this 2^0 (1 raw) or 0 raw? |
@My1 I'm pretty sure 0 raw would be an invalid send transaction so bucket 0 should start at 2^0 = 1 raw. |
You can still change your rep even if it's kinda useless. And we wouldn't like this to suddenly cause problems |
* Update protocol-reference.md with V24 bucket info Updating from 129 to 62 buckets, per: nanocurrency/nano-node#3980 Updating from current block balance to max of current or previous, per: nanocurrency/nano-node#4022 * Update protocol-reference prioritization notable functions Update protocol-reference.md Election Scheduler section with election_scheduler::activate notable function & adjust wording for pre vs post V24 clarity * Update protocol reference link to tagged vs develop Update protocol reference link to a more static tagged release instead of the develop branch (which can change)
This change re-balances the scheduling buckets to more closely match naturally occurring balance ranges.
This change approximates a normal distribution around 2^88 raw (Ӿ0.0003) through 2^120 raw (Ӿ1,300,000) with amounts out of this range getting a single bucket and amounts within this range getting an increased amount of prioritization.