Files
skills/public/hanzo-hips.html
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

292 lines
30 KiB
HTML

<!doctype html>
<html lang="en"><head>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>hanzo-hips</title>
<meta name="color-scheme" content="dark">
<style>
/* Committed to one visual world: a dark instrument panel. No light variant —
the dot field and the hairline rules only read on black, and a naive
inversion would wash both out. Every colour is painted explicitly so the page
never borrows a host background. */
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
:root{
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
--font-zen-pixel-square:'Zen Pixel Square',monospace;
--mono:var(--font-zen-mono);
--sans:var(--font-zen-sans);
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
--r:999px; --r-soft:14px;
}
*{box-sizing:border-box}
html{-webkit-text-size-adjust:100%}
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
/* The dot field. A halftone made of one repeating radial-gradient, faded out
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
/* No overflow clip here: the dot field is inset to the box already, and a clip
would cut off the copy-prompt menu. */
.hero{position:relative;border-bottom:1px solid var(--line)}
.hero::before{content:"";position:absolute;inset:0;
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
background-size:7px 7px;
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
pointer-events:none}
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
nav{border-bottom:1px solid var(--line)}
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
justify-content:space-between;align-items:center;gap:1rem}
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--ink);text-decoration:none;
display:inline-flex;align-items:center;gap:.6rem}
.brand i{font-style:normal;color:var(--faint)}
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--soft);text-decoration:none}
nav a.up:hover{color:var(--ink)}
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
h1 em{font-style:normal;color:var(--faint)}
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
line-height:1.2;font-weight:400}
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
.btn.solid:hover{background:#d8d8d4}
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
/* Copy-prompt selector. Each row copies the prompt for its own target. */
.copy{position:relative;display:inline-flex}
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
padding:.4rem;display:flex;flex-direction:column;
box-shadow:0 12px 32px rgba(0,0,0,.75)}
.menu[hidden]{display:none}
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
white-space:nowrap}
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
.mi:hover .mark{color:var(--ink)}
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
letter-spacing:.1em;text-transform:uppercase}
/* Works-with bar: one scrolling row, name and mark per agent. */
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
display:flex;align-items:center}
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
-webkit-overflow-scrolling:touch;
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
.bar::-webkit-scrollbar{display:none}
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
text-decoration:none;background:var(--ground)}
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
.agent .mark{width:.95rem;height:.95rem}
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
p{margin:0 0 1rem;max-width:70ch}
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
li{margin:.22rem 0}
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
text-decoration-color:var(--line-hi)}
a:hover{text-decoration-color:var(--ink)}
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
display:block;overflow-x:auto}
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
.curl{display:block;background:var(--panel);border:1px solid var(--line);
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
white-space:pre;line-height:1.9}
.curl b{color:var(--ink);font-weight:400}
.curl i{font-style:normal;color:var(--faint)}
/* index */
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
#q:focus{outline:none;border-color:var(--soft)}
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
text-transform:uppercase;margin:0 0 2rem}
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
padding-bottom:.45rem}
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
border-radius:var(--r-soft);text-decoration:none}
.row:hover{background:#0a0a0a}
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
color:var(--faint);font-size:.85rem}
footer a{color:var(--soft)}
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
margin:0 0 2rem;font-size:.85rem}
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
border-bottom:1px solid var(--line);padding-bottom:.4rem}
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
.fmap a:hover{text-decoration:underline}
.fmap div{color:var(--faint);line-height:1.5}
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
@media (max-width:640px){
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
.btns{gap:.5rem}
.btn{padding:.75rem 1.15rem;font-size:.68rem}
.copy,.copy .btn{width:100%;justify-content:center}
.menu{left:0;right:0;min-width:0}
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
.strip b{border-right:0;padding-right:0}
.bar{width:100%}
}
</style>
<link rel="alternate" type="text/markdown" href="/hanzo-hips.md">
<link rel="icon" href="/favicon.svg">
<link rel="canonical" href="https://hanzoskills.com/hanzo-hips">
</head>
<!-- Reading this with a machine? Every page here is also plain markdown.
This one: https://hanzoskills.com/hanzo-hips.md
Index: https://hanzoskills.com/llms.txt
Corpus: https://hanzoskills.com/all.md
Append .md to any path for the markdown twin. -->
<body>
<nav><div class="in">
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
<a class="up" href="/">All skills</a>
</div></nav>
<div class="wrap">
<h1>hanzo-hips</h1><p class="lede">Hanzo Improvement Proposals (HIPs) are the primary mechanism for proposing new features, gathering community input, and documenting design decisions for the Hanzo AI ecosystem.</p><h1>Hanzo Improvement Proposals (HIPs)</h1>
<p>Hanzo Improvement Proposals (HIPs) are the primary mechanism for proposing new features, gathering community input, and documenting design decisions for the Hanzo AI ecosystem. HIPs serve as formal design documents that provide information to the community about proposed changes to the platform.</p>
<p>Repository: github.com/hanzoai/hips Website: hips.hanzo.ai License: CC0 1.0 Universal Public Domain Dedication</p>
<h2>What HIPs Cover</h2>
<ul><li>AI architectures, models, and infrastructure</li><li>Standards for agent frameworks, protocols, and interfaces</li><li>Blockchain and consensus mechanisms</li><li>Infrastructure services (databases, security, networking)</li><li>Governance and responsible AI practices</li><li>Cross-chain integrations with Lux and Zoo ecosystems</li></ul>
<h2>HIP Types</h2>
<ul><li><strong>Standards Track</strong>: Technical changes affecting Hanzo AI (subtypes: Core, Interface, Infrastructure, Bridge, Security)</li><li><strong>Meta</strong>: Process proposals, governance, responsible AI</li><li><strong>Informational</strong>: Guidelines and best practices</li></ul>
<h2>HIP Lifecycle</h2>
<p>Draft -&gt; Review -&gt; Last Call (14-day final review) -&gt; Final (or Withdrawn/Superseded)</p>
<h2>Core Protocol HIPs (Root Level)</h2>
<h3>HIP-001: Post-Quantum Cryptography Standard</h3>
<ul><li><strong>Status</strong>: Implemented</li><li><strong>Category</strong>: Security</li><li>Establishes post-quantum cryptography using ML-DSA-87 (FIPS 204) for digital signatures and ML-KEM-768 (FIPS 203) for key encapsulation</li><li>All implementations use the <code>hanzo-crypto</code> library (pure Rust, constant-time, automatic secret zeroization)</li><li>Hybrid signatures (classical + PQ) supported during migration from Ed25519/X25519</li></ul>
<h3>HIP-002: AI/Blockchain Convergence Architecture</h3>
<ul><li><strong>Status</strong>: In Development</li><li><strong>Category</strong>: Core</li><li>Defines on-chain model registry, decentralized multi-node inference with BFT consensus, zero-knowledge ML proofs (zkSNARKs for small models, optimistic rollups for large), and an inference marketplace with reputation-based node selection and slashing</li></ul>
<h3>HIP-002-ASO: Active Semantic Optimization Protocol</h3>
<ul><li><strong>Status</strong>: Active</li><li><strong>Category</strong>: Core</li><li>Training-free adaptation framework for agentic code generation using TF-GRPO (Training-Free Group-Relative Policy Optimization) and decode-time Product-of-Experts (PoE) ensemble</li><li>1-bit compression via BitDelta (29.5x compression, 1 bit per element + 1 scalar per matrix)</li><li>SWE-bench Verified: 18.2% resolved rate (vs 12.5% Claude 3.5 Sonnet agentic, 8.3% GPT-4 zero-shot)</li><li>CLI: <code>hanzo dev solve &lt;issue_file&gt; --repo &lt;path&gt; --group-size 4 --test-cmd &quot;pytest&quot;</code></li><li>Extended by Zoo&#x27;s ZIP-001 (Decentralized Semantic Optimization)</li></ul>
<h3>HIP-003: Model Context Protocol (MCP) Integration</h3>
<ul><li><strong>Status</strong>: Active</li><li><strong>Category</strong>: Interface</li><li>Standardizes MCP across all Hanzo services with stdio, HTTP, and WebSocket transports</li><li>Tool categories: Blockchain (query/submit/verify/subscribe), AI (list/deploy/inference), Cryptography (ML-DSA sign, ML-KEM encrypt, BLAKE3 hash), Storage (IPFS/Arweave)</li><li>All tool calls signed with ML-DSA, parameters encrypted with ML-KEM</li></ul>
<h3>HIP-004: Hamiltonian Market Maker (HMM)</h3>
<ul><li><strong>Status</strong>: Active</li><li><strong>Category</strong>: Core</li><li>Automated market maker for pricing heterogeneous AI compute resources via conserved Hamiltonian invariants</li><li>Single-asset invariant: H(Psi, Theta) = Psi * Theta = kappa (constant-product)</li><li>Multi-asset: H(Psi, Theta) = sum(wi <em> Psi_i </em> Theta_i) + lambda * sum((Psi_i^2 + Theta_i^2)/2)</li><li>Oracle-free pricing, risk-adjusted fees, PoAI-integrated settlement</li><li>Job lifecycle: Escrow -&gt; Allocation -&gt; Execution -&gt; Attestation (PoAI) -&gt; Verification -&gt; Settlement</li><li>Testnet: 182ms quote latency, 98.7% price stability, +15.3% capital efficiency vs oracle-based</li></ul>
<h3>HIP-005: KMS Hardware Security Module Integration</h3>
<ul><li><strong>Status</strong>: Active</li><li><strong>Category</strong>: Infrastructure</li><li>Extends Lux KMS (LP-325) with AI-specific features: model weight encryption (AES-256-GCM), PoAI attestation signing, HMM settlement key management</li><li>HSM providers: Google Cloud KMS, AWS CloudHSM, YubiHSM 2 FIPS, Zymbit HSM6, SoftHSM2 (dev)</li><li>Multi-tenant key isolation with per-model/per-customer namespaces</li><li>Go API: <code>github.com/hanzoai/kms</code></li></ul>
<h3>HIP-006: AI Mining Protocol</h3>
<ul><li><strong>Status</strong>: Draft</li><li><strong>Category</strong>: Core</li><li>Native AI compute mining on Hanzo L1 with quantum-safe ML-DSA wallets</li><li>NVTrust chain-binding prevents double-spend: each unit of AI work bound to a specific chain BEFORE compute runs</li><li>GPU TEE receipts signed by NVIDIA hardware attestation (H100, H200, B100, B200, GB200 supported)</li><li>Rewards teleportable to Hanzo EVM (36963), Zoo EVM (200200), or Lux C-Chain (96369)</li><li>EVM precompile at 0x0300 for on-chain mining balance and ML-DSA verification</li><li>Reference implementation: <code>github.com/hanzoai/node</code> (hanzo-mining crate)</li></ul>
<h3>HIP-007: ZAP (Zero-copy Agent Protocol)</h3>
<ul><li><strong>Status</strong>: Draft</li><li><strong>Category</strong>: Interface</li><li>High-performance binary RPC protocol using Cap&#x27;n Proto serialization, replacing JSON-RPC for AI agent communication</li><li>10-100x performance over MCP JSON-RPC: 0.2us parse latency vs 45us (1KB), 0 memory allocations per message</li><li>MCP-compatible semantics (tools, resources, prompts) with gateway bridging to existing MCP servers</li><li>Transports: TCP (zap://), TLS (zaps://), Unix socket, WebSocket, HTTP/2, stdio</li><li>Promise pipelining: chain RPC calls without round-trip latency</li><li>Also adopted by Lux Network (LP-120) for VM-Node communication, consensus voting</li><li>Packages: <code>hanzo-zap</code> (Rust), <code>@hanzo/zap</code> (TypeScript), <code>hanzo-zap</code> (Python)</li></ul>
<h3>HIP-008: Unified Payment Platform</h3>
<ul><li><strong>Status</strong>: Draft</li><li><strong>Category</strong>: Infrastructure</li><li>Self-hosted payment infrastructure with three-zone isolation, designed to the PCI DSS v4.0 control set</li><li>Zone 3 (Vault CDE): card tokenization with AES-256-GCM envelope encryption, network tokenization (Visa VTS, Mastercard MDES)</li><li>Zone 2 (Commerce): payment intent orchestration, multi-processor routing (Stripe, Adyen, Square, PayPal, Braintree), double-entry ledger, subscription engine (Temporal workflows)</li><li>Crypto payments: BTC (on-chain + Lightning), ETH, ERC-20 (custodial and non-custodial)</li><li>mTLS with SPIFFE/SPIRE identity attestation between zones</li><li>Repositories: <code>hanzoai/vault</code>, <code>hanzoai/commerce</code></li></ul>
<h3>HIP-009: Unified Agent Skills Architecture</h3>
<ul><li><strong>Status</strong>: Draft</li><li><strong>Category</strong>: Interface</li><li><code>~/.hanzo/skills/</code> as canonical source of truth for all AI agent skills</li><li>Automatic symlink distribution to Claude Code, Cursor, Codex, , Hanzo Bot directories</li><li>Follows open Agent Skills specification (agentskills.io)</li><li>Install: <code>npx @hanzo/bot skills add org/repo</code></li><li>Multi-brand support: Bootnode, Hanzo Web3, Lux Cloud, Zoo Labs, Pars Cloud</li></ul>
<h2>Expanded HIPs (HIPs/ Subdirectory)</h2>
<h3>Foundation and Models (HIP-0000 to HIP-0010)</h3>
<p>| HIP | Title | Status | |-----|-------|--------| | HIP-0000 | Hanzo AI Architecture and Framework | Final | | HIP-0001 | AI Token (Hanzo Native Currency) | Draft | | HIP-0002 | Hamiltonian Large Language Models (HLLMs) | Draft | | HIP-0003 | Jin Multimodal AI Architecture | Draft | | HIP-0004 | LLM Gateway (Unified AI Provider Interface) | Draft | | HIP-0005 | Post-Quantum Security for AI Infrastructure | Final | | HIP-0006 | Per-User Fine-Tuning Architecture | Draft | | HIP-0007 | Active Inference Integration for HLLMs | Draft | | HIP-0008 | HMM Native DEX for AI Compute Resources | Draft | | HIP-0009 | Agent SDK (Multi-Agent Orchestration) | Draft | | HIP-0010 | MCP Integration Standards | Draft |</p>
<h3>Application Interfaces (HIP-0011 to HIP-0025)</h3>
<p>| HIP | Title | Status | |-----|-------|--------| | HIP-0011 | Chat Interface Standard | Draft | | HIP-0012 | Search Interface Standard | Draft | | HIP-0013 | Workflow Execution Standard | Draft | | HIP-0014 | Application Deployment Standard | Draft | | HIP-0015 | Computer Control Standard | Draft | | HIP-0016 | Document Processing Standard | Draft | | HIP-0017 | Analytics Event Standard | Draft | | HIP-0018 | Payment Processing Standard | Draft | | HIP-0019 | Tensor Operations Standard | Draft | | HIP-0020 | Blockchain Node Standard | Draft | | HIP-0021 | Hanzo IDE | Draft | | HIP-0022 | Personalized AI (Own Your AI) | Draft | | HIP-0023 | Decentralized AI Compute Swarm Protocol | Draft | | HIP-0024 | Hanzo Sovereign L1 Chain Architecture | Final | | HIP-0025 | Bot Agent Wallet and RPC Billing Protocol | Draft |</p>
<h3>Infrastructure Services (HIP-0026 to HIP-0068)</h3>
<p>| HIP | Title | Status | |-----|-------|--------| | HIP-0026 | Identity and Access Management Standard | Draft | | HIP-0027 | Secrets Management Standard | Draft | | HIP-0028 | Key-Value Store Standard | Draft | | HIP-0029 | Relational Database Standard | Draft | | HIP-0030 | Event Streaming Standard | Draft | | HIP-0031 | Observability and Metrics Standard | Draft | | HIP-0032 | Object Storage Standard | Draft | | HIP-0033 | Container Registry Standard | Draft | | HIP-0034 | Automation Platform Standard | Draft | | HIP-0035 | Image and Video Generation Standard | Draft | | HIP-0036 | CI/CD Build System Standard | Draft | | HIP-0037 | AI Cloud Platform Standard | Draft | | HIP-0038 | Admin Console Standard | Draft | | HIP-0039 | Zen Model Architecture | Draft | | HIP-0040 | Multi-Language SDK Standard | Draft | | HIP-0041 | CLI Standard | Draft | | HIP-0042 | Vector Search Standard | Draft | | HIP-0043 | LLM Inference Engine Standard | Active | | HIP-0044 | API Gateway Standard | Active | | HIP-0045 | Documentation Framework Standard | Draft | | HIP-0046 | Embeddings Standard | Draft | | HIP-0047 | Analytics Datastore Standard | Draft | | HIP-0048 | Decentralized Identity (DID) Standard | Draft | | HIP-0049 | DNS Service Standard | Draft | | HIP-0050 | Edge AI Runtime Standard | Active | | HIP-0051 | Guard Security Standard | Draft | | HIP-0052 | Nexus Integration Hub Standard | Draft | | HIP-0053 | Visor Monitoring Standard | Draft | | HIP-0054 | Zero Trust Architecture Standard | Draft | | HIP-0055 | Message Queue Standard | Draft | | HIP-0056 | PubSub Real-Time Messaging Standard | Draft | | HIP-0057 | ML Pipeline and Training Standard | Draft | | HIP-0058 | Unified Database Abstraction Standard | Draft | | HIP-0059 | Timeseries Database Standard | Draft | | HIP-0060 | Serverless Functions (FaaS) Standard | Draft | | HIP-0061 | Notification Service Standard | Draft | | HIP-0062 | Cron and Job Scheduler Standard | Draft | | HIP-0063 | Feature Flags Standard | Draft | | HIP-0064 | Log Aggregation Standard | Draft | | HIP-0065 | Backup and Disaster Recovery Standard | Draft | | HIP-0066 | Data Governance Standard | Draft | | HIP-0067 | Federated Learning Standard | Draft | | HIP-0068 | Ingress Standard | Active |</p>
<h3>Quantum Computing (HIP-0070 to HIP-0073)</h3>
<p>| HIP | Title | Status | |-----|-------|--------| | HIP-0070 | Quantum Computing Integration | Draft | | HIP-0071 | Quantum Key Distribution | Draft | | HIP-0072 | Quantum Machine Learning | Draft | | HIP-0073 | Quantum Random Number Generation | Draft |</p>
<h3>Governance and Supply Chain (HIP-0074 to HIP-0076)</h3>
<p>| HIP | Title | Status | |-----|-------|--------| | HIP-0074 | Software Bill of Materials Standard | Draft | | HIP-0075 | OSS Contributor Payout Standard | Draft | | HIP-0076 | Open AI Protocol Standard | Draft |</p>
<h3>Robotics and Physical AI (HIP-0080 to HIP-0083)</h3>
<p>| HIP | Title | Status | |-----|-------|--------| | HIP-0080 | Robotics and Embodied AI Integration | Draft | | HIP-0081 | Computer Vision Pipeline Standard | Draft | | HIP-0082 | Digital Twin and Simulation Standard | Draft | | HIP-0083 | Sensor Fusion and SLAM Standard | Draft |</p>
<h3>Biotech and Life Sciences (HIP-0090 to HIP-0096)</h3>
<p>| HIP | Title | Status | |-----|-------|--------| | HIP-0090 | Brain-Computer Interface (BCI) Standard | Draft | | HIP-0091 | Genomics Pipeline Standard | Draft | | HIP-0092 | Drug Discovery AI Pipeline Standard | Draft | | HIP-0093 | Synthetic Biology and DNA Data Storage | Draft | | HIP-0094 | Medical AI and Clinical Decision Support | Draft | | HIP-0095 | QoS Challenge System | Draft | | HIP-0096 | AI Compute Contribution Rewards | Draft |</p>
<h3>Cross-Chain, Responsible AI, and Architecture</h3>
<p>| HIP | Title | Status | |-----|-------|--------| | HIP-0101 | Hanzo-Lux Bridge Protocol Integration | Draft | | HIP-0200 | Responsible AI Principles | Draft | | HIP-0201 | Model Risk Management | Draft | | HIP-0210 | Safety Evaluation Framework | Draft | | HIP-0220 | Bias Detection and Mitigation | Draft | | HIP-0230 | AI Transparency and Explainability | Draft | | HIP-0240 | AI Incident Response | Draft | | HIP-0250 | Sustainability Standards Alignment | Draft | | HIP-0251 | AI Compute Carbon Footprint | Draft | | HIP-0260 | Efficient Model Practices | Draft | | HIP-0270 | AI Supply Chain Responsibility | Draft | | HIP-0280 | AI for Sustainability | Draft | | HIP-0290 | Evidence Locker Index | Draft | | HIP-0295 | Hanzo AI Impact Thesis | Draft | | HIP-0300 | Unified MCP Tools Architecture | Draft |</p>
<h2>Key Protocols</h2>
<h3>ASO (Active Semantic Optimization) - HIP-002-ASO</h3>
<p>Training-free adaptation for code generation. Uses grouped rollouts to extract semantic advantages, compresses them into token-level expert factors via BitDelta (1-bit quantization), and applies them at decode time via Product-of-Experts. No weight updates needed. Extended by Zoo&#x27;s DSO (ZIP-001) for decentralized aggregation.</p>
<h3>HMM (Hamiltonian Market Maker) - HIP-004</h3>
<p>Prices heterogeneous AI compute (GPU, VRAM, CPU, network, disk) using physics-inspired Hamiltonian invariants. Oracle-free: price emerges from the constant H = kappa constraint. Integrated with Zoo&#x27;s PoAI (ZIP-002) for quality verification. Supports multi-asset routing with SLA constraints solved as a convex program.</p>
<h3>ZAP (Zero-copy Agent Protocol) - HIP-007</h3>
<p>Binary RPC protocol built on Cap&#x27;n Proto. Zero memory allocations per message parse. Drop-in replacement for MCP JSON-RPC with full semantic compatibility and gateway bridging. Used for agent-to-agent communication, HMM settlement, and Lux infrastructure.</p>
<h3>AI Mining Protocol - HIP-006</h3>
<p>GPU-based AI compute mining with NVTrust hardware attestation. Each job pre-commits to a target chain (Hanzo/Zoo/Lux) before compute runs, preventing double-spend across chains. Rewards are native L1 tokens, teleportable to any EVM chain via Lux Teleport bridge.</p>
<h2>Relationship to Lux Proposals (LPs) and Zoo Proposals (ZIPs)</h2>
<h3>Hanzo &lt;-&gt; Lux</h3>
<ul><li>Hanzo operates as a sovereign L1 on Lux Network (HIP-0024)</li><li>Hanzo KMS (HIP-005) extends Lux KMS (LP-325)</li><li>ZAP (HIP-007) adopted by Lux as LP-120</li><li>Hanzo-Lux Bridge Protocol (HIP-0101)</li><li>Shared post-quantum cryptography standards</li><li>AI Mining rewards teleportable to Lux C-Chain (96369)</li></ul>
<h3>Hanzo &lt;-&gt; Zoo</h3>
<ul><li>ASO (HIP-002) extended by Zoo&#x27;s DSO (ZIP-001) for decentralized prior aggregation</li><li>HMM (HIP-004) uses Zoo&#x27;s PoAI (ZIP-002) for quality verification and attestation</li><li>Zoo AI Mining Integration (ZIP-005)</li><li>Shared HLLM architecture and model portability</li><li>Zoo EVM (200200) is a mining reward destination</li></ul>
<h3>Key Differences</h3>
<ul><li><strong>HIPs</strong>: Hanzo-specific standards for AI infrastructure, services, and L1 chain</li><li><strong>LPs</strong>: Lux blockchain standards for consensus, networking, cross-chain protocols</li><li><strong>ZIPs</strong>: Zoo Foundation standards for decentralized AI research, training, and governance</li></ul>
<h2>HANZO Tokenomics (1B total supply)</h2>
<p>| Allocation | Percentage | |-----------|-----------| | Training Rewards | 30% | | Compute Providers | 20% | | Model Developers | 15% | | Community Treasury | 15% | | Team (4yr vest) | 10% | | Public Sale | 5% | | Liquidity | 5% |</p>
<p>Token utility: 0.01 HANZO per interaction, 0.001-0.1 per 1K tokens, 10+ to mint Model NFT, veHANZO governance.</p>
<h2>Creating a New HIP</h2>
<ol><li>Copy <code>docs/templates/hip-template.md</code> to <code>HIPs/hip-X.md</code></li><li>Submit PR to github.com/hanzoai/hips</li><li>HIP editors review for completeness</li><li>Community discussion and feedback</li><li>Last Call (14-day review period)</li><li>Final status if accepted</li></ol>
<h2>Validation</h2>
<pre><code class="lang-bash">make validate-hip HIP=hip-X # Format check
make check-links # Reference check
act -j validate # Local CI</code></pre>
<hr>
<p>Last Updated: 2026-03-13</p>
<footer>
<div class="fmap">
<div><b>Build</b>
<a href="https://hanzo.app">hanzo.app</a> app builder
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
<div><b>Run</b>
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
<div><b>Account</b>
<a href="https://hanzo.id">hanzo.id</a> sign in
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
<div><b>Company</b>
<a href="https://hanzo.ai">hanzo.ai</a> canonical
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
</div>
<div class="fend"><a href="/hanzo-hips.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
</footer>
</div></body></html>