Etherlink 8.0, codenamed Horus, is the newest major upgrade proposal for the Etherlink kernel, announced jointly by Nomadic Labs, TriliTech and Functori. Three changes lead the release. EVM aliases of Tezos accounts can now be recovered on any EVM chain, the Michelson interface gains gas refunds, and Michelson errors are brought into line with Tezos L1. The teams aim to submit the proposal on November 18, 2026.
With Etherlink 7.0 (Ganesha), Etherlink gained a second interface. According to the teams, Etherlink 8.0 is about making that two-interface chain safer and more predictable for its current users. Nothing in the upgrade takes effect unless Tezos L1 bakers approve it in a successful governance vote.
How wallet addresses change
Every Tezos account has had an EVM alias since Etherlink 7.0. The alias is a 0x address that stands for the account on Etherlink’s EVM interface. If a Tezos account calls an EVM contract through Native Atomic Composability (NAC), the alias appears as the msg.sender. It holds the account’s ERC-20 tokens and NFTs, and wallets display it to users as their EVM address.
Up to this point, an alias was simply a hash of the Tezos address. The hash only has meaning on Etherlink, and no other chain can tie it back to a key. Even so, bridges and centralized exchanges accepted it as a withdrawal destination. Funds sent to an alias address on another EVM chain were permanently lost, since nobody could ever sign for that address.
Under Etherlink 8.0, each alias is derived as the CREATE2 address of a smart-account contract deployed through the Safe singleton factory (0x914d7Fec6aaC8cd542e72Bca78B30650d45643d7). Each account type (tz1, tz2, tz3) gets its own contract, which embeds the account’s public key hash. The Safe factory lives at the same address on every chain that Safe supports.
There will be no migration of existing aliases. Starting with Etherlink 8.0, the kernel uses the new formula to compute the alias of every Tezos account. Old aliases remain and keep forwarding tez to their Tezos account, but they are no longer that account’s alias, so the account loses access to any other assets held at the old address. The teams say only a handful of legacy aliases have been materialized so far, and none of them hold funds.
dApps and wallets that store or compute aliases face a breaking change. Anything that stores or hard-codes aliases must recompute them using the new formula, for instance with the latest release of octez.js.
On-demand aliases and Michelson updates
In Etherlink 7.0, aliases appeared only as a by-product of crossing the gateway. A Tezos account’s EVM alias was created by its first NAC call, and an EVM account’s KT1 alias on the Michelson interface was created by its first call. Etherlink 8.0 allows users and dApps to materialize aliases on demand on both interfaces, without first making a cross-interface call.
Gas refunds are now active on the Michelson interface, and its errors match Tezos L1. The teams say both changes make the interface easier to work with for users and for existing Tezos tooling.
On the EVM side, Etherlink moves to the latest version of REVM, the Rust EVM implementation that powers its execution. The teams say this keeps Etherlink aligned with upstream Ethereum semantics and moves it toward supporting the upcoming Glamsterdam upgrade.
Steps for builders, node operators and bakers
- Builders: dApps and wallets that display, store or compute EVM aliases of Tezos accounts should be tested against the new derivation on the Tezos X Previewnet, which is already running a release candidate of Etherlink 8.0. Builders should also move to the latest octez.js. Support is available on Tezos Agora.
- Node operators: Octez EVM node version 0.68 is required for Etherlink 8.0. Operators running an older version must upgrade before activation or they will run into regressions and broken features. The EVM node documentation describes the process: stop the node, upgrade it, then restart it.
- Bakers: governance begins once the upgrade is live on Testnet. Bakers should have their voting key ready for the proposal vote.
Timeline
On November 18, 2026, the teams intend to submit the Etherlink 8.0 proposal for Etherlink Mainnet via the slow track of the governance process. A separate post on Tezos Agora will then lay out voting instructions, the exact voting periods and steps for reproducing the root hash.


