This post is to make a formal proposal from the discussion around this post suggesting alternate BN activity requirements to the one proposed in the Mapping Ecosystem Changes - BN Ecosystem thread. This is being put in a separate post as to be applied in the next cycle of changes.
The original proposal had an exploit where a BN could alternate between 2 and 0 nominations each month and be fine, averaging out to an effective 1 nom/month minimum activity. This proposal aims to patch that loophole while applying a similar standard of activity as the current system.
==========================================
I am proposing:
==========================================
For example:
Following the first warning, the BN receives a message saying they need 3 more nominations before the next check to avoid removal.
Following the second warning, the BN receives a message saying they need 4 more nominations before the next check to avoid removal.
==========================================
To quote myself from the original post, this would make it so that the BN is granted some leniency in the following months if they had a month of high activity, but also cannot exploit the system by nominating extremely minimally in a specific pattern.
The original proposal had an exploit where a BN could alternate between 2 and 0 nominations each month and be fine, averaging out to an effective 1 nom/month minimum activity. This proposal aims to patch that loophole while applying a similar standard of activity as the current system.
I am proposing:
- EVERY MONTH, the BN's activity for the previous THREE MONTHS is checked automatically.
- If a check falls below 6 NOMINATIONS, the BN receives an automated activity warning telling them how many nominations they need for next month's check to reach 6.
- If two consecutive activity checks fall below 6 nominations, the BN is removed for inactivity (pending review by NAT incase of extenuating circumstances).
- There are NO ACTIVITY CHECKS for the FIRST TWO MONTHS when a BN (new or returning) joins the BNG.
- The BN receives a warning if a check falls below 9 NOMINATIONS.
- The BN receives a warning if a check has less than 3 NOMINATIONS IN ANY PROFICIENT GAMEMODE
- Automated warning messages tell the BN how many nominations they need to reach 9 before the next check, and/or, if applicable, how many nominations needed in each proficient gamemode.
For example:
Month | 1 2 3 4 5 6 7 8 9 10
-----------------|------------------------------
Nominations | 10 1 1 2 3 10 1 1 1 2
|
3-Month Activity | __ __ 12 4 6 15 14 12 3 4
^ ^ ^
warn warn removalFollowing the first warning, the BN receives a message saying they need 3 more nominations before the next check to avoid removal.
Following the second warning, the BN receives a message saying they need 4 more nominations before the next check to avoid removal.
To quote myself from the original post, this would make it so that the BN is granted some leniency in the following months if they had a month of high activity, but also cannot exploit the system by nominating extremely minimally in a specific pattern.