HolyCode White Paper

DAO-first strategy: capital plan, tokenomics, and public-market entry

HolyCode remains a community and philosophy focused on healthy collaboration between people and AI, with products HolyAgent, HolyChat, and HolyBuild. This paper defines the financial and token pipeline: DAO distribution and business scale first (including data-center infrastructure), controlled public-market entry second.

Version

v0.1 (Investor Draft)

Publication Date

March 5, 2026

Status

DAO First -> Public Later

Opens browser print dialog. Save as PDF.

Core Thesis

  • • HolyCode is designed as a healthy-society model where people and AI operators collaborate in one productive loop.
  • • Public listing is not activated at an early stage before product and governance readiness metrics are met.
  • • Business-first priority: revenue, B2B distribution, and adoption of HolyAgent/HolyBuild/HolyChat.
  • • A separate revenue track comes from HolyDC: owned data centers and leased agent-compute capacity.
  • • Daenerys remains a private internal onboarding layer and is not marketed as a public token product.

Launch Pipeline

  • • Phase 1: DAO Internal Distribution (private rounds, role-tier access, governance bootstrap).
  • • Phase 2: Product & Revenue Scale (paying-customer growth, treasury discipline, contract audits, and HolyDC pilot-capacity launch).
  • • Phase 3: Public Market Entry (limited unlock, liquidity setup, listing by governance decision).

HolyAgent Memory Architecture

Core technical thesis for the HolyCode stack

  • • HolyAgent operates as the memory core: internal context structure remains stable regardless of the external AI provider in use.
  • • The product stack is layered as HolyAgent (entry + automation) -> HolyChat (multi-agent coordination) -> HolyBuild (delivery execution).
  • • The runtime is multi-model by design (OpenAI, Anthropic, Google, and others) with fast provider switching.
  • • A multi-agent execution layer reuses shared memory across HolyChat/HolyBuild tasks, preserving context continuity and improving delivery speed.

Role Marketplace and HolyAgent Wallet

Economics of trained roles and automation flows

  • • Role packs are trained in HolyAgent, tested, and published through Daenerys for controlled sharing.
  • • Teams attach those role packs to their LLM providers and execute with already-trained contextual memory.
  • • Role usage rewards are credited in HCODE to an internal HolyAgent balance.
  • • Internal balances can be synchronized to external EVM wallets for withdrawal and exchange under launch policy.
  • • Baseline role-marketplace revenue split: 70% creator, 20% DAO treasury, 10% AI-Agent Reserve.

Target raise before public stage

$6,000,000

covers runway, audit, legal, and liquidity preparation

Total Supply

1,000,000,000 HCODE

fixed DAO-token emission

Target HolyDC capacity before PME

0.5 - 1.0 MW

managed hosting for agent workloads and B2B contracts

Circulating supply at public launch

120,000,000 HCODE (12%)

88% remains locked at launch

Target initial price range

$0.08 - $0.12

controlled market-entry corridor

Target circulating market cap

$9.6M - $14.4M

at Public Market Entry event

Implied FDV range

$80M - $120M

at full 1B HCODE supply

Readiness Gates Before Public

  • • ARR >= $1.5M across HolyCode business lines.
  • • 100+ paying organizations in B2B/B2G pipeline.
  • • At least 1 operating HolyDC pilot site with SLA >= 99.5%.
  • • 500+ active DAO members in monthly governance cycle.
  • • At least 2 independent smart-contract audits.
  • • Treasury runway >= 18 months after public liquidity launch.

Fundraising Rounds (Pre-Public)

Base-case financial scenario for investor disclosure

Round Tokens Supply Share Price Raise Lock / Vesting
DAO Seed (Member/Angel) 20,000,000 HCODE 2.00% $0.03 $600,000 12m cliff + 18m linear
Strategic Round 40,000,000 HCODE 4.00% $0.06 $2,400,000 6m cliff + 24m linear
Growth Round (Pre-Public) 37,500,000 HCODE 3.75% $0.08 $3,000,000 3m cliff + 18m linear

Total pre-public sale: 97,500,000 HCODE (9.75% supply), total raise $6,000,000.

DAO Investor Conversion into Public Tokens

Settlement framework at Public Market Entry (PME)

Round DAO Instrument Conversion Rule Settlement @ PME Post-PME Vesting
DAO Seed Seed Allocation Units (SAU) 1 SAU = 1 HCODE 15% unlock (within global private-round cap) 85% linear over 18 months
Strategic Round Strategic Token Allocation Units (STAU) 1 STAU = 1 HCODE 20% unlock (within global private-round cap) 80% linear over 24 months
Growth Round Growth Allocation Units (GRAU) 1 GRAU = 1 HCODE 25% unlock (within global private-round cap) 75% linear over 18 months

Combined private-round unlock is capped at 3.0% of total supply at PME. Any excess is automatically shifted into vesting.

Public Launch Unlock Policy

Token unlock schedule at Public Market Entry (PME Event)

Bucket Unlock @ PME Tokens Notes
Public Sale + Liquidity Pool 6.0% 60,000,000 public float + CEX/DEX liquidity
Private Rounds (partial unlock) 3.0% 30,000,000 remaining balances stay under vesting
Community Rewards 1.5% 15,000,000 onboarding and ecosystem activation
Staking/Governance Incentives 1.0% 10,000,000 governance bootstrap
Treasury Operational Unlock 0.5% 5,000,000 governance-approved reserve

Total unlock @ PME: 120,000,000 HCODE (12.0%). Launch locked supply: 880,000,000 HCODE (88.0%).

Use of Funds (Plan)

Allocation of raised $6M

Stream % Budget What it funds
Product Build 28% $1,680,000 HolyAgent/HolyBuild/HolyChat roadmap delivery
Go-To-Market 22% $1,320,000 sales, partnerships, enterprise onboarding
HolyDC Infrastructure Build 20% $1,200,000 pilot site, compute racks, network, and operations setup
Security + Legal + Audit 15% $900,000 smart contracts, compliance, legal setup
Liquidity Preparation 10% $600,000 listing readiness and market operations
DAO Operations 5% $300,000 community, governance tooling, reporting

AI-Agent Allocation

A fixed 6% of total supply is reserved for AI-Agent execution layers inside Community & Ecosystem Rewards. This reserve powers autonomous HolyAgent/HolyBuild execution flows and can be released only under governance rules with public reporting.