Proposing mainnet software upgrade to v1.1.1 at block 894,000

Mainnet Ops
1

Hello Namada community,

I am proposing that we coordinate a mainnet software upgrade to occur at block height 894,000, which is expected to occur in between 15:00 and 16:00 UTC on Thursday, February 13, 2025. See estimates of the expected amount of time until this height is reached in the following two links:

This upgrade requires coordination to upgrade at a specific height because v1.1.1 is consensus-breaking with respect to v1.0.0. Namada v1.1.1 has been thoroughly tested on both Campfire and Housefire testnets.

Operators can download the binaries from the github here: Release Namada 1.1.1 · anoma/namada · GitHub. Please note that operators running on Ubuntu 22.04 machines will likely need to build from source.

The general process for upgrading will require operators to stop their nodes right before executing height 894,000 (which can be done easily and automatically), swap out for the upgraded binaries, and then restart the nodes, at which point the network will need to wait until > 2/3 of the network voting power comes back online with the new binaries.

Specific instructions will come soon. Follow along some active discussion on discord.

Thanks for your continued cooperation!

17 Likes
2

Supporting this proposal

3

Mandragora supports this one.

4

ITRocket supporting this proposal

5

KonsorTech support that proposal upgrade.

6

OriginStake supporting this proposal

7

itudou supports this proposal.

8

Supporting this proposal!

9

We voted YAY for this one . Lets go !

10

Supported and voted!

11

We supported this proposal

12

Supporting this one.

13

namada.info supports this !

14

We are in support of this proposal :+1:

15

Chainflow supports this proposal!

16

Hey everyone, here’s an update on the necessary steps in order to execute the software upgrade later this week. In general, the upgrade will work very similarly to the upgrade we performed during the dry-run (though even easier since no state migration is required).

  1. Download or build the namada binaries from source for v1.1.1 and place them somewhere on your node.
  2. Set your ledger to run until the target block height, at which point it will automatically halt or shut down:
    export BLOCK_HEIGHT=894000
namadan ledger run-until --block-height $BLOCK_HEIGHT --halt
    Note: you should still be using namadan v1.0.0 in the above command.
  3. Your node will halt after executing / committing block BLOCK_HEIGHT - 1. At this point, shut your node down and replace your namadan on path with the new namadan v1.1.1.
  4. Restart your ledger with the new v1.1.1 binary:
    namadan ledger run

At this point, once at least 2/3 of the network voting power has completed these steps, you should start seeing the production of blocks once again.

12 Likes
17

ready :saluting_face: :saluting_face: :saluting_face: :saluting_face: :saluting_face: :saluting_face: :saluting_face: :saluting_face: :saluting_face: :saluting_face:

18

Ready, supporting this proposal!

19

We’re supporting this proposal

20

Hey folks, I would like to add this heads up for any of you who use systemd to manage their Namada node binary.

Please make sure to set the service template to NOT auto restart via Restart=no

For example, here is our configuration:

WorkingDirectory=/root/.local/share/namada
#ExecStart=/root/.cargo/bin/namada node ledger run
ExecStart=/root/.cargo/bin/namada node ledger run-until --block-height 894000 --halt

#Restart=always
Restart=no
#RestartSec=3s

NOTE: you will see the commented lines that will be put back into effect after the update.

5 Likes