> For the complete documentation index, see [llms.txt](https://hyper-performance-edge-computing.gitbook.io/hyper-performance-edge-computing-hpec-dao-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyper-performance-edge-computing.gitbook.io/hyper-performance-edge-computing-hpec-dao-docs/documentation/basics-execution-layer/integrations/economic-framework/economic-initiatives/cmhpec-dao-pass.md).
# CMHPEC DAO PASS
Infrastructure Participation Layer
**Overview**
**CMHPEC DAO PASS connects decentralized compute infrastructure with long-term ecosystem assets — governed by people who build, not speculate.**
***
## CMHPEC DAO PASS
### Economic Initiative Overview
CMHPEC DAO PASS is the participation and coordination layer for the **CMHPEC decentralized infrastructure ecosystem**.
It enables participants to join a live, DAO-coordinated network of Node Factories, governance processes, and ecosystem initiatives **without fragmenting or liquidating core infrastructure assets**.
Participation is abstracted through a DAO PASS, while infrastructure remains permanent, shared, and DAO-governed.
***
### How to Join CMHPEC DAO
There are **two aligned participation paths**, each contributing to infrastructure expansion and ecosystem growth in different ways.
***
### Option A — CMHPEC DAO PASS (Community & Ecosystem Path)
Participants may acquire a **CMHPEC DAO PASS (NFT)** via the official mint portal.
{% embed url="" %}
#### What This Represents
Holding a CMHPEC DAO PASS provides:
* Participation in CMHPEC DAO governance
* Alignment with shared Node Factory infrastructure
* Exposure to Node Factories delegated to CMHPEC DAO
* Access to ecosystem initiatives and future services
#### Use of Funds (Critical Clarification)
Funds raised through **Option A** are **not used for speculative yield**.
They are allocated to:
* Acquire and expand **metaverse land assets** inside the **Infinity Rising / Cornucopias ecosystem**
* Support long-term ecosystem initiatives developed in collaboration with **Corn Mafia**
* Expand community-owned digital infrastructure linked to CMHPEC DAO
These land assets are:
* Held transparently on-chain
* Managed as DAO-aligned ecosystem assets
* Expanded incrementally as participation grows
#### Strategic Partnership: Corn Mafia × CMHPEC
Corn Mafia is the **largest and most active community** within the Infinity Rising / Cornucopias metaverse.
Through a strategic partnership with Corn Mafia:
* CMHPEC DAO has established **Corn AI Lands**
* These lands act as a shared ecosystem asset
* Each additional CMHPEC DAO PASS strengthens the collective land position
* Expansion benefits all aligned participants structurally, not individually
🔎 **On-chain verification of land holdings:**\
👉 Corn AI Lands (Pool.pm):
{% embed url="" %}
🪙 **Official Mint Portal:**
{% embed url="" %}
***
### Option B — Delegate a Level 10 Node License (Active Ambassador Path)
HyperCycle operators and infrastructure builders may join CMHPEC DAO by **delegating a Level 10 HyperCycle Node License**.
#### How This Works
* The delegated license is used to create Node Factories
* Those Node Factories become **permanent CMHPEC DAO infrastructure**
* The participant receives a **CMHPEC DAO PASS**
* Participation is represented by the DAO PASS, not by ownership of specific factories
#### Important Constraints
* Node Licenses are **not resold**
* Node Factories are **not individually owned**
* Infrastructure remains stable, continuous, and DAO-coordinated
This path is designed for **Active Ambassadors** who want to expand real compute infrastructure.
***
### CMHPEC Node Factory Infrastructure
* CMHPEC DAO currently includes:
* **33 Node Factories delegated by HPEC DAO**
* Additional Node Factories are added through:
* Level 10 license delegation
* DAO-approved expansion initiatives
* Strategic ecosystem growth
All Node Factories:
* Operate as shared DAO infrastructure
* Support ANaaS, AaaS, and Autonomous Web Infrastructure
* Are never fragmented or liquidated
When a new participant joins by delegating **1 Level 10 Node License**: You get 1 ( CMHPEC NFT - Only 400 ).
> New members enter a live pool that already includes **32 DAO-backed Node Factories**, not an empty system.
***
### Participation, Transferability & Exit
* Participation in CMHPEC DAO is represented **only** by the CMHPEC DAO PASS (NFT)
* The NFT is transferable
* Node Licenses and Node Factories remain within the DAO
* Exiting the ecosystem occurs by transferring or selling the NFT
* There is **no dismantling or resale of infrastructure assets**
This preserves:
* Network continuity
* Operational stability
* Governance clarity
***
### Design Principles (Why This Model Exists)
* Infrastructure is permanent and non-fragmented
* Participation is abstracted through NFTs
* Governance replaces bilateral agreements
* Value is represented structurally and socially, not contractually
* CMHPEC DAO coordinates infrastructure, not individual claims
***
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://hyper-performance-edge-computing.gitbook.io/hyper-performance-edge-computing-hpec-dao-docs/documentation/basics-execution-layer/integrations/economic-framework/economic-initiatives/cmhpec-dao-pass.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.