# StakedCelo: Upgrade to v3

**URL:** <https://forum.celo.org/t/stakedcelo-upgrade-to-v3/7934>\
**Category:** Dapps\
**Created:** [May 1, 2024, 2:19pm UTC](https://forum.celo.org/t/stakedcelo-upgrade-to-v3/7934 "2024-05-01T14:19:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![soloseng](https://avatars.discourse-cdn.com/v4/letter/s/8797f3/32.png) [@soloseng](https://forum.celo.org/u/soloseng)\
**Post date:** [May 1, 2024, 2:19pm UTC](https://forum.celo.org/t/stakedcelo-upgrade-to-v3/7934/1 "2024-05-01T14:19:29Z")

</div>

Hey Celo community, and especially all users of the StakedCelo (stCELO) protocol:

I am posting here as a Celo community member and contributor to StakedCelo. The multisig holders have approved an upgrade of StakedCelo from v2 to v3.

**Short summary:**

- The StakedCelo protocol is upgraded to v3, which has following benefits:
  - Celo Governance can now execute proposals as the stCELO Multisig.
  - stCELO contracts can now be paused, either by Celo Governance, or by a Multisig owner.

- 1 additional MultiSig owner is being added
- 3/5 multisig holders have voted on the code change (last confirmation transaction [**here**](https://celoscan.io/tx/0xf4667580a52562f2a5ef67ee83f799041e8b26712fdfee862b6fffa97db0b47d) ). Therefore, the 7-day timelock has started. It will elapse on Wed May 08 2024 00:29:57 UTC. After that, the change will be executed and go into effect.

**Details:**

For anyone wishing to verify the code changes which will go into effect:

- The proposal was submitted with this [**transaction**](https://celoscan.io/tx/0x2649c9d64d2f76690d5d5ce977cb45465ba0d7e111fe46dde975932b39273e1e) and the following parameters:
  - Destinations: [0x78DaA21FcE4D30E74fF745Da3204764a0ad40179,0x0239b96D10a434a56CC9E09383077A0490cF9398,0x4aAD04D41FD7fd495503731C5a2579e19054C432,0xC668583dcbDc9ae6FA3CE46462758188adfdfC24,0xDa30d1F96C17Fe7919FC12Ea672915c2e0B9ab8e,0x140b36FFc554d174fbf1B436C50D5409bDceCDCF,0xb88af6EAc9cd146D8b03b66708EF76beBD937871,0x3A3ed74B1cC543D5EB323f70ac2F19977a0eA088,0xDc5762753043327d74e0a538199c1488FC1F44cf,0x78DaA21FcE4D30E74fF745Da3204764a0ad40179,0x0239b96D10a434a56CC9E09383077A0490cF9398,0x4aAD04D41FD7fd495503731C5a2579e19054C432,0xC668583dcbDc9ae6FA3CE46462758188adfdfC24,0xDa30d1F96C17Fe7919FC12Ea672915c2e0B9ab8e,0x140b36FFc554d174fbf1B436C50D5409bDceCDCF,0xb88af6EAc9cd146D8b03b66708EF76beBD937871,0x3A3ed74B1cC543D5EB323f70ac2F19977a0eA088,0xDc5762753043327d74e0a538199c1488FC1F44cf,0x3A3ed74B1cC543D5EB323f70ac2F19977a0eA088,0x78DaA21FcE4D30E74fF745Da3204764a0ad40179]
  - Values: [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
  - payloads: [0x3659cfe60000000000000000000000008bd50c8df89840ca8e78c32a730076397933f818,0x3659cfe60000000000000000000000002cb8b2e0915629c8999e739932f6a6642600e9af,0x3659cfe600000000000000000000000007550767a1604af3e504749e284792ff30fb4a53,0x3659cfe60000000000000000000000006e17cf4e1a21125d0ce9a1ce4a284ad7bf783b67,0x3659cfe600000000000000000000000054496eb9b1ec14bf718b5de11f269b23063f83bd,0x3659cfe6000000000000000000000000073bb388eeea656e056c8750494cd0bc460985d9,0x3659cfe600000000000000000000000054c819e39fde40aa8fcf1244589ec5aebf32999a,0x3659cfe6000000000000000000000000d718b64bc1facbd0087d827c0a3ea144445f5745,0x3659cfe600000000000000000000000058fc5556dfb1a1b23e32b395f6522aa86c14713c,0x2d88af4a00000000000000000000000078daa21fce4d30e74ff745da3204764a0ad40179,0x7c0d530f,0x7c0d530f,0x7c0d530f,0x7c0d530f,0x7c0d530f,0x7c0d530f,0x7c0d530f,0x7c0d530f,0x41b9179f0000000000000000000000000000000000000000000000000000000000000003,0x7065cb4800000000000000000000000001aae13f65fb90b490e6614ade0bfffa57ac5bbc]

- The payload needed to submit the multisig proposal was generated using
  - yarn hardhat stakedCelo:multiSig:update:v2:v3 --network celo --account \< **Multisig submitter** \>
  - [StakedCelo github repo](https://github.com/celo-org/staked-celo/tree/releases/3)

If you have any questions, feedback or thoughts, please share these below.

Best,

Soloseng

---

<div class="post-metadata">

**Author:** ![0xGoldo](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.celo.org/0xgoldo/32/7159_2.png) [@0xGoldo](https://forum.celo.org/u/0xGoldo)\
**Post date:** [May 2, 2024, 9:42am UTC](https://forum.celo.org/t/stakedcelo-upgrade-to-v3/7934/2 "2024-05-02T09:42:48Z")

</div>

Thanks a lot for the update!

I do not fully understand this point

> - Celo Governance can now execute proposals as the stCELO Multisig.

Can you please explain more about it? Maybe with an example of usecase?

---

<div class="post-metadata">

**Author:** ![soloseng](https://avatars.discourse-cdn.com/v4/letter/s/8797f3/32.png) [@soloseng](https://forum.celo.org/u/soloseng)\
**Post date:** [May 3, 2024, 2:38pm UTC](https://forum.celo.org/t/stakedcelo-upgrade-to-v3/7934/3 "2024-05-03T14:38:38Z")

</div>

This is in an effort to bring stacked Celo closer to the CELO community by giving Celo Governance co-ownership of the stCELO protocol.

An example of this would be if the CELO community wanted to add a specific validator group to the list of default validator groups, they could do so by proposing and voting on a CELO Governance proposal that makes the desired changes.