Measured against regen-1 at block height 28,401,966, as of 2026-08-18. These are not figures we maintain by hand; they are recomputed straight from the chain.
Why move it at all
A better experience, paid for from outside Regen
Using Regen today asks a person to install Keplr, hold a Cosmos wallet, and understand a chain most people never touch. That friction is the single biggest tax on a network whose whole point is to be used. On an Ethereum L2 the same registry is reachable from any wallet a person already has, a credit retires in one signature, and the certificate is portable across the largest tooling ecosystem in the space.
The second reason is money. An Ethereum L2 like Arbitrum runs a funded grant treasury with revenue behind it. That means the audits and the engineering to do this properly can be financed by the destination network, not out of Regen's community pool, which stays untouched. Regen would gain a modern front door and a maintained registry without spending its own reserves to get there.
None of this asks the community to trust a promise. The parts that make the decision possible are already built, and the rest of this page is the proof.
What is built, as of 2026-08-18
The whole package, not a sketch
The ecocredit registry, in Solidity
Credit classes, projects, batches, transfer, and retire, carrying the same beneficiary, jurisdiction, and reason a Regen retirement certificate carries today, so history stays meaningful.
REGEN, claimable by every holder
A fixed-supply REGEN with a real burn, plus a claim contract. A normal holder claims their balance with one Keplr signature. No seed phrase leaves the wallet.
The credit economy, ported
Sell orders, direct buys with retire on purchase, and baskets that mint and redeem, matched to how Regen's own modules behave, with the rounding tightened so sub-cent gas cannot mint free credits.
The chain-side handoff
A reference upgrade handler for the clean stop and final snapshot, written for regen-1's actual module version, for validators to review and run. Nothing here executes on any chain.
The part you should not take on faith
Reconcile it yourself
A full export of regen-1 was taken at a pinned block height and every account was summed. The total matches the chain's own reported supply with zero difference, and the credit batches match one for one. The export is deterministic: run it again and it produces the same result, byte for byte.
- Height:
28,401,966, pinned so anyone re-running gets the same state. - Supply: 22,434 account balances sum to
239,412,675.406252 REGEN, exactly the chain total. Gap zero. - Credits: all 80 credit batches reconcile exactly, tradable and retired.
- Claim root:
0x6d307a91…3bfadover 23,263 leaves, identical on an independent cold re-run.
This is the trust anchor for the whole migration. It means no holder has to believe our accounting. They reproduce it. The reconciliation now runs three independent, falsifiable checks rather than one identity that could print a false pass.
Reviewed against itself, before anyone else sees it
The audit, shown honestly
An independent adversarial review was run against this package. It found real defects in our own new code, which is exactly where they should be found. Every critical one is fixed and covered by a regression test. The full findings and dispositions are written down, not summarized away.
| Finding | What it was | Status |
|---|---|---|
| Critical 1 | A seal step left one mint path open, so an owner could mint the unclaimed remainder. | Fixed, tested |
| Critical 2 | About 7.5% of supply was minted with no way to claim it. Closed both in the chain-side handler and with a timelocked contract backstop. | Fixed, flagged |
| Critical 3 | A large share of supply sat behind one fixed key. Replaced with a capped, timelocked, succession-bearing role. | Fixed, tested |
| Coverage | About 49% of REGEN can claim with a normal signature; about 43% (multisigs, IBC escrows) needs a supervised path. This is the chain's real shape, not a bug. | Community decision |
The reviewer also cleared the surfaces it attacked and could not break, so a paid audit does not spend its budget re-checking them. What remains open is written plainly below.
Not ours to decide
What the community and RND still choose
- Whether to do it at all. The package makes the choice possible. It does not make it. The migration happens only if Regen governance says yes.
- How the supervised accounts move. The roughly 43% held by multisigs and bridge escrows needs an agreed, transparent path. This is a design conversation, and the numbers above are the starting point for it.
- Who funds and administers it. An Ethereum L2 audit program is the natural source. The nearest window opens around 2026-10-01, which leaves time to get the community proposal and a public testnet rehearsal done first.
- Who holds the keys, and for how long. Every privileged role in the package is now time-boxed and can be handed on. The community sets those terms.
A place to talk that is not gated behind another account
Discuss this
Regen's own forum needs a separate login. This one does not: your wallet is your name, and your stake shows next to what you say. Bring questions, objections, and better ideas. Nothing about this moves without discussion.
Built by EcoWealth as independent work and offered to Regen Network's dev team and community for open review. Every figure on this page is derived from regen-1's public chain data at a pinned height and can be reproduced. This page is a proposal and a working reference. It is not an official Regen Network product, and nothing here has been deployed, submitted, or voted on.
Contact: [email protected]