Files
skills/public/hip-0078.html

340 lines
26 KiB
HTML
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<!doctype html>
<html lang="en"><head>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>hip-0078</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="/hip-0078.md">
<link rel="icon" href="/favicon.svg">
<link rel="canonical" href="https://hanzoskills.com/hip-0078">
</head>
<!-- Reading this with a machine? Every page here is also plain markdown.
This one: https://hanzoskills.com/hip-0078.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>hip-0078</h1><p class="lede">HIP-78: Z-Chain — Post-Quantum Identity &amp; Attestation Rollup. Status Draft. Hanzo architectural specification.</p><h1>HIP-0078: Z-Chain — Post-Quantum Identity &amp; Attestation Rollup</h1>
<h2>Abstract</h2>
<p>Z-Chain is the post-quantum rollup for <strong>bulky identity, validator-set, DKG-transcript, and attestation state</strong> on the Lux primary network. It is <strong>post-quantum from v1</strong> — STARK / FRI over Goldilocks with cSHAKE-256 Merkle commitments. Pairing-based proof systems (Groth16 / BN254, KZG) are explicitly forbidden on the wire and refused by the strict-PQ verifier; the wire reserves IDs for them so audit pipelines name a misconfiguration precisely.</p>
<p>Z-Chain is the <strong>identity layer</strong>. Q-Chain (HIP-0079) is the <strong>finality layer</strong>. Pulsar-M (HIP-0084) is the <strong>threshold-signing primitive</strong> Q-Chain consumes. The three layers replace the prior single-chain &quot;all of the above&quot; design with a compact, fully-PQ stack:</p>
<pre><code>Lux primary network
├── Q-Chain (HIP-0079) small finality blocks, frequent, consensus-critical
├── Z-Chain (HIP-0078) PQ STARK/FRI rollup, bulky identity / validator state
└── Pulsar-M (HIP-0084) threshold ML-DSA DKG + signing (consumed by Q-Chain)</code></pre>
<p>The core principle: <strong>ML-DSA-65 identity material does not enter every finality block.</strong> Z-Chain holds the bulky state; Q-Chain references its roots; Pulsar-M produces the threshold cert that finalises the Q-Block.</p>
<h2>Motivation</h2>
<p>ML-DSA-65 public keys are 1.95 KB; signatures 3.31 KB (FIPS 204 Table 2). For a 64-validator committee, validator-set state runs to hundreds of kilobytes per epoch. Naively duplicating that into every finality block makes mainnet bandwidth dominated by static identity material; finality stalls every time the committee rotates.</p>
<p>The fix is a rollup chain that proves identity-state transitions and exposes only their roots to consensus — a standard L2 pattern applied to validator identity, but with the rollup proof system itself constrained to be PQ.</p>
<p>The earlier <code>quasar</code> mode (HIP-0077) rolled per-validator ML-DSA sigs into a Groth16 proof on a chain we initially called Z-Chain — but Groth16/BN254 is pairing-based, classically broken under Shor. That collapses the defense-in-depth claim. HIP-0078 fixes this by mandating a STARK / FRI / SHA-3 rollup as the <strong>v1</strong> Z-Chain — not &quot;later PQ&quot;, PQ from genesis. Groth16/BN254 is the explicit anti-pattern.</p>
<h2>Specification</h2>
<h3>Chain roles</h3>
<p>| chain | purpose | content | size profile | |------------|--------------------------------------|------------------------------------------------------------------------|---------------------| | Q-Chain | Quasar finality (HIP-0079) | compact finality blocks + roots | small, per-block | | Z-Chain | identity &amp; attestation rollup (this HIP) | validator registry, DKG transcripts, revocations, epoch commitments | bulky, per-epoch | | Pulsar-M | threshold signing (HIP-0084) | DKG ceremony state, threshold sigs | per-epoch + per-block |</p>
<p>Q-Chain references Z-Chain roots; Z-Chain produces those roots; the two chains are linked by <code>EpochCommitment</code> records and the rule that Q-Chain finality MUST anchor to the latest accepted Z-Chain epoch root.</p>
<h3>Z-Chain state</h3>
<pre><code>ZState {
validator_registry_root // hash-based authenticated tree
identity_root // ML-DSA-65 pubkey commitments
revocation_root // revoked / rotated keys
stake_weight_root // weights, slashing positions
dkg_epoch_root // accepted DKG transcripts
committee_selection_root // current epoch&#x27;s committee derivation
slashing_root // pending and applied slashes
}</code></pre>
<p>Every root is a hash-based authenticated tree head (Merkle / hash accumulator). No KZG, no pairing-friendly accumulators, no curve-based commitments. Hash family is exclusively FIPS 202 / SP 800-185.</p>
<h3>EpochCommitment</h3>
<pre><code>EpochCommitment {
version uint16
network_id uint32
chain_id uint32
epoch uint64
hash_suite_id HashSuiteID // = 0x01 SHA3_NIST canonical
sig_scheme_id SigSchemeID // = 0x52 Pulsar-M-65 default; 0x53 for high-value roots
proof_system_id ProofSystemID // = 0x10 STARK_FRI_SHA3_PQ canonical
validator_registry_root [32]byte
identity_root [32]byte
revocation_root [32]byte
stake_weight_root [32]byte
committee_root [32]byte
dkg_transcript_root [32]byte
group_public_key_hash [32]byte
zchain_state_root [32]byte
previous_epoch_commitment_hash [32]byte
}</code></pre>
<p>Each Q-Block (HIP-0079) MUST bind <code>zchain_state_root</code>, <code>validator_set_root</code>, <code>committee_root</code>, <code>dkg_transcript_root</code>, and <code>group_public_key_hash</code> to the latest accepted EpochCommitment for the current epoch.</p>
<h3>Z-Chain proof obligations (v1)</h3>
<p>Z-Chain produces a STARK proof per epoch transition that establishes:</p>
<ol><li><strong>Validator registration is valid.</strong> ML-DSA-65 identity signature</li></ol>
<p> verifies against the registering pubkey under unmodified FIPS 204 ML-DSA.Verify.</p>
<ol><li><strong>Validator update is valid.</strong> Previous key authorized the</li></ol>
<p> rotation to the new key (signed transition).</p>
<ol><li><strong>Revocation is valid.</strong> Revocation key or governance-path</li></ol>
<p> signature authorized the removal.</p>
<ol><li><strong>Stake / weight update is valid.</strong> Update follows the staking</li></ol>
<p> protocol; sum-conservation; no negative weights.</p>
<ol><li><strong>Committee selection is valid.</strong> Selected committee derives</li></ol>
<p> deterministically from <code>validator_registry_root</code> plus the epoch randomness beacon (Lux randomness layer; out of scope for this HIP).</p>
<ol><li><strong>DKG participant set matches committee.</strong> Pulsar-M DKG</li></ol>
<p> participants = <code>committee_root</code> entries; no impostors.</p>
<ol><li><strong>DKG transcript commitment is valid.</strong> Transcript root matches</li></ol>
<p> the accepted public messages from the Pulsar-M ceremony (HIP-0084 §&quot;Transcript binding&quot;).</p>
<ol><li><strong><code>group_public_key_hash</code> corresponds to accepted DKG output.</strong></li><li><strong>Q-Chain reference is consistent.</strong> Q-Block height that triggered</li></ol>
<p> the epoch transition has roots consistent with this EpochCommitment.</p>
<p>Out of scope for v1: per-block threshold-signing transcripts. Threshold sigs verify directly at Q-Chain via Pulsar-M&#x27;s public-key-based verifier; their soundness does not need a Z-Chain proof.</p>
<h3>Proof system</h3>
<p><strong>ProofSystemID = <code>STARK_FRI_SHA3_PQ</code> (0x10) is the only acceptable production proof system.</strong></p>
<p>| ID | name | status | |-------|-------------------------------------|-------------| | 0x00 | None | wire-only (no proof in this slot) | | 0x10 | <code>STARK_FRI_SHA3_PQ</code> | <strong>canonical</strong> — Plonky3-style, cSHAKE256 Merkle + Fiat-Shamir | | 0x11 | <code>STARK_FRI_KECCAK_PQ</code> | secondary — Keccak Merkle (FIPS 202; valid PQ alternative) | | 0x20 | <code>RISC_ZERO_STARK_RAW</code> | engineering prototype only — raw STARK receipt, no Groth16 wrapper | | 0x21 | <code>PLONKY3_STARK_FRI</code> | engineering prototype; Plonky3 toolkit direct use | | 0x80 | <code>GROTH16_BN254_CLASSICAL_FORBIDDEN_IN_PQ</code> | refusal marker — never produced in strict-PQ mode | | 0x81 | <code>KZG_CLASSICAL_FORBIDDEN_IN_PQ</code> | refusal marker |</p>
<p>Strict-PQ verifiers MUST refuse any cert whose <code>proof_system_id</code> returns true from <code>ProofSystemID.IsForbiddenInPQMode()</code>.</p>
<h3>Reference implementation</h3>
<p><strong>Recommendation: Plonky3 fork with cSHAKE256 Merkle + Fiat-Shamir.</strong></p>
<p>Sourcing notes:</p>
<ul><li>Plonky3 is a polynomial-IOP toolkit; we use its FRI + Merkle + AIR</li></ul>
<p> primitives but swap the default Keccak/SHA-256 hash for cSHAKE256 to align with FIPS 202 / SP 800-185 normative.</p>
<ul><li>Plonky3&#x27;s verifier has documented caveats (panic-on-malformed-proof</li></ul>
<p> warnings in its README); strict-PQ deployments MUST wrap the verifier with malformed-proof fuzzing as a launch gate.</p>
<ul><li>RISC Zero raw STARK (<code>0x20</code>) is acceptable as an engineering</li></ul>
<p> prototype path for proving the identity-registry state machine in Rust/RISC-V. <strong>Strict-PQ mainnet MUST NOT use the Groth16 receipt; use only the raw STARK / FRI receipt path.</strong> RISC Zero default parameters target ~98-bit conjectured security per their docs; production Z-Chain MUST configure to ≥ 128-bit classical and ≥ NIST PQ Cat 3 (matching ML-DSA-65 / Pulsar-M-65) and document the parameter choice in the spec.</p>
<p>The custom Plonky3-PQ fork lives at <code>~/work/lux/plonky3-pq</code> (planned location); audit gate is mandatory before mainnet activation.</p>
<h3>Cert envelope changes</h3>
<p>Q-Chain finality certs (HIP-0079) add three explicit fields when a proof is attached (epoch boundaries, Z-Chain anchor updates):</p>
<pre><code>proof_system_id ProofSystemID // 0x10 normative; cert is refused if 0x80 / 0x81
zchain_state_root [32]byte // anchors the latest accepted EpochCommitment
zchain_proof []byte // optional: Z-Chain proof bytes</code></pre>
<p><code>ProofSystemID</code> is bound into <code>Certificate.TranscriptHash()</code> per the HIP-0077 F1 fix pattern; a flipped byte breaks signature verification.</p>
<h3>Verifier API</h3>
<p>Strict-PQ verifier (Go reference):</p>
<pre><code class="lang-go">func VerifyZChainEpochProof(
ctx context.Context,
proof []byte,
publicIn ZChainPublicInputs,
suiteID config.HashSuiteID, // must == HashSuiteSHA3NIST (0x01)
proofSysID config.ProofSystemID, // must == ProofSystemSTARKFRISHA3PQ (0x10)
) error</code></pre>
<p>Constant-time guarantees: verifier MUST run in time independent of proof contents on accepted vs rejected proofs. Memory budget: ≤ 64 MB per verification on standard validator hardware.</p>
<h2>Security considerations</h2>
<ul><li><strong>No classical primitive in the trust path.</strong> Hash, commitment,</li></ul>
<p> Fiat-Shamir, recursion — all FIPS 202 / SP 800-185. The <code>0x80</code> and <code>0x81</code> ProofSystemIDs are explicit forbidden markers, not fallback.</p>
<ul><li><strong>STARK soundness reduces to hash-collision resistance.</strong> cSHAKE256</li></ul>
<p> is FIPS-approved; PQ-secure under classical and quantum models. Round-by-round soundness via the standard FRI analysis (Ben-Sasson, Bentov, Horesh, Riabzev — <em>&quot;Fast Reed–Solomon Interactive Oracle Proofs of Proximity,&quot;</em> ICALP 2018; refined by Bordage, Lecomte — <em>&quot;On the Soundness of the FRI Protocol&quot;</em> (proximity gaps), 2022).</p>
<ul><li><strong>Validator-set tampering.</strong> A malicious validator-set update must</li></ul>
<p> produce a valid Z-Chain proof; without it, Q-Chain refuses the EpochCommitment. Trust delegation: from Q-Chain consensus to Z-Chain proof-system soundness.</p>
<ul><li><strong>Recursion-overflow.</strong> Plonky3 recursion has constant proof size</li></ul>
<p> but prover budget grows with depth. Cap recursion depth at network-wide config; refuse certs above the cap.</p>
<ul><li><strong>DA assumption.</strong> Z-Chain state must be retrievable. v1 uses Lux</li></ul>
<p> DA layer (out of scope for this HIP). DA failure → validators cannot produce new Z-Chain proofs → Q-Chain stalls. This is the correct failure mode (chain halt, not validator compromise).</p>
<ul><li><strong>End-to-end security claim.</strong> The mainnet headline security</li></ul>
<p> level is bounded by <code>min(Pulsar-M parameter set, Z-Chain proof configuration)</code>. If Z-Chain proof is configured at 98-bit conjectured security, the chain MUST NOT advertise NIST PQ Cat 3 end-to-end. Configure to ≥ 128-bit classical / ≥ Cat 3 PQ to match Pulsar-M-65.</p>
<h2>Adoption order</h2>
<ol><li>Plonky3 fork with cSHAKE256 Merkle + Fiat-Shamir lands at</li></ol>
<p> <code>~/work/lux/plonky3-pq</code>.</p>
<ol><li>Reference Z-Chain prover implements obligations 1–9 against a</li></ol>
<p> mock validator set.</p>
<ol><li>KAT cross-validation: each validator-registration proof verifies</li></ol>
<p> an actual ML-DSA-65 sig under unmodified FIPS 204 ML-DSA.Verify.</p>
<ol><li>Verifier-totality fuzzing — every malformed proof returns an</li></ol>
<p> error, never panics.</p>
<ol><li>External cryptanalysis engagement (start 2026 Q3).</li><li>Q-Block envelope (HIP-0079) gains <code>proof_system_id</code>.</li><li>Phase 2 ships behind feature flag.</li><li>Phase 3 mandatory; flag day published.</li></ol>
<h2>References</h2>
<ul><li>FIPS 204 — <em>Module-Lattice-Based Digital Signature Standard</em>.</li><li>FIPS 202 — <em>SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions</em>.</li><li>NIST SP 800-185 — <em>cSHAKE / KMAC / TupleHash / ParallelHash</em>.</li><li>NIST IR 8214C — <em>First Call for Multi-Party Threshold Schemes</em>.</li><li>Plonky3 — https://github.com/Plonky3/Plonky3</li><li>Ben-Sasson, Bentov, Horesh, Riabzev — <em>&quot;Fast Reed–Solomon Interactive Oracle Proofs of Proximity,&quot;</em> ICALP 2018 — FRI soundness baseline.</li><li>Bordage, Lecomte — <em>&quot;On the Soundness of the FRI Protocol&quot;</em> (proximity gaps for FRI), 2022 — refined RBR soundness bound.</li><li>RISC Zero zkVM whitepaper.</li><li>HIP-0077 — Mesh Identity, Gossip &amp; Payments (parent).</li><li>HIP-0079 — Q-Chain Finality Blocks (consumer of Z-Chain roots).</li><li>HIP-0084 — Pulsar-M DKG (consumer of Z-Chain identity state).</li></ul>
<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="/hip-0078.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
</footer>
</div></body></html>