Horizen EON has stopped. Its last block was produced in October 2025, its endpoints and explorer are gone, and the chain registry marks it as retired.
ZEN itself continues. It moved to Base as an ordinary token in July 2025, and that is where the asset lives now.
The detail that matters most: wallet balances moved across automatically, but ZEN locked inside smart contracts did not.
What you get out of the box

Pick your import method.
Before you start
- Add your Base wallet. ZEN lives there now, at the same address you used on EON.
- If you had ZEN in an application or staked through a contract, gather your records from before the migration. That portion was not carried across.
On Kryptos
- Log in to Kryptos.
- Go to Integrations.
- Click Add Integration, then search for and select Horizen EON.
- Click the Horizen EON icon and choose Upload CSV.
- Upload the file. Kryptos reads it and categorises the transactions for you.
Good to know
- EON wallet balances moved to Base automatically, at the same address, because both use the same format.
- ZEN held in smart contracts, including some staking, was not migrated.
- The old chain kept producing blocks for about three months after the migration before stopping in October 2025.
What moved, what did not, and why the difference matters
Horizen's migration is unusually well documented, and the distinction it drew is exactly the one that decides your tax treatment.
In July 2025 Horizen moved ZEN onto Base as an ordinary token. Balances sitting in ordinary wallets on EON were migrated automatically, and because both chains use the same address format, they arrived at the same address their owner already controlled. Nothing to claim, nothing to do.
That half is a continuation. Same asset, same ticker, same address, one for one. Nothing was sold, so your original cost carries through and your holding period is unbroken.
The other half is where the money was lost. Horizen stated plainly that ZEN held in smart contracts, including balances locked in applications and stakes delegated through contracts, was not migrated. Anyone whose ZEN was deposited in a lending market or a liquidity pool on EON did not get it back, and since the chain stopped producing blocks in October 2025 there is no way to retrieve it.
That is a real loss with a determinable date, which is rarer and more useful than it sounds: most crypto losses of this kind are messy about when exactly the asset became worthless. Here there is a published statement about what was excluded and a chain that verifiably stopped. Whether you can claim it, and in which year, depends on where you file, so it is worth taking to an accountant with the dates in hand. See the USA crypto tax guide or the UK crypto tax guide.
There is also a smaller wrinkle. EON did not stop when the migration finished; it carried on for about three months before halting in October 2025. Activity in that window is real and happened, on a chain that no longer answers.
Manage your Horizen EON portfolio with Kryptos.
Carrying ZEN cost across the migration
Your Base ZEN is the same holding you had on EON, at the same address. The original purchase price should follow it.
Accounting for ZEN that did not migrate
ZEN locked in contracts was not carried across and the chain is now stopped, so it is unrecoverable. That is a loss with a determinable date.
Reconstructing pre-migration activity
EON cannot be queried now, so its history exists only in records you kept and exchange statements.
Audit-ready, automatically.
Once your wallets and exchanges are connected, generating a tax report takes a single click. Open Reports from the menu, choose your jurisdiction, and download.
The migration was not a sale
ZEN moved from one chain to another, at the same address, one for one. Nothing was disposed of, so your original cost carries through and your holding period continues.
ZEN stuck in contracts is a genuine loss
Balances locked in smart contracts were explicitly not migrated, and the chain has since stopped. That portion is gone with a date attached, which is unusually clean as loss events go. Whether you can claim it depends on where you file.
The old chain ran on after the migration
EON kept producing blocks for roughly three months after balances moved. Activity in that window is real but happened on a chain that has since stopped.
You still need the purchase price
Whether you are recording a continuation or a loss, both work from what you originally paid, which now lives in exchange records and saved exports.
Read-only by design.
- A file upload is read-only. Nothing connects to your account
- Kryptos never asks for your password or login details
- Delete an import at any time and its data goes with it
- Keep the original file: it is your evidence if anyone asks later
If something doesn't sync.
The chain stopped producing blocks in October 2025 and its endpoints are gone. A few third-party endpoints still answer with the final block, which makes it look alive.
Check Base rather than EON. Wallet balances were moved there automatically at the same address.
ZEN held inside smart contracts was not migrated. The chain has since stopped, so that portion is not recoverable.
Still stuck? Email support@kryptos.io or open live chat from the app.
