> 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/participation-roles/active-ambassadors.md). # Active Ambassadors Active Ambassadors delegate Node Licenses to create HyperCycle Node Factories. Node Factories are operated by Node Operator Authorities under DAO governance, powering services and reinvesting rewards ## Active Ambassadors of HPEC DAO HPEC DAO is built one node at a time, by people who run the infrastructure themselves. ### Overview Active Ambassadors are the backbone of HPEC DAO’s global expansion. They are the participants who **activated the first Node Factories**, coordinated early DAO-operated infrastructure, and continue to operate and expand the HPEC network across regions. Active Ambassadors are typically: * HyperAIBox node runners * Early HyperCycle participants * Node Factory operators * License delegators * DAO-aligned builders Rather than relying on centralized deployment, Active Ambassadors activated **Node Factories one license at a time**, across countries, networks, and strategic partnerships. This represents a **grassroots, bottom-up deployment of HyperCycle infrastructure**, coordinated through DAO governance. *** ### Early Active Ambassadors — Bootstrap Phase (Historical) During the bootstrap phase of HPEC DAO: * HyperCycle infrastructure was early-stage * Node Factory abstractions did not yet exist * HYPC prices were significantly higher than today * Infrastructure risk was materially higher To enable the network, early Active Ambassadors coordinated the delegation of **10,240 HYPC per activation**, enabling the creation of the **first DAO-operated Node Factories**. This phase resulted in: * The formation of a DAO of Node Operators * The activation of **Node Factory #1 of HPEC DAO** * Multi-region coordination without centralized custody * The foundation for CMHPEC and DAO abstraction layers This bootstrap mechanism is **historical** and is no longer a requirement for new participation. *** ### Quantified Infrastructure Activation (Preserved Data) #### HPEC DAO — Node Factory #1 (Primary Initiative) Node Factory #1 is not the **largest coordinated Node Factory initiative** within HPEC DAO. As [HPEC | CANADA](/hyper-performance-edge-computing-hpec-dao-docs/documentation/basics-execution-layer/integrations/economic-framework/regional-dao-framework/hpec-or-canada.md)currently is managing more Node Factories . But **Node Factory #1** is created with the first Node Licences which has more reputation . Over time we are going to learn which node factories unlock first . **Aggregated Infrastructure Metrics (Snapshot):** * **Total Node Factories activated:** 180+ * **Primary networks:** Ethereum & Base * **HYPC utilized:** \~195,584 HYPC * **Activation method:** Delegated Node Licenses * **Custody model:** Non-custodial, operator-held keys * **Coordination:** DAO-governed Node Operator Authorities These Node Factories were activated through **human coordination and shared governance**, not centralized control. *** ### Aggregated Ambassador Contributions (Privacy-Preserving) To preserve privacy while remaining transparent, HPEC DAO aggregates Active Ambassador contributions rather than listing individuals. **Contribution characteristics include:** * Delegation of Level-based Node Licenses * Shared licensing across strategic partners * DAO-covered activations during early phases * Long-term operational commitment This approach demonstrates **real economic and operational commitment** while respecting contributor privacy. *** ### Evolution of the Active Ambassador Model As the HPEC ecosystem matured: * Node Factory tooling stabilized * DAO abstraction layers (CMHPEC) were introduced * Infrastructure scale surpassed 1,000+ Node Factories across HPEC DAOs * Participation no longer needed fixed HYPC thresholds Today, Active Ambassador participation is based on: * Delegation of Node Licenses into DAO infrastructure * Operation under [Node Operator Authorities | NOA](/hyper-performance-edge-computing-hpec-dao-docs/documentation/basics-execution-layer/integrations/participation-roles/editor.md) * Participation via [CMHPEC DAO PASS](/hyper-performance-edge-computing-hpec-dao-docs/documentation/basics-execution-layer/integrations/economic-framework/economic-initiatives/cmhpec-dao-pass.md) * Long-term alignment with infrastructure expansion Infrastructure remains permanent.\ Participation is abstracted. *** ### Relationship to DAO PASS Initiatives Active Ambassador Node Factories: * Feed into DAO-governed infrastructure pools * Supported the **HPEC DAO PASS Proof of Concept** (148+ Node Factories) * Now expand capacity through **CMHPEC DAO PASS**, which includes: * 32 Node Factories already delegated by HPEC DAO * Additional Node Factories added over time This creates a continuous feedback loop: **Operators → Infrastructure → Services → Rewards → Reinvestment** *** ### Why Active Ambassadors Matter The Active Ambassador model demonstrates that: * HyperCycle infrastructure can scale without central operators * Node Factories grow through delegation + governance * Operators are stakeholders, not customers * DAO coordination outperforms isolated deployment * Global expansion can remain non-custodial Active Ambassadors are not contractors.\ They are **co-builders of the HPEC network**. *** ### Forward Outlook Active Ambassadors will continue to support: * New regional HPEC DAOs * Expanded Node Factory pools * ANaaS and AaaS service growth * DAO-driven economic initiatives All growth remains: * Non-custodial * Permissionless (within governance) * Transparent * DAO-governed --- # 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/participation-roles/active-ambassadors.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.