# \[Testnet\] Coordinating Upgrade to v201.0.0

**URL:** <https://forum.namada.net/t/testnet-coordinating-upgrade-to-v201-0-0/1815>\
**Category:** Network Operations\
**Created:** [23 July 2025 01:12 UTC](https://forum.namada.net/t/testnet-coordinating-upgrade-to-v201-0-0/1815 "2025-07-23T01:12:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![brentstone](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.namada.net/brentstone/32/464_2.png) [@brentstone](https://forum.namada.net/u/brentstone)\
**Post date:** [23 July 2025 01:12 UTC](https://forum.namada.net/t/testnet-coordinating-upgrade-to-v201-0-0/1815/1 "2025-07-23T01:12:46Z")

</div>

Namada [v201.0.0](https://github.com/namada-net/namada/releases/tag/untagged-989e440a7adc587cf8dc) was recently cut and includes several important upgrades, most important of which provides full support for IBC Eureka.

I propose to upgrade and hard fork the Housefire Testnet at block height [2333000](https://explorer75.org/namada-housefire/blocks/2333000), estimated to occur at roughly 14:30 UTC on Thursday, July 24.

**Instructions**  
No migration is required, and this is a simple replacement and upgrade of binaries.

1. Download or build the [v201.0.0](https://github.com/namada-net/namada/releases/tag/untagged-989e440a7adc587cf8dc) binaries. **Please do this ahead of time and ensure the binaries are compatible with your system by running** `namadac --version`.
2. At any time before the upgrade height, stop your node and restart with `namadan ledger run-until --block-height 2333000 --halt`
3. Switch the `namadan` in your `$PATH` to `v201.0.0`.
4. Restart the node with `namadan ledger run` using `namadan v201.0.0`.

**If you miss the upgrade and get a consensus failure**  
No worries! Once you encounter a consensus error, just roll back the state of your node by a block with `namadan ledger rollback` and then restart `namadan ledger run` with `namadan v201.0.0`.

---

<div class="post-metadata">

**Author:** ![sirouk](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.namada.net/sirouk/32/235_2.png) [@sirouk](https://forum.namada.net/u/sirouk)\
**Post date:** [23 July 2025 18:10 UTC](https://forum.namada.net/t/testnet-coordinating-upgrade-to-v201-0-0/1815/2 "2025-07-23T18:10:02Z")

</div>

The link to the tagged release is giving a 404.

We checked out and built on branch v201.0.0 and the `namada -V` yields:

```auto
Namada v101.1.2-4-g9a3538a

```

Is this version to be expected?

---

<div class="post-metadata">

**Author:** ![brentstone](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.namada.net/brentstone/32/464_2.png) [@brentstone](https://forum.namada.net/u/brentstone)\
**Post date:** [23 July 2025 21:01 UTC](https://forum.namada.net/t/testnet-coordinating-upgrade-to-v201-0-0/1815/3 "2025-07-23T21:01:02Z")

</div>

No, I have built the binaries on a Ubuntu 22.04 machine and get

```auto
$ namadac --version
Namada v201.0.0

```

The steps you should follow are:

```auto
git checkout v201.0.0
make build

```

---

<div class="post-metadata">

**Author:** ![sirouk](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.namada.net/sirouk/32/235_2.png) [@sirouk](https://forum.namada.net/u/sirouk)\
**Post date:** [24 July 2025 05:13 UTC](https://forum.namada.net/t/testnet-coordinating-upgrade-to-v201-0-0/1815/4 "2025-07-24T05:13:40Z")

</div>

> [@brentstone](#):
>
> namadan ledger run-until --block-height 2333000 --halt

I ended up not moving the binaries, thinking I did `make install` but it was in fact a `make build`, so I moved the binaries and the correct version is showing 👍

```auto
Namada v201.0.0

```

Thank you!