New audit scoring is live

[BrightSilence]

Some more highlights.

This is what scores would do over time with 15% data loss, before the implemented changes.

@BrightSilence

This is a graph of scores with 4% data loss with the new changes.

@BrightSilence

Note: the threshold line is at 95 here. This was bumped to 96 to better match the intended allowed data loss.

Here are some tests ran with the new settings in a simulation script built by @thepaul .

@BrightSilence

Tuning it even tighter by raising the threshold to 96% and you get exactly the result you wanted. No nodes disqualified at 2% data loss, all nodes disqualified at 4% data loss.

./simrep.py -d 0.02 -r 10000 -x 3000 -l 0.999 -w 1 -q 0.96 -a 1000 -b 0 -g 50
with 2.00% data loss, 0.00% of runs hit dq (after 0.00 rounds on avg)

./simrep.py -d 0.03 -r 10000 -x 3000 -l 0.999 -w 1 -q 0.96 -a 1000 -b 0 -g 50
with 3.00% data loss, 21.73% of runs hit dq (after 6275.94 rounds on avg)

./simrep.py -d 0.04 -r 10000 -x 3000 -l 0.999 -w 1 -q 0.96 -a 1000 -b 0 -g 50
with 4.00% data loss, 99.77% of runs hit dq (after 2906.48 rounds on avg)

Ok, I guess 99.77% isn’t all, but I hope you’ll forgive me that last 0.23%.

That script can be found in this post by him: Tuning audit scoring - #16 by thepaul

And these are the changes we eventually landed on for those who want to dive into the math:

@thepaul

So the new change plan is:

1. Change lambda to 0.999
2. Use alpha=1000, beta=0 for new nodes
3. Reset all node reputations to alpha=1000, beta=0
4. Change the DQ threshold to 0.96