# Regen Ledger v7.3.1: public source for v7.3.0, no chain upgrade needed

**URL:** <https://forum.regen.network/t/regen-ledger-v7-3-1-public-source-for-v7-3-0-no-chain-upgrade-needed/646>\
**Category:** General\
**Created:** [November 4, 2026, 10:14am UTC](https://forum.regen.network/t/regen-ledger-v7-3-1-public-source-for-v7-3-0-no-chain-upgrade-needed/646 "2026-11-04T10:14:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marie](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Marie](https://forum.regen.network/u/Marie)\
**Post date:** [November 4, 2026, 10:14am UTC](https://forum.regen.network/t/regen-ledger-v7-3-1-public-source-for-v7-3-0-no-chain-upgrade-needed/646/1 "2026-11-04T10:14:10Z")

</div>

# Regen Ledger v7.3.1: public source for v7.3.0, no chain upgrade needed

Regen Ledger v7.3.1 is released: [Release Regen Ledger v7.3.1 🌱 · regen-network/regen-ledger · GitHub](https://github.com/regen-network/regen-ledger/releases/tag/v7.3.1)

**Validators and node operators: please switch your nodes to v7.3.1 ASAP.** There is no governance proposal, no upgrade height and no chain halt. You can switch at any time with a restart.

## What v7.3.1 is

v7.3.0, applied on mainnet at height 28971032 on 24 September, was a security release. Its binaries were published without the source code while the fix was under embargo. The fix is now public, and v7.3.1 publishes the source of v7.3.0.

v7.3.1 behaves exactly like v7.3.0 on chain. The differences are in how it is built:

- It uses the public releases of CosmWasm (wasmd v0.60.9 and wasmvm v2.3.5) instead of the private builds used for v7.3.0.
- It is built with Go 1.26.10.

Other dependencies are unchanged from v7.3.0: Cosmos SDK v0.53.6, IBC-Go v10.5.0 and CometBFT v0.38.21.

**Do not build from the `v7.3.0` tag.** It does not contain the v7.3.0 source code, and a binary built from it cannot run on mainnet. Use `v7.3.1`.

## Validator checklist

Full instructions: [Upgrade Guide v7.3](https://docs.regen.network/validators/upgrades/v7.3-upgrade.html)

## Questions and status

We also heard the feedback on how v7.3.0 was communicated. v7.3.0 had no forum thread because the fix was under embargo: we coordinated with validators directly and kept details private until the fix was public. From now on, every upgrade should have a forum thread when the proposal goes up, even when some details have to wait.