In this motion, we are going to correct a problem by re-submitting the tokenmoic parameters as we proposed in Motion 3.
In the last batch of the motions, we have submitted an updated tokenomic parameters, namely extending the heartbeat challenge window from 10 to 20, and remove the slash rate.
However it turned out the tokenmoic parameters were not applied. We submitted the update transaction and the genesis gatekeeper launch transaction in the same batch. However, in the implementation of GK, all the tokenomic changes are ignored before the genesis GK finished the launch process (a few blocks after the launch transaction got included).
As a result, our first tokenomic update transaction was not applied, and we have already seen miners got slashed (causing reduced V) like what shown in this Github issue. A resubmit should fix it:
Encoded call:
0x7103043e020c5706e17a14ae47e17ad40000000000000000fd7eb4062f0b000001000000000000005255555555555555080000000000000000000000000000003075000000000000a5ffacd6510000000000000000000000cdc46a636da90200000000000000000000000000000000000000000000000000333333333333333300000000000000001400000025bcd1d4f9b5875c0000000000000000000000000000000000000000000000000000000000000080010000000000000000000000000000003200000000000000000000000000000001000000000000008d03