# ZenIP 42405 DRAFT: Directing the Horizen Foundation to Request a Migration Proposal for $ZEN and EON

**URL:** <https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627>\
**Category:** ZenIP Discussions\
**Tags:** zen, eon\
**Created:** [May 15, 2024, 4:45pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627 "2024-05-15T16:45:23Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![PVM](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/pvm/32/56_2.png) [@PVM](https://horizen.discourse.group/u/PVM)\
**Post date:** [May 15, 2024, 4:45pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/1 "2024-05-15T16:45:23Z")

</div>

**Preamble**

ZENIP: 42405

Title: Directing the Horizen Foundation to Request a Migration Proposal for $ZEN and EON

Owner: Paul Mihalache

Discussions-To: Paul Mihalache, [thesadu4ever@gmail.com](mailto:thesadu4ever@gmail.com)

Comments-URL:

Status: Draft

Type: Non-Technical

Created: 05-15-2024

License: MIT

**Abstract**

This ZenIP constitutes a formal action by the Horizen community to direct the Horizen Foundation to request that its current technical service provider, Horizen Labs, develop a technical migration path for the EON blockchain and $ZEN token pursuant to the community discussion on this topic in recent weeks, and that Horizen Labs include an estimated timeline and cost. It is the desire of the Horizen community that this work be undertaken as part of Horizen Lab’s existing services agreement with the Horizen Foundation as a technical provider to the Horizen ecosystem.

Any proposed migration path that Horizen Labs may develop as a result of this proposal would be subject to adoption by the community in a separate ZenIP.

**Motivation**

In April 2024, Rob Viglione, co-founder of Horizen, published a [blog post](https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://medium.com/@robviglione/horizen-as-a-home-for-zk-and-an-enduring-utility-for-zen-751ab1381867%26amp;sa%3DD%26amp;source%3Deditors%26amp;ust%3D1715795008217691%26amp;usg%3DAOvVaw24maqhU4TZ7u6TBBTofeab&sa=D&source=docs&ust=1715795008222524&usg=AOvVaw02PwCxCg8SZNpikmfgGrQR) outlining his vision for the future of the Horizen ecosystem. In this vision, Horizen would become a “home for zero-knowledge,” with a new version of EON (“EON 2.0”) serving as the execution environment for zk applications.

Achieving this vision entails migrating the $ZEN cryptocurrency token and the EON blockchain to a new technology stack, porting over $ZEN to serve as the gas and governance token of EON 2.0, and deprecating the current Horizen mainchain once safe to do so.

Meanwhile, Horizen Labs [announced](https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://horizen.discourse.group/t/updated-process-for-rapid-deployment-of-the-zk-proof-verification-blockchain/611%26amp;sa%3DD%26amp;source%3Deditors%26amp;ust%3D1715795008217979%26amp;usg%3DAOvVaw1MV66GaEou51KpXSDkrLrY&sa=D&source=docs&ust=1715795008222749&usg=AOvVaw38PWSnRIxv36M1PiVdyRPi) in early May that it will independently undertake the buildout of the upcoming proof verification chain in order to bring it to market more quickly. This makes the need to develop a migration roadmap for $ZEN and EON more urgent.

This ZenIP aims to gather community support to direct the Horizen Foundation to request that Horizen Labs develop a proposed pathway for this migration. This work should be done under Horizen Labs’ existing services agreement with the Horizen Foundation as it pertains to ongoing maintenance and development of the Zen and EON blockchains.

**Specification**

Should this ZenIP be approved by the community, the appropriate representatives of the Horizen Foundation will be responsible for formally requesting the proposal from Horizen Labs. The proposal should include an estimated timeline and cost for the project.

Should Horizen Labs undertake this work, the result would be a technical migration roadmap. Such a roadmap would be presented to the community and subject to approval in a separate ZenIP.

**Rationale**

This ZenIP 1) starts the process of determining the technical roadmap for migrating $ZEN and EON migration, while 2) doing so with the consultation of the community. It is important that the Horizen community be involved in this process as it is the most consequential upgrade to Horizen’s technology in years.

**Security and Privacy Considerations**

Given this ZenIP is to approve a directive to Horizen Labs, there are no major security or privacy considerations. However, it is worth noting that any migration path developed by Horizen must put security at its center, to ensure that the integrity of the blockchain, including token balances, is upheld.

---

<div class="post-metadata">

**Author:** ![SKyTL](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/skytl/32/317_2.png) [@SKyTL](https://horizen.discourse.group/u/SKyTL)\
**Post date:** [May 15, 2024, 5:00pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/2 "2024-05-15T17:00:10Z")

</div>

Agreed, I fully support this migration.

---

<div class="post-metadata">

**Author:** ![RME18](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@RME18](https://horizen.discourse.group/u/RME18)\
**Post date:** [May 15, 2024, 5:10pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/3 "2024-05-15T17:10:30Z")

</div>

LFG!! Glad this is finally happening

---

<div class="post-metadata">

**Author:** ![PVM](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/pvm/32/56_2.png) [@PVM](https://horizen.discourse.group/u/PVM)\
**Post date:** [May 15, 2024, 5:11pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/4 "2024-05-15T17:11:35Z")

</div>

We need to keep up with the crypto status quo and this migration looks like the best way

---

<div class="post-metadata">

**Author:** ![PVM](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/pvm/32/56_2.png) [@PVM](https://horizen.discourse.group/u/PVM)\
**Post date:** [May 15, 2024, 5:11pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/5 "2024-05-15T17:11:56Z")

</div>

Thanks for your support

---

<div class="post-metadata">

**Author:** ![zenchick](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/zenchick/32/117_2.png) [@zenchick](https://horizen.discourse.group/u/zenchick)\
**Post date:** [May 15, 2024, 5:23pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/6 "2024-05-15T17:23:50Z")

</div>

> [@PVM](#):
>
> iven this ZenIP is to approve a directive to Horizen Labs, there are no major security or privacy considerations. However, it is worth noting that any migration path developed by Horizen must put security at its center, to ensure that the integrity of the blockchain, including token balances, is upheld.

We really need to close out the direction for Horizen and EON. I’m excited for this proposal!

---

<div class="post-metadata">

**Author:** ![PVM](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/pvm/32/56_2.png) [@PVM](https://horizen.discourse.group/u/PVM)\
**Post date:** [May 15, 2024, 5:57pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/7 "2024-05-15T17:57:17Z")

</div>

We all are! 💪 2024 will be such a great year!

---

<div class="post-metadata">

**Author:** ![finpunk](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/finpunk/32/114_2.png) [@finpunk](https://horizen.discourse.group/u/finpunk)\
**Post date:** [May 15, 2024, 9:06pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/8 "2024-05-15T21:06:01Z")

</div>

If I can speak for Horizen Labs, I’ll just say that we’re fully on board with doing this and ridiculously excited to envision what EON 2.0 could look like within the broader vision. I know there are many ideas out there from different people, but it’s time to put a plan to paper and get the community excited about it.

---

<div class="post-metadata">

**Author:** ![nrdl](https://avatars.discourse-cdn.com/v4/letter/n/3da27b/32.png) [@nrdl](https://horizen.discourse.group/u/nrdl)\
**Post date:** [May 15, 2024, 9:22pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/9 "2024-05-15T21:22:13Z")

</div>

I agree. This is a task that needs to be carried out quickly by having a person in charge as soon as possible.

---

<div class="post-metadata">

**Author:** ![PVM](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/pvm/32/56_2.png) [@PVM](https://horizen.discourse.group/u/PVM)\
**Post date:** [May 15, 2024, 9:33pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/10 "2024-05-15T21:33:39Z")

</div>

Brainstorming is always good for creative flow! No matter what’s the chosen path… I am fully supportive

---

<div class="post-metadata">

**Author:** ![Primordial](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/primordial/32/292_2.png) [@Primordial](https://horizen.discourse.group/u/Primordial)\
**Post date:** [May 15, 2024, 9:39pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/11 "2024-05-15T21:39:13Z")

</div>

Yes this sounds great, excited and ready to vote for the migration!

---

<div class="post-metadata">

**Author:** ![PVM](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/pvm/32/56_2.png) [@PVM](https://horizen.discourse.group/u/PVM)\
**Post date:** [May 16, 2024, 8:34am UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/12 "2024-05-16T08:34:09Z")

</div>

ZenIP 42405 DRAFT - Directing the Horizen Foundation to Request a Migration Proposal for ZEN and EON 🌟  
[https://www.publish0x.com/mind-puzzle/zenip-42405-draft-directing-the-horizen-foundation-to-reques-xxvnjqv?a=pmbk1p5ezJ](https://www.publish0x.com/mind-puzzle/zenip-42405-draft-directing-the-horizen-foundation-to-reques-xxvnjqv?a=pmbk1p5ezJ)

---

<div class="post-metadata">

**Author:** ![ParaTu](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/paratu/32/298_2.png) [@ParaTu](https://horizen.discourse.group/u/ParaTu)\
**Post date:** [May 16, 2024, 8:44am UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/13 "2024-05-16T08:44:55Z")

</div>

support！ please quickly 😍

---

<div class="post-metadata">

**Author:** ![rocket](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/rocket/32/198_2.png) [@rocket](https://horizen.discourse.group/u/rocket)\
**Post date:** [May 16, 2024, 12:22pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/14 "2024-05-16T12:22:04Z")

</div>

I completely agree, we need to expedite, and after community approval, proceed with this process as quickly as possible.

---

<div class="post-metadata">

**Author:** ![PVM](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/pvm/32/56_2.png) [@PVM](https://horizen.discourse.group/u/PVM)\
**Post date:** [May 16, 2024, 12:34pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/15 "2024-05-16T12:34:21Z")

</div>

The community support is high so this will hopefully go to snapshot quickly

---

<div class="post-metadata">

**Author:** ![robin](https://avatars.discourse-cdn.com/v4/letter/r/e5b9ba/32.png) [@robin](https://horizen.discourse.group/u/robin)\
**Post date:** [May 16, 2024, 2:44pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/16 "2024-05-16T14:44:05Z")

</div>

Support migrations to EON, but can we get a proposal for ZEN changing tokenomics and be used as new token for the verification protocol as well?

---

<div class="post-metadata">

**Author:** ![RME18](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@RME18](https://horizen.discourse.group/u/RME18)\
**Post date:** [May 16, 2024, 2:56pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/17 "2024-05-16T14:56:28Z")

</div>

That topic has been discussed extensively in other threads on Discourse. What is clear is:

- the tokenomics of $Zen won’t change

- $Zen will migrate to a new blockchain (the new version of EON), which will have a connection with the proof verification chain \<\<–what this will actually look like is what we are asking HL to flesh out

- the proof verification chain should get its own token and that will be part of a new ecosystem, but Rob is supportive of the idea that the Horizen community should be rewarded for its support of the proof verification chain

---

<div class="post-metadata">

**Author:** ![robin](https://avatars.discourse-cdn.com/v4/letter/r/e5b9ba/32.png) [@robin](https://horizen.discourse.group/u/robin)\
**Post date:** [May 16, 2024, 3:55pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/18 "2024-05-16T15:55:51Z")

</div>

Just hate the idea of 2 tokens. As Labs is going to be service provider for 2 chains, dealing with exchanges for 2 tokens etc, ZEN just ending up as pure comunity projects with not much chance for a network effect and being a good utility token except gas on EON. I would imagine New horizen token is probaly going to be evm capable also? So over time why should we speculative on ZEN and not new token which can do the same and will have seemingly much more backing by professionals firms. “Just” to keep the idea of fair lunch and fixed tokenomics

---

<div class="post-metadata">

**Author:** ![RME18](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@RME18](https://horizen.discourse.group/u/RME18)\
**Post date:** [May 16, 2024, 5:18pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/19 "2024-05-16T17:18:04Z")

</div>

Why would you imagine that a new token for the proof verification chain would be EVM compatible if it’s built on substrate?

As for $Zen, it would be the native token of the new version of EON, which will have tons of built in TVL at launch assuming the migration path ports over balances, which I think is a safe assumption. This means a nice treasury for funding ZK projects & growing the ecosystem more broadly. Plus, if $Zen holders are eligible to claim some supply of a future PV token, that’s an attractive proposition

---

<div class="post-metadata">

**Author:** ![Manon](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/manon/32/5_2.png) [@Manon](https://horizen.discourse.group/u/Manon)\
**Post date:** [May 16, 2024, 6:44pm UTC](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627/20 "2024-05-16T18:44:27Z")

</div>

I am fully supportive as well. HL is the best to perform the migration, I can’t wait to have the roadmap for this

[Next page](https://horizen.discourse.group/t/zenip-42405-draft-directing-the-horizen-foundation-to-request-a-migration-proposal-for-zen-and-eon/627.md?page=2)
