[Software Upgrade Proposal]: Regen Ledger v7.0

Governance
1

We have finalized the release for Regen Ledger v7.0.0.
Over the past few weeks, the software has undergone thorough testing, including a full release candidate phase, to ensure a smooth and reliable network upgrade pending community approval.

A detailed validator upgrade guide will be published once the release is finalized and the on-chain upgrade proposals are ready to be submitted for Regen Mainnet.

New Features

  • Cosmos SDK v0.53
  • Protocol Pool and Circuit Breaker modules
  • IBC v2
  • IBC Wasm Client

We will share the updates about onchain proposal and upgrade guide in coming days.

5 Likes
2

Super exciting Anil! We are looking forward to the migration docs

3

Nice work team - pumped for this update. Another major milestone for Regen Network

1 Like
4

Thanks for the update and for carrying the weight on this release — it’s clear that v7.0.0 is a big step for Regen.

If I understand correctly, this upgrade mainly modernizes the base (Cosmos SDK v0.53) and unlocks new capabilities:

  • The Protocol Pool, allowing on-chain treasury management under governance.
  • The Circuit Breaker, adding safety controls for modules.
  • Full IBC v2 + Wasm Client support, connecting Regen to more chains and smart-contract environments.

That’s a solid foundation — it moves Regen from maintaining legacy infra to being ready for more dynamic economic systems.

I’m curious about two things:

  1. Operationally: Once mainnet is upgraded and stable, what’s the concrete plan for configuring and using these modules (Protocol Pool funding logic, Circuit Breaker permissions, initial cross-chain tests)?
  2. Community side: How can contributors engage or learn from this process — e.g., testing transactions, writing docs, or helping build dashboards or monitoring around the new modules?

I’ve been studying these systems closely and have AI tools/time to assist with coordination, documentation, or analysis — whatever’s most useful for the next phase.

Quarterly Governance Rhythm
5

The proposal is posted on-chain for voting: Mintscan

1 Like
6

I just wanted to share my full analysis of the technical aspects of the upgrade, as well as what it unlocks so that this is clearly in the public record of the forum and makes future documentation easier: Proposal 62: Regen Ledger v7 Software Upgrade

Proposal 62: Regen Ledger v7 Software Upgrade

Governance Status
┌───────────────┬────────────────────────────────────────┐
│ Field │ Value │
├───────────────┼────────────────────────────────────────┤
│ Proposal ID │ 62 │
├───────────────┼────────────────────────────────────────┤
│ Status │ VOTING_PERIOD │
├───────────────┼────────────────────────────────────────┤
│ Submitted │ 2026-01-30 10:49:56 UTC │
├───────────────┼────────────────────────────────────────┤
│ Voting Ends │ 2026-02-06 10:51:16 UTC │
├───────────────┼────────────────────────────────────────┤
│ Deposit │ 6,000 REGEN │
├───────────────┼────────────────────────────────────────┤
│ Current Tally │ ~43.65 trillion uregen YES (unanimous) │
├───────────────┼────────────────────────────────────────┤
│ Total Votes │ 62 voters (all YES) │
└───────────────┴────────────────────────────────────────┘

Upgrade Summary
┌─────────────────────┬──────────────────────────────┐
│ Parameter │ Value │
├─────────────────────┼──────────────────────────────┤
│ Target Version │ v7.2.0 │
├─────────────────────┼──────────────────────────────┤
│ Upgrade Name │ v7_0 │
├─────────────────────┼──────────────────────────────┤
│ Block Height │ 25,516,877 │
├─────────────────────┼──────────────────────────────┤
│ Estimated Time │ February 10, 2026 ~15:00 UTC │
├─────────────────────┼──────────────────────────────┤
│ Go Version Required │ 1.23+ │
└─────────────────────┴──────────────────────────────┘

7

Technical Deep Dive

  1. Cosmos SDK Upgrade (v0.47 → v0.53.4)

This is a major SDK version jump introducing significant architectural changes:

Key SDK v0.53 Changes:

  • New FinalizeBlock ABCI method (replaces separate BeginBlock/EndBlock)
  • Event emission changes with msg_index attributes
  • abci.TxResult.Log no longer populated on success
  • mode=BeginBlock/EndBlock attributes for block lifecycle events
  1. New Modules Added

The upgrade adds 3 new store modules (app/upgrades/v7_0/upgrade.go:50-54):

StoreUpgrades: storetypes.StoreUpgrades{
Added: string{
circuittypes.ModuleName, // Circuit Breaker
protocolpooltypes.ModuleName, // Protocol Pool
ibcwasmtypes.ModuleName, // IBC Wasm Light Client
},
},

Circuit Breaker Module (cosmossdk.io/x/circuit v0.2.0)

  • Purpose: Safety mechanism to halt specific message types during emergencies
  • Use Case: Can disable problematic operations without full chain halt
  • Governance: Controlled via governance proposals

Protocol Pool Module (cosmos/cosmos-sdk/x/protocolpool)

  • Purpose: Manages dedicated funds for protocol-level operations
  • Use Case: Enables governance-controlled fund allocation
  • Benefit: Sustainable network financing without per-expenditure votes

IBC Wasm Light Client (ibc-go/modules/light-clients/08-wasm v10.4.0)

  • Purpose: WebAssembly-based light client verification
  • Use Case: Enables custom light clients for IBC connections
  • Benefit: Greater interoperability with heterogeneous chains
  1. Wasm Permission Changes (Governance-Gated Upload)

Critical Change in app/upgrades/v7_0/upgrade.go:35-44:

govModuleAddrBytes := authtypes.NewModuleAddress(govtypes.ModuleName)

params := wasmKeeper.GetParams(sdkCtx)
params.InstantiateDefaultPermission = types.AccessTypeAnyOfAddresses
params.CodeUploadAccess = types.AccessConfig{
Permission: types.AccessTypeAnyOfAddresses,
Addresses: string{govModuleAddrBytes.String()},
}

Impact:

  • Code Upload: Only governance module can upload new wasm contracts
  • Instantiation: Restricted to approved addresses
  • Security: Prevents arbitrary contract deployment, requires governance approval
8
  1. Wasm Permission Changes (Governance-Gated Upload)

Critical Change in app/upgrades/v7_0/upgrade.go:35-44:

govModuleAddrBytes := authtypes.NewModuleAddress(govtypes.ModuleName)

params := wasmKeeper.GetParams(sdkCtx)
params.InstantiateDefaultPermission = types.AccessTypeAnyOfAddresses
params.CodeUploadAccess = types.AccessConfig{
Permission: types.AccessTypeAnyOfAddresses,
Addresses: string{govModuleAddrBytes.String()},
}

Impact:

  • Code Upload: Only governance module can upload new wasm contracts
  • Instantiation: Restricted to approved addresses
  • Security: Prevents arbitrary contract deployment, requires governance approval
  1. IBC API Breaking Changes

From docs/ledger/migrations/v7.0-migration.md:
┌───────────────────────────────────────────────┬─────────────────────────────────────────┐
│ Old Endpoint │ New Endpoint │
├───────────────────────────────────────────────┼─────────────────────────────────────────┤
│ GET /ibc/apps/transfer/v1/denom_traces │ GET /ibc/apps/transfer/v1/denoms │
├───────────────────────────────────────────────┼─────────────────────────────────────────┤
│ GET /ibc/apps/transfer/v1/denom_traces/{hash} │ GET /ibc/apps/transfer/v1/denoms/{hash} │
└───────────────────────────────────────────────┴─────────────────────────────────────────┘
Denom Object Format Change:
// Old (DenomTrace)
{“base_denom”: “uregen”, “path”: “transfer/channel-0”}

// New (Denom)
{“base”: “uregen”, “trace”: [{“port_id”: “transfer”, “channel_id”: “channel-0”}]}

  1. Dependency Versions
    ┌────────────────┬──────────┐
    │ Dependency │ Version │
    ├────────────────┼──────────┤
    │ Cosmos SDK │ v0.53.4 │
    ├────────────────┼──────────┤
    │ CometBFT │ v0.38.19 │
    ├────────────────┼──────────┤
    │ IBC-Go │ v10.4.0 │
    ├────────────────┼──────────┤
    │ CosmWasm wasmd │ v0.60.1 │
    ├────────────────┼──────────┤
    │ WasmVM │ v2.2.4 │
    ├────────────────┼──────────┤
    │ Go │ 1.23.8+ │
    └────────────────┴──────────┘
9

Upgrade Handler Analysis

Location: app/upgrades/v7_0/upgrade.go

Execution Flow:

  1. Log migration start
  2. Run all module migrations via manager.RunMigrations()
  3. Configure wasm permissions to governance-only upload
  4. Log migration completion

Store Upgrades: Adds circuit, protocolpool, and ibc-wasm stores

Impact Assessment

For Validators

  • Must upgrade to Go 1.23+
  • Binary upgrade at block 25,516,877
  • Cosmovisor auto-download NOT recommended (build from source)

For Developers/Integrators

  • Update IBC denom trace API calls
  • Handle new event format with msg_index
  • Wasm contract uploads now require governance proposals

For Users

  • No direct action required
  • Enhanced security via circuit breaker
  • Community fund management via protocol pool

Risk Analysis
┌────────────────────────┬───────────────────────────────────────┐
│ Risk │ Mitigation │
├────────────────────────┼───────────────────────────────────────┤
│ SDK major version jump │ Extensive testing on testnet │
├────────────────────────┼───────────────────────────────────────┤
│ API breaking changes │ Migration guide published │
├────────────────────────┼───────────────────────────────────────┤
│ Wasm permission change │ Gradual rollout, governance oversight │
├────────────────────────┼───────────────────────────────────────┤
│ New module integration │ Standard Cosmos SDK modules │
└────────────────────────┴───────────────────────────────────────┘

Code Locations
┌─────────────────┬──────────────────────────────────────────┐
│ Component │ Path │
├─────────────────┼──────────────────────────────────────────┤
│ Upgrade Handler │ app/upgrades/v7_0/upgrade.go │
├─────────────────┼──────────────────────────────────────────┤
│ Upgrade Types │ app/upgrades/types.go │
├─────────────────┼──────────────────────────────────────────┤
│ Dependencies │ go.mod │
├─────────────────┼──────────────────────────────────────────┤
│ Migration Guide │ docs/ledger/migrations/v7.0-migration.md │
├─────────────────┼──────────────────────────────────────────┤
│ Validator Guide │ docs/validators/upgrades/v7.0-upgrade.md │
└─────────────────┴──────────────────────────────────────────┘

10

sorry about the crappy formatting