mstable/mStable-contracts

Emissions Controller: update with Linear function and upgrade contract

dimsome opened this issue · 5 comments

Hi @jkusne , could you please attach the expected emission details to double check the calculations ?
It could be a sample of emissions like [1, 8, 100, 306, 611, 612]

The actual total number of epochs is 624, not 612 as it is wrongly stated in the MCCP. I made a mistake when typing the MCCP. The current number of total epochs es 312, which corresponds to 6 years, so the new number of epochs should be the double of that, which is 624. This way, we would have exactly 12 years of emissions, and the last epoch would emit 0 (as it is supposed to be).

yarn task --network mainnet deploy-emissions --deploy-proxy "false"
  • Contract Verified
npx hardhat verify --network mainnet 0x48A91EB6D623bBc1b9c350dC40a671E72e1D4cdd 000000000000000000000000afce80b19a8ce13dec0739a1aab7a028d6845eb3000000000000000000000000a3bed4e1c75d00fa6f4e5e6922db7261b5e9acd2fffffffffffffffffffffffffffffffffffffffffffffffffffff329c7bb8194000000000000000000000000000000000000000000000000001f4a2926f42816000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000270
  • Tx Proposing upgrade

Admin Proxy 0x5C8eb57b44C1c6391fC7a8A0cf44d26896f92386
proposeUpgrade
proxy: 0xBa69e6FC7Df49a3b75b565068Fb91ff2d9d91780
implementation: 0x48A91EB6D623bBc1b9c350dC40a671E72e1D4cdd
data: []

@jkusne please update the MCCP in GitHub and forum with the correct number