# New audit scoring is live

**URL:** <https://forum.storj.io/t/new-audit-scoring-is-live/19466>\
**Category:** Node Operators\
**Tags:** audits, disqualification\
**Created:** [August 23, 2022, 7:28pm UTC](https://forum.storj.io/t/new-audit-scoring-is-live/19466 "2022-08-23T19:28:06Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [August 23, 2022, 7:28pm UTC](https://forum.storj.io/t/new-audit-scoring-is-live/19466/1 "2022-08-23T19:28:07Z")

</div>

> [@Tuning audit scoring](https://forum.storj.io/t/tuning-audit-scoring/14084/72):
>
> I’m back! After re-reviewing this whole thread, I’ve re-run the simulations with 2 significant changes: It’s fine to start with an alpha \>= 1/(1-lambda). It’s fine to reset all node reputations as a one-time change. An added point of evaluation is “how long does it take to get from a perfect score to a DQ when (apparent) data loss is suddenly 100%?” We want this to be larger than 10 audits, but probably less than hundreds of audits. Given those, I don’t see any set of parameters that does si…

What’s mean in a first glance?

- threshold is now 96% instead of 60%;
- 40 consecutive audits failures is enough to go from a perfect score to disqualification (it was 10 audits before);
- only GET\_AUDIT and GET\_REPAIR affects audit score.

---

_[View the full topic](https://forum.storj.io/t/new-audit-scoring-is-live/19466)._
