Force YAMv2 Mitigation to YAMv3 to Keep Community Consensus United

Basic Summary/Abstract

YAMv2 and YAMv3 are separated from each other, as this proposal is written, the price of v2 10 times of v3 which is doubled the ScalingFactor of 5.05. It will cause YAM community consensus splitted into two groups which MUST be stopped asap.

This proposal is to force YAMv2 mitigated to YAMv3 in the specified time window. If it is not done in the mitigation in the time-line, then a punished discount rate will apply to the mitigation process. If late than the specified time-line, the mitigation process will be prohibited.

Motivation

Make Yam Community Consensus United Again!

Risks

The very little risk for yam community, the benefit is we could keep the YAM consensus a ONE, not two.

Specifications

To force YAMv2 to mitigate to YAMv3, we should specify a final date. In this proposal, the normal mitigation transition date is the last day of Oct (10/31/2020 12:00 pm UTC). If missing the time-line, the following punishment rules will be applied to keep YAM consensus as ONE:

  • in 10days(11/10/2020 12:00 pm), the 30% discount rate will be applied for the mitigation process which means YAMv2 could get YAMv3 numbers as, YAMv2 * ScalingFactor * (1 - 0.3).

  • in 20days(11/20/2020 12:00 pm), the 50% discount rate will be applied for the mitigation process which means YAMv2 could get YAMv3 numbers as, YAMv2 * ScalingFactor * (1 - 0.5).

  • in 30days(11/30/2020 12:00 pm), the 70% discount rate will be applied for the mitigation process which means YAMv2 could get YAMv3 numbers as, YAMv2 * ScalingFactor * (1 - 0.7).

  • after 45days(12/15/2020 12:00 pm), none of the YAMv2 could be mitigated to YAMv3.

Poll

  • For
  • Against

0 voters