# V7.3.0 upgrade: what happened, and what every upgrade needs from now on

**URL:** https://forum.regen.network/t/v7-3-0-upgrade-what-happened-and-what-every-upgrade-needs-from-now-on/637
**Category:** Governance
**Tags:** software-upgrade, governance-ideas
**Created:** [September 24, 2026, 5:50pm UTC](https://forum.regen.network/t/v7-3-0-upgrade-what-happened-and-what-every-upgrade-needs-from-now-on/637 "2026-09-24T17:50:44Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![brawlaphant](https://yyz2.discourse-cdn.com/flex004/user_avatar/forum.regen.network/brawlaphant/32/71_2.png) [@brawlaphant](https://forum.regen.network/u/brawlaphant)
#### Post date: [September 24, 2026, 5:50pm UTC](https://forum.regen.network/t/v7-3-0-upgrade-what-happened-and-what-every-upgrade-needs-from-now-on/637/1 "2026-09-24T17:50:44Z")

</div>

**Where was the comms today? We just ran a major chain upgrade with no signal to the community.**

v7.3.0 was tagged Sept 17, and #79 went up 15 minutes later.

I can’t find a single forum post about it — not when it went up, not during the upgrade, and not after.

At **14:58 UTC** , the chain hit the upgrade height and made no blocks for an hour and a half.

When it came back, **3 of the 11 validators were missing** , including **ecoBridge.earth** , the biggest one. For a while, we were running about **7 points above halting again**.

As I write this:

- **10 of 11 validators are back**

- **MekongLabs is still down** and gets jailed tomorrow morning if nobody reaches them

- **ecostake’s public endpoint** , which a lot of tooling reads, is still stuck at the upgrade block

There is no cohort of support from the projects using our chain, much less any kind of turnout.

**Six of the last eight proposals came from my steward account.**

## What every upgrade needs from now on

1. **A forum thread the day the proposal goes up**  
Include the upgrade height, estimated time, binaries, and validator checklist.

2. **Live status during the upgrade window**  
Followed by a short post-mortem after the chain is stable.

3. **One named person responsible for chain communications**  
And a named backup.

4. **A post-mortem for this upgrade**  
What happened, why block production stopped for as long as it did, which validators missed the upgrade, and what changes before the next one.

If nobody owns this, **I’ll run it — but then it has to be recognized as work.**