MCCP 14: Whitelist Abachi Multisig in Staking V2 Source


Simple Summary

Abachi acquired recently some MTA and would like to stake this in Staking V2 on mStable. The MTA is in the Multi-sig and Abachi to stake MTA from the Gnosis Safe Multisog. Abachi plans to acquire more MTA both via buying from the market and our MTA and Stable pools. These will be added to the treasury backing and staked in the future.


With the introduction of Staking V2, we introduced a limitation that only Externally Owned Accounts (EOA) can stake. Additionally, the functionality to whitelist certain contract addresses was added.

This Proposal requests to whitelist the following address in Staking V2: 0x6FcE4c6CDd8C4e6C7486553D09BdD9aEE61cF095


Abachi recently started to use mStable Save for generating yield:

  1. 500k into Save on Ethereum Mainnet.
  2. 500k into Save on Polygon

Alongside this investment, MTA was acquired as well to use in Staking V2. This would allow us to boost our MTA rewards, participate in governance and represent our interests within the mStableDAO.


To whitelist the Abachi Multisig the following transactions will be executed by the ProtocolDAO Multisig:

  • Staked MTA (stkMT)

    • 0x8f2326316eC696F6d023E37A9931c2b2C177a3D7:
    • whitelistWrapper(0x6FcE4c6CDd8C4e6C7486553D09BdD9aEE61cF095)
  • Staked Token BPT (stkBPT)

    • 0xeFbe22085D9f29863Cfb77EEd16d3cC0D927b011:
    • whitelistWrapper(0x6FcE4c6CDd8C4e6C7486553D09BdD9aEE61cF095)

Copyright and related rights waived via CC0