Horizen EON Bridge After Shutdown: What Still Works

The Horizen EON bridge no longer moves assets into a live EON network: the chain’s migration snapshot fixed which ZEN balances could move to Base, and transactions after its final block have no migration value. Horizen completed the migration on July 23, 2025. EOA balances of native ZEN were mapped to the same wallet address on Base, while balances held in smart contracts and non-ZEN tokens were excluded. The distinction is between a wallet balance recorded at the snapshot and an asset or position whose value depended on EON contracts.

What did the EON migration move to Base?

The migration moved eligible native ZEN balances belonging to externally owned accounts (EOAs), along with ZEN staked by forgers or delegators, to the same addresses on Base. EON and Base use the same address format, so holders did not need to submit a claim for those balances. The receiving asset is ZEN represented by an ERC-20 contract on Base; it is not an EON balance that remains spendable on the old chain.

The transfer used a fixed state snapshot, not a bridge transaction for each holder. Horizen’s migration process loaded EON balance data into the EONBackupVault contract on Base. After the data was loaded and checked against a cumulative hash, the vault’s distribute method minted the corresponding ZEN to each payee. That design preserves a recorded balance without requiring each EON wallet to initiate a withdrawal. A broader spookyswap guide to which networks are worth checking takes up the network-selection question; for EON, the decisive check is whether an asset appears in the migration state or depends on a contract the snapshot excluded.

The cutoff is encoded in the chain history. EON’s final migration block was the block that referenced the designated final Horizen mainchain block. Horizen’s documentation says transactions recorded after that final block have no value for migration. A wallet display, old dApp page or token balance on an EON explorer therefore does not establish that the asset was carried over to Base.

Which EON assets did not migrate?

ZEN held by smart contracts did not migrate automatically, and neither did ZEN balances locked in those contracts or stakes delegated by smart contracts. Wrapped ZEN (wZEN), stablecoins and other tokens were also outside the native-ZEN snapshot. The earlier migration instructions told users to exit DeFi pools, unwrap wZEN into native ZEN, and bridge non-native tokens back to their original chains before the cutoff.

Those steps mattered because a bridge transfer and a token migration solve different problems. A bridge moves an asset between networks through contracts or a bridge operator’s supported path. The ZEN migration copied eligible native balances from a defined state into a new ERC-20 system. It did not recreate EON’s contracts, pool shares, token contracts, allowances, or bridge liquidity on Base.

As a result, there is no general conversion from an old EON token balance into a Base asset. If a position depended on an EON dApp, its underlying contracts and the terms of that application determine whether any separate recovery route exists. A displayed balance alone is not evidence of a live redemption path.

What can holders still do after the shutdown?

For native EON ZEN held directly in an EOA at the snapshot, check the same address on Base for the migrated ERC-20 ZEN. The migration was automatic, but a wallet may need to be configured to show the Base network and token. If the expected balance is absent, compare the address and the snapshot eligibility before treating it as a bridge failure.

For other cases, the next step depends on where the asset sat:

• Native ZEN in an EOA: Check the corresponding address on Base. No manual EON claim was required.
• ZEN in an EON contract or smart-contract stake: It was excluded from automatic migration. Check the application’s own records and any documented recovery process.
• wZEN, stablecoins or other EON tokens: They were not converted by the ZEN migration. Do not assume the old bridge route or token issuer still supports withdrawal.
• ZEN on the old mainchain: This followed a separate claim process through the ZendBackupVault contract. It is not the EON balance-mapping path.

The mainchain claim distinction matters because the old UTXO chain did not map addresses to Base in the same way as EON. Eligible mainchain holders make a signed claim to the ZendBackupVault; an EON holder whose balance was mapped to the same address does not use that procedure. The two routes concern different source ledgers and should not be mixed.

Any recovery attempt should begin with the official migration records and the relevant contract or application, not a link sent by an unsolicited account. A wallet prompt cannot restore a position that was absent from the snapshot, and signing a transaction does not make a discontinued EON bridge operational.

What still works is the Base-side ZEN created from eligible EON snapshot balances, plus the separate mainchain claim route for qualifying old-chain balances. The old EON state can remain useful as a historical record, but it is not a live bridge ledger: post-cutoff transactions and excluded contract positions do not become transferable merely because an interface still displays them.