# StakedCelo upgrade to V4

**URL:** <https://forum.celo.org/t/stakedcelo-upgrade-to-v4/10399>\
**Category:** Dapps\
**Created:** [February 25, 2025, 4:19pm UTC](https://forum.celo.org/t/stakedcelo-upgrade-to-v4/10399 "2025-02-25T16:19:13Z")\
**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:** [February 25, 2025, 4:19pm UTC](https://forum.celo.org/t/stakedcelo-upgrade-to-v4/10399/1 "2025-02-25T16:19:13Z")

</div>

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

# Short summary:

- The StakedCelo protocol is upgraded to v4, which patches a few bugs including the one previously mentioned in [stCelo - Minor Accounting Error](https://forum.celo.org/t/stcelo-minor-accounting-error/8382) .

# Details:

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

- The proposal was submitted with this [transaction](https://celo.blockscout.com/tx/0x8e2c632dd12ef753125bc4c1175728a89c6d78b2ea22090159f63740f3380f2e) and the following parameters:
  - Destinations: [0x3a3ed74b1cc543d5eb323f70ac2f19977a0ea088, 0x0239b96D10a434a56CC9E09383077A0490cF9398,0xb88af6EAc9cd146D8b03b66708EF76beBD937871,0x3A3ed74B1cC543D5EB323f70ac2F19977a0eA088,0x4aAD04D41FD7fd495503731C5a2579e19054C432]
  - Values: [0,0,0,0]
  - payloads: [0x3659cfe600000000000000000000000078b405d3a6af7a1f17b74fcea51934f4ee46f38e,0x3659cfe6000000000000000000000000365e623c568f0e8ee6aa93a5ac42fda9daa58d23,0x3659cfe6000000000000000000000000d54bc0ab3b363a0e34767581daab4a9db1684a09,0x3659cfe6000000000000000000000000c2fd564028536df9fe87de36bbab6ae26b33e3d0]

- The payload needed to submit the multisig proposal was generated using
  - yarn hardhat stakedCelo:multiSig:update:v3:v4 --network celo --account [YOUR\_ACCOUNT\_ADDRESS]
  - [StakedCelo github repo](https://github.com/celo-org/staked-celo/tree/releases/4)

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

Best,

soloseng

---

<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:** [March 20, 2025, 2:42pm UTC](https://forum.celo.org/t/stakedcelo-upgrade-to-v4/10399/2 "2025-03-20T14:42:12Z")

</div>

**UPDATE** : The proposal has been fully confirmed and scheduled after [0x86f681acae76a2727123caedd5cfbcf154135d96b8e6093d629489011d41a80a](https://celoscan.io/tx/0x86f681acae76a2727123caedd5cfbcf154135d96b8e6093d629489011d41a80a) was successful. It will become executable once the time-lock has been reached on Thu Mar 27 2025 03:44:42 GMT+0000.

---

<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:** [March 27, 2025, 1:52pm UTC](https://forum.celo.org/t/stakedcelo-upgrade-to-v4/10399/3 "2025-03-27T13:52:21Z")

</div>

> [@soloseng](#):
>
> Thu Mar 27 2025 03:44:42 GMT+0000

The StCELO protocol has now been upgraded to V4

> **[Celo Mainnet transaction...](https://celo.blockscout.com/tx/0x8330d5b8922ea76a349cbae7df79011f981104ef82b01a7e876f444231a265c4)**
>
> View transaction 0x8330d5b8922ea76a349cbae7df79011f981104ef82b01a7e876f444231a265c4 on Celo Mainnet (Mainnet) Explorer