# Request For Proposals: RFP #1 (RETRACTED) **URL:** \ **Category:** Proposal Discussions\ **Created:** [April 22, 2024, 6:50pm UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575 "2024-04-22T18:50:53Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Wildri](https://avatars.discourse-cdn.com/v4/letter/w/b3f665/32.png) [@Wildri](https://horizen.discourse.group/u/Wildri)\ **Post date:** [April 22, 2024, 6:50pm UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575/1 "2024-04-22T18:50:53Z")
UPDATE TO POST: May 5, 2024: The below RFP #1 post has been retracted by The Horizen Foundation and can be disregarded. Please refer to the retraction statement posted under a separate topic [RFP #1 - Retraction statement by The Horizen Foundation](https://horizen.discourse.group/t/rfp-1-retraction-statement-by-the-horizen-foundation/616) **The Horizen Foundation** REQUEST FOR PROPOSALS RFP #1 RFP Submission Date: April 22, 2024 _Designing a new token for the upcoming Horizen Proof Verification blockchain._ Proposal Due Date: May 6, 2024 at 1:00 P.M. EST Proposal Vote Date: May 15, 2024 **Overview:** Earlier this year, the Horizen community voted overwhelmingly in favor of building a new modular blockchain solution, beginning with a new blockchain dedicated to proof verification. In recent weeks, the community has discussed the need for a new token optimized for this blockchain. Pursuant to those discussions, the Horizen Foundation is requesting proposals from qualified vendors who are interested in providing tokenomic design services for a new token to be utilized in the new proof verification layer. An MVP version of this new proof verification layer built utilizing the Substrate framework is already available in an early testnet (for details please see [New Horizen Mainchain Key Factors | Horizen Documentation](https://docs.horizen.io/new_horizen/mainchain/key_factors)). Tokenomic design services are sought for the design of a native token to power the proof verification layer built with Substrate. Due to the lack of an EVM in the upcoming proof verification layer, an ERC-20 token launch is not in scope for this RFP. The selected vendor will be compensated to perform the service of designing this new token. The selected vendor will work collaboratively with the Horizen Foundation and its current service providers who are developing the infrastructure of this proof verification layer to ensure the token design aligns with features of the new blockchain. The Horizen Foundation would like to emphasize that no changes to the tokenomics of $ZEN will be solicited or accepted; this request for proposal solely pertains to design of a new token dedicated to the upcoming proof verification chain. The final vendor will be selected via a ZenIP vote where ZEN holders will vote for the most suitable vendor. **Proposal Requirements:** Vendors interested in submitting proposals for this project must include the following five points in a proposal: 1. Background on the Vendor: Provide a brief overview of your organization, including its history, mission, vision, and relevant experience in blockchain technology and token design. 2. Qualifications: Detail the qualifications of your team members, highlighting their expertise in token design, economics, blockchain development and/or cryptography, along with any relevant experience with previous projects. 3. Interest in the Proposal: Explain why your organization is interested in this particular proposal and how you believe your expertise aligns with the vision of the Horizen ecosystem. 4. Quote: Provide a comprehensive quote for the proposed project, including all costs associated with token design, development, testing, and implementation. Break down the quote into specific cost categories, if applicable. 5. Deliverables: Outline the deliverables that will be provided upon completion of the project, including the design specifications for the new token, documentation, and any necessary training or support for The Horizen Foundation staff. **Submission Instructions:** Proposals must be submitted electronically to the The Horizen Foundation no later than 1:00 PM EST on May 6, 2024. To submit proposals, please create a new topic in Discourse in the “Proposal Discussion” category. We recommend that you title your post “RFP #1 - Vendor Name - Proposal Title” and link the post in a comment below this RFP post. Late submissions will not be considered. **Evaluation Criteria:** Proposals will be evaluated based on the following criteria: - Demonstrated expertise and experience in token design and blockchain technology; - Alignment of the proposed solution with the needs and objectives of the proof verification chain in particular and the Horizen ecosystem in general; - Clarity and thoroughness of the proposal, including the quote and deliverables; - Overall cost-effectiveness of the proposed solution. **Questions and Inquiries:** The Horizen Foundation is the point of contact for this Request for Proposal (RFP). Any questions concerning this RFP must be addressed in writing to the The Horizen Foundation, via Discourse no later than May 6, 2024. Responses to questions will be submitted via Discourse. We thank all interested vendors for their participation and look forward to reviewing your proposals. ---
**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:** [April 23, 2024, 10:54am UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575/2 "2024-04-23T10:54:20Z")
Needless to say, this is an extremely important project and I look forward to seeing strong candidates respond to the RFP. ---
**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:** [April 23, 2024, 12:53pm UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575/3 "2024-04-23T12:53:42Z")
Looking forward to seeing the proposals coming. It´s a pivotal time for the project. ---
**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:** [April 23, 2024, 3:01pm UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575/4 "2024-04-23T15:01:54Z")
Hoping to see some strong vendor/candidates with knowledge and experience that can expeditiously plan the new token details. ---
**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:** [April 23, 2024, 5:23pm UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575/5 "2024-04-23T17:23:11Z")
You are all invited to share this ZenIP with all the tokenomics providers you know. They can reach us under this topic to learn more about the ecosystem and the needs 🙂 This way, you will help to bring even more decentralization to the Horizen DAO ---
**Author:** ![blockops](https://yyz1.discourse-cdn.com/flex035/user_avatar/horizen.discourse.group/blockops/32/523_2.png) [@blockops](https://horizen.discourse.group/u/blockops)\ **Post date:** [April 24, 2024, 2:21pm UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575/6 "2024-04-24T14:21:44Z")
I would like to see that the tokenomics proposal include an incentivized testnet. See this topic here for details: > [@Incentivized testnet for Proof Verification chain](https://horizen.discourse.group/t/incentivized-testnet-for-proof-verification-chain/581): > > If a zenIP passes for a new token for the proof verification chain, there will be need for testing and integration. We should definitely have a multiple phase incentivized testnet! This may need to be part of a tokenomics study, or perhaps we can do a zenip just for a token carve-out to authorize incentivized testnet. Maybe having an incentivized testnet needs a zenip of its own. If so, this can be the discussion for it. We can use it to generate partnership participation, hosted validator s… ---
**Author:** ![RME18](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@RME18](https://horizen.discourse.group/u/RME18)\ **Post date:** [April 24, 2024, 4:19pm UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575/7 "2024-04-24T16:19:00Z")
Looking at this RFP, especially the deliverables asked for in the proposal, I think that would be beyond the scope of this request. The proposal is focused on selecting a provider, not getting into the specifics of the token design work itself. ---
**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:** [April 25, 2024, 1:08pm UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575/8 "2024-04-25T13:08:06Z")
But still good info for whoever wins to know what the community has been thinking 🙂 ---
**Author:** ![Wildri](https://avatars.discourse-cdn.com/v4/letter/w/b3f665/32.png) [@Wildri](https://horizen.discourse.group/u/Wildri)\ **Post date:** [April 25, 2024, 3:10pm UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575/9 "2024-04-25T15:10:00Z")
Hi @blockops , thank you for the comment. I would agree with @RME18 's comment that the incentivized testnet idea falls outside the scope of the current RFP#1 proposal, as the current proposal is focused on gathering information on vendors with regards to designing a new token and selecting the most suitable provider. ---
**Author:** ![gmjn](https://avatars.discourse-cdn.com/v4/letter/g/df788c/32.png) [@gmjn](https://horizen.discourse.group/u/gmjn)\ **Post date:** [April 26, 2024, 9:40pm UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575/10 "2024-04-26T21:40:40Z")
Hello everyone, as requested in this request, this is the link that leads to our proposal. I remain available for any further question! Enjoy your day, JN > [@RFP #1 - Wagmi Studio - Proposal 04262024](https://horizen.discourse.group/t/rfp-1-wagmi-studio-proposal-04262024/594): > > Hello everyone, here’s our proposal for RFP #1! [https://jmp.sh/s/9aI0ZoBfesIWNBUouaSL](https://jmp.sh/s/9aI0ZoBfesIWNBUouaSL) Our team fervently hopes that it will meet your requirements and I remain at your disposal for any further clarification. Feel free to contact me! @gmjn\_eth JN ---
**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:** [April 29, 2024, 12:15pm UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575/12 "2024-04-29T12:15:29Z")
Thank you for your submission, Jean. At first glance, it’s a solid proposal. I look forward to learning more about your team and past collaborations. ---
**Author:** ![Wildri](https://avatars.discourse-cdn.com/v4/letter/w/b3f665/32.png) [@Wildri](https://horizen.discourse.group/u/Wildri)\ **Post date:** [April 29, 2024, 7:21pm UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575/14 "2024-04-29T19:21:50Z")
Hi everyone, just to note, we have updated the RFP post to further clarify the scope of work and technical considerations. Please refer to the amended “Overview” section in the post. ---
**Author:** ![gmjn](https://avatars.discourse-cdn.com/v4/letter/g/df788c/32.png) [@gmjn](https://horizen.discourse.group/u/gmjn)\ **Post date:** [May 3, 2024, 7:35am UTC](https://horizen.discourse.group/t/request-for-proposals-rfp-1-retracted/575/15 "2024-05-03T07:35:41Z")
Hello everyone, as requested, this is the link that leads to our updated technical proposal. I remain available for any further question! Enjoy your day, JN > [@\[Updated\] RFP #1 - Wagmi Studio - Proposal 05032024](https://horizen.discourse.group/t/updated-rfp-1-wagmi-studio-proposal-05032024/605): > > Hello everyone, as we saw the amended overview, here’s our updated technical proposal for RFP #1! Our team fervently hopes that it will meet your requirements and I remain at your disposal for any further clarification. Feel free to reach me! Tg: @gmjn\_eth JN