Files
skills/public/hip-0097.html
zeekayandHanzo Dev 9e10c1c10e Each llms index points at the other two
hanzoskills.com/llms.txt now opens with the install line, the API
reference index and the company index, so an agent that lands on any
one of the three can find the rest.

robots.txt claimed 537 documents while llms.txt counts 920. The number
is gone from robots.txt; llms.txt derives it.

public/ is regenerated from scripts/site.py, which it had fallen
behind: the copy-prompt menu and agent bar were in the generator and
not in the committed pages. tests/site.mjs passes against the result.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-11 00:27:59 -07:00

538 lines
46 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-0097</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-0097.md">
<link rel="icon" href="/favicon.svg">
<link rel="canonical" href="https://hanzoskills.com/hip-0097">
</head>
<!-- Reading this with a machine? Every page here is also plain markdown.
This one: https://hanzoskills.com/hip-0097.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-0097</h1><p class="lede">HIP-97: Node Identity and the did:hanzo: DID Method. Status Final. Hanzo architectural specification.</p><h1>HIP-0097: Node Identity and the did:hanzo: DID Method</h1>
<h2>Abstract</h2>
<p>Every Hanzo node, profile, agent, and device is currently named with the Shinkai-legacy <code>HanzoName</code> format: a <code>@@</code>-prefixed label with a network suffix baked into the string, e.g. <code>@@alice.sep-hanzo/main/agent/myChatGPTAgent</code>. That string is signed into every <code>HanzoMessage</code> and is the lookup key for on-chain identity registration (Base Sepolia, contract <code>0x425fb20ba3874e887336aaa7f3fab32d08135ba9</code>). It therefore is <strong>not</strong> a cosmetic label — it is consensus- and wire-critical.</p>
<p>This HIP proposes one clean replacement scheme: the <strong>canonical node identity is a <code>did:hanzo:&lt;name&gt;</code> Decentralized Identifier</strong> — the same W3C DID method this HIP specifies for every Hanzo subject. The legacy <code>@@…&lt;suffix&gt;</code> and the <code>network-in-the-string</code> design are retired. The network/chain is expressed as DID query parameters or resolved from the registry, never embedded in the human-readable name. A precise grammar and charset are defined, the signing and on-chain registration impact is specified, and a backward-compatible, three-phase migration and rollout is given so that no in-flight message or already-registered name breaks.</p>
<p>The same method serves every Hanzo subject — humans, agents, services and devices — so this HIP also specifies the DID Document a <code>did:hanzo:</code> identifier resolves to (§8), the resolution contract and lifecycle against the on-chain registry (§9), and the Verifiable Credential format that carries everything which is an attribute of a subject rather than its identity (§10).</p>
<h2>Motivation</h2>
<p>The <code>@@&lt;name&gt;.&lt;network&gt;-hanzo</code> format is inherited verbatim from Shinkai. It has four concrete problems, all of which touch code that is live today in <code>hanzo-libs/hanzo-messages/src/schemas/hanzo_name.rs</code>:</p>
<ol><li><strong>Network is welded into the identity string.</strong> The valid endings are hard-coded:</li></ol>
<p> <code>.hanzo</code>, <code>.sepolia-hanzo</code>, <code>.arb-sep-hanzo</code>, <code>.sep-hanzo</code> (<code>HanzoName::VALID_ENDINGS</code>). The <em>same node</em> on testnet vs. mainnet has a <em>different identity string</em>, a different signed sender, and a different registry key. Migrating a node from Base Sepolia to the Hanzo L1 mainnet (HIP-24, chain <code>36963</code>) today means it is literally a different identity. This is the single worst property of the legacy scheme.</p>
<ol><li><strong><code>@@</code> is non-standard and non-interoperable.</strong> It is not a URI, not a DID, not a</li></ol>
<p> DNS name. Nothing outside Hanzo can resolve it. Meanwhile <code>did:hanzo:</code> is the W3C-compliant identity method for every other Hanzo subject — humans, agents, services and devices — with a W3C resolver and an on-chain registry (<code>IHanzoDIDRegistry</code>). Node identity and DID identity are needlessly two different namespaces.</p>
<ol><li><strong>The format is already half-migrated, inconsistently.</strong> <code>HanzoName</code> <em>already</em></li></ol>
<p> accepts <code>did:hanzo:&lt;network&gt;</code> and <code>did:lux:&lt;network&gt;</code> (see <code>is_did_format</code>, <code>validate_did_name</code>), but only as a network selector (<code>did:hanzo:mainnet</code>, <code>did:hanzo:sepolia</code>, <code>did:hanzo:local:node1</code>) — the <em>node&#x27;s own name</em> still has no home in that form, and a separate <code>hanzo-libs/hanzo-did</code> crate parses general W3C DIDs with yet another grammar. Three parsers, one concept.</p>
<ol><li><strong>Charset and case rules are loose.</strong> The legacy regex</li></ol>
<p> <code>^@@[a-zA-Z0-9\_\.]+(\.hanzo|…)$</code> permits embedded dots in the node label (<code>@@a.b.c.hanzo</code>), mixes case then lowercases at construction, and silently auto-corrects (<code>correct_node_name</code> prepends <code>@@</code> and appends <code>.hanzo</code>). Loose, auto-correcting identity parsing is a security smell for something that is signed.</p>
<h2>Specification</h2>
<h3>1. Decision: <code>did:hanzo:&lt;name&gt;</code>, not <code>&lt;name&gt;.hanzo</code></h3>
<p>Two candidate clean schemes were considered:</p>
<ul><li><strong>A. ENS-like <code>&lt;name&gt;.hanzo</code></strong> — e.g. <code>alice.hanzo</code>, <code>alice.hanzo/main/agent/x</code>.</li><li><strong>B. DID-style <code>did:hanzo:&lt;name&gt;</code></strong> — e.g. <code>did:hanzo:alice</code>,</li></ul>
<p> <code>did:hanzo:alice/main/agent/x</code>.</p>
<p><strong>This HIP selects B, <code>did:hanzo:&lt;name&gt;.</code></strong> Rationale:</p>
<p>| Criterion | <code>&lt;name&gt;.hanzo</code> (A) | <code>did:hanzo:&lt;name&gt;</code> (B) — chosen | |---|---|---| | Aligns with existing standard | No — new third namespace | <strong>Yes — the <code>did:hanzo:</code> method itself</strong> | | Already parseable by <code>HanzoName</code> | No | <strong>Partly — <code>did:hanzo:</code> path exists today</strong> | | Network kept out of the name | Yes | <strong>Yes</strong> (query param / registry, never the label) | | Globally resolvable / W3C interop | No (looks like a DNS host but isn&#x27;t) | <strong>Yes — resolves at <code>did.hanzo.ai</code>, <code>did:</code> URI scheme</strong> | | Collides with real DNS / TLD confusion | Yes (<code>.hanzo</code> reads as a gTLD) | No | | One identity across testnet/mainnet | Yes | <strong>Yes</strong> | | Verifiable Credentials, <code>alsoKnownAs</code> cross-chain (<code>did:lux:</code>, <code>did:ai:</code>) | No native hook | <strong>Native (§8, §10)</strong> |</p>
<p><code>A</code> reads more cleanly to a human, but it manufactures a <em>third</em> identity grammar (after <code>@@…</code> and <code>did:…</code>) and looks deceptively like a DNS hostname while resolving through none of DNS. <code>B</code> collapses node identity into the DID method the ecosystem already standardized, makes node identity a first-class W3C DID, and gets cross-chain <code>alsoKnownAs</code>, Verifiable Credentials, and the <code>did.hanzo.ai</code> resolver for free. The human-friendly display form is recovered cheaply (see §6, UX) by rendering <code>did:hanzo:alice</code> as <code>alice</code> / <code>@alice</code> in UIs without changing the wire identity.</p>
<blockquote><p>Note on <code>did:hanzo:mainnet</code> legacy usage: the existing code uses <code>did:hanzo:&lt;network&gt;</code> where the method-specific-id is a <em>network</em>. Under this HIP the method-specific-id is the <strong>node name</strong>, and the network moves to a query parameter (<code>?chain=</code>/<code>?network=</code>). <code>did:hanzo:mainnet</code> is reinterpreted during migration as the reserved node name <code>mainnet</code> on the default chain; deployments that used it purely as a network selector MUST migrate to <code>did:hanzo:&lt;node&gt;?network=mainnet</code> (see Migration §M0).</p></blockquote>
<h3>2. Canonical grammar (ABNF)</h3>
<p>The canonical, signed, on-chain identity is the <strong><code>hanzo-id</code></strong> production:</p>
<pre><code class="lang-abnf">hanzo-id = did-node [ &quot;/&quot; profile [ &quot;/&quot; sub-type &quot;/&quot; sub-name ] ]
did-node = &quot;did:hanzo:&quot; name [ params ]
name = label *( &quot;_&quot; label ) ; node name, the method-specific-id
label = lletter *( letterdigit ) ; MUST start with a letter
profile = label *( &quot;_&quot; label )
sub-type = &quot;agent&quot; / &quot;device&quot;
sub-name = label *( &quot;_&quot; label )
params = &quot;?&quot; param *( &quot;&amp;&quot; param ) ; OPTIONAL; carried, never signed (§3)
param = pkey &quot;=&quot; pval
pkey = &quot;network&quot; / &quot;chain&quot; / &quot;versionId&quot; / &quot;versionTime&quot;
pval = 1*( unreserved )
letterdigit = lowletter / digit
lowletter = %x61-7A ; a-z (lowercase ONLY)
letter = lowletter
digit = %x30-39 ; 0-9
unreserved = lowletter / digit / &quot;-&quot; / &quot;.&quot; / &quot;:&quot;</code></pre>
<p>Equivalently, the node-name regex (replacing the legacy <code>^@@[a-zA-Z0-9\_\.]+(\.hanzo|…)$</code>):</p>
<pre><code>^did:hanzo:[a-z][a-z0-9]*(_[a-z0-9]+)*(\?[a-z]+=[a-z0-9.:-]+(&amp;[a-z]+=[a-z0-9.:-]+)*)?$</code></pre>
<h4>Charset and length rules (normative)</h4>
<ul><li><strong>Lowercase only.</strong> The method-specific name and every path segment MUST match</li></ul>
<p> <code>[a-z][a-z0-9_]<em></code>. No uppercase, no auto-lowercasing at parse time — a mixed-case input is <strong>rejected</strong>, not silently corrected. (The legacy lower-casing in <code>HanzoName::new</code> is removed; canonicalization is now the </em>caller&#x27;s* job before signing.)</p>
<ul><li><strong>No dots in names.</strong> Unlike legacy <code>@@a.b.hanzo</code>, the node name MUST NOT contain</li></ul>
<p> <code>.</code>. Dots appear only inside <code>params</code> values (e.g. a chain RPC alias).</p>
<ul><li><strong>Separator is <code>_</code> inside a segment, <code>/</code> between segments.</strong> Matches the existing</li></ul>
<p> 4-part structure (node / profile / <code>agent|device</code> / name) so downstream parsing in <code>inbox_name.rs</code>, <code>tool_router_key.rs</code>, etc. keeps the same <code>split(&#x27;/&#x27;)</code> shape.</p>
<ul><li><strong>Length:</strong> <code>name</code> and each path segment 1–63 bytes; total <code>hanzo-id</code> ≤ 255 bytes</li></ul>
<p> (DNS-label-compatible bound, keeps registry keys bounded).</p>
<ul><li><strong>Reserved names:</strong> <code>localhost</code>, <code>mainnet</code>, <code>testnet</code>, <code>sepolia</code>, <code>local</code>, <code>node</code>,</li></ul>
<p> <code>agent</code>, <code>device</code>, <code>did</code> MUST NOT be used as a <em>node</em> <code>name</code> except for the reserved-mapping defined in Migration §M0. The default local dev identity becomes <code>did:hanzo:localhost?network=local</code> (replacing <code>@@localhost.sep-hanzo</code>).</p>
<h4>Valid examples</h4>
<pre><code>did:hanzo:alice
did:hanzo:alice/main
did:hanzo:alice/main/agent/my_chatgpt_agent
did:hanzo:alice/main/device/my_phone
did:hanzo:alice?network=mainnet
did:hanzo:alice?chain=36963
did:hanzo:node1?network=sepolia ; Base Sepolia during migration
did:hanzo:localhost?network=local</code></pre>
<h4>Invalid examples (and why)</h4>
<pre><code>@@alice.sep-hanzo ; legacy @@ form — rejected post-migration (accepted read-only in Phase 1)
did:hanzo:Alice ; uppercase
did:hanzo:al!ce ; illegal char
did:hanzo:a.b.c ; dot in node name
did:hanzo:_alice ; must start with a letter
did:hanzo:alice/main/myPhone ; 3-part must be …/agent/… or …/device/…
did:hanzo:alice/main/agent ; agent/device requires a 4th sub-name part
did:hanzo:alice.hanzo ; no network/TLD suffix in the name</code></pre>
<h3>3. Network is a parameter, never part of the identity</h3>
<p>The single most important rule: <strong>the chain/network is NOT part of the signed, on-chain identity.</strong> <code>did:hanzo:alice</code> is the <em>same node</em> whether it is registered on Base Sepolia (migration), the Hanzo L1 mainnet (chain <code>36963</code>, HIP-24), or running locally.</p>
<ul><li>The optional <code>params</code> (<code>?network=…</code>, <code>?chain=…</code>) are a <strong>resolution hint only</strong>.</li><li>When computing the value that is <strong>signed</strong> (sender/recipient in</li></ul>
<p> <code>external_metadata</code>) and the value used as the <strong>registry key</strong>, the params are <strong>stripped</strong>. The canonical signed form is the bare <code>did:hanzo:&lt;name&gt;[/path]</code> with no query string.</p>
<ul><li>This directly fixes Motivation #1: a node moving from testnet to mainnet keeps the</li></ul>
<p> same identity, the same signed sender, and the same registry key.</p>
<h3>4. Signing impact</h3>
<p>In <code>hanzo_message_signing.rs</code>, the name is not hashed field-by-field; rather <code>external_metadata.sender</code> / <code>external_metadata.recipient</code> (full <code>HanzoName</code> strings) are part of the message whose hash is signed with ed25519 (<code>sign_outer_layer</code> / <code>sign_inner_layer</code>). Therefore <strong>the exact bytes of the identity string are inside the signature preimage.</strong> Consequences:</p>
<ol><li>Changing a node&#x27;s canonical string from <code>@@alice.sep-hanzo</code> to <code>did:hanzo:alice</code></li></ol>
<p> changes the signed bytes. A verifier expecting one form will fail signatures produced under the other. This is why a flag-day rename is unacceptable and why §7 defines an <code>IdentityProtocolVersion</code> negotiation.</p>
<ol><li>The <strong>canonicalization rule for the preimage is fixed by this HIP</strong>: the signed</li></ol>
<p> sender/recipient MUST be the <strong>params-stripped, NFC, lowercase <code>did:hanzo:</code> form</strong> (§3). Because §2 forbids uppercase and auto-correction, canonicalization is now deterministic and side-effect-free — there is exactly one byte sequence per identity, removing the legacy ambiguity where <code>@@Alice…</code> and <code>@@alice…</code> could both be constructed and then lower-cased.</p>
<ol><li><strong>PQ readiness.</strong> Outer/inner signatures stay ed25519 for wire compatibility in</li></ol>
<p> this HIP. The <code>did:hanzo:&lt;name&gt;</code> DID Document MAY additionally carry an <code>MLDSAVerificationKey2025</code> key (HIP-5, §8) so the <em>same node identity</em> can be verified post-quantum without another rename. PQ message signing is deferred to a follow-up but is unblocked by using the DID form now.</p>
<h3>5. On-chain registration impact</h3>
<p>Registration today goes through <code>hanzo-bin/hanzo-node/src/managers/identity_network_manager.rs</code>:</p>
<ul><li>RPC <code>https://sepolia.base.org</code>, contract</li></ul>
<p> <code>0x425fb20ba3874e887336aaa7f3fab32d08135ba9</code>, via <code>HanzoRegistry::get_identity_record(identity)</code>.</p>
<ul><li>Resolution special-cases the suffix: it checks</li></ul>
<p> <code>node_base.ends_with(&quot;.sepolia-hanzo&quot;)</code> to decide proxy handling.</p>
<p>Changes required:</p>
<ol><li><strong>Registry key becomes the canonical params-stripped <code>did:hanzo:&lt;name&gt;</code>.</strong> The</li></ol>
<p> existing Base Sepolia registry contract is retained during Phase 1–2 (no contract redeploy needed to <em>start</em>), but the <em>key string</em> it stores transitions from <code>@@alice.sepolia-hanzo</code> to <code>did:hanzo:alice</code>. A node registers its DID form; the suffix-sniffing (<code>.sepolia-hanzo</code>) branch is replaced by reading the <code>?network=</code>/<code>?chain=</code> hint (default <code>sepolia</code> during migration, <code>36963</code> after).</p>
<ol><li><strong>Converge onto <code>IHanzoDIDRegistry</code>.</strong> The end-state registry is the</li></ol>
<p> <code>did:hanzo:</code> registry on Hanzo L1 (chain <code>36963</code>), which stores <code>documentHash</code>, <code>controller</code>, <code>version</code>, <code>active</code> per DID (§9). Node registration and DID registration become the <strong>same on-chain record</strong>: a node <em>is</em> a DID. This removes the separate Base Sepolia identity contract entirely at end-of-life (Phase 3).</p>
<ol><li><strong>Dual-read during migration.</strong> The resolver MUST, given a query, attempt</li></ol>
<p> resolution of both the new <code>did:hanzo:&lt;name&gt;</code> key and the legacy <code>@@&lt;name&gt;.&lt;suffix&gt;</code> key (deterministic mapping, §M1) so that a node which has re-registered under the DID form is still reachable by peers that only know its legacy name, and vice-versa.</p>
<h3>6. UX / display form</h3>
<p>To preserve readability lost by dropping the short <code>@@alice</code> look:</p>
<ul><li>UIs render <code>did:hanzo:alice</code> as <strong><code>alice</code></strong> (or <code>@alice</code> in social contexts);</li></ul>
<p> <code>did:hanzo:alice/main/agent/researcher</code> renders as <strong><code>alice › researcher</code></strong>.</p>
<ul><li><code>alsoKnownAs</code> in the DID Document MAY list <code>did:lux:alice</code>, <code>did:ai:alice</code></li></ul>
<p> (§8 cross-chain links). These are display/interop aliases, never the signed identity.</p>
<ul><li>A node MAY publish a human label and avatar in its DID Document <code>service</code> /</li></ul>
<p> profile credential (the <code>HanzoAgentCredential</code> of §10), so the short name is a resolvable attribute, not part of the cryptographic identity.</p>
<h3>7. <code>HanzoName</code> type changes (normative, Rust)</h3>
<p>In <code>hanzo-libs/hanzo-messages/src/schemas/hanzo_name.rs</code>:</p>
<ul><li>Add <code>pub network_hint: Option&lt;String&gt;</code> and <code>pub chain_id_hint: Option&lt;u64&gt;</code> to</li></ul>
<p> <code>HanzoName</code>, populated from <code>params</code> and <strong>excluded</strong> from <code>Display</code>, <code>Hash</code>, <code>PartialEq</code>, <code>Serialize</code>, and from the signing preimage (they are resolution-only).</p>
<ul><li><code>node_name</code> now holds the canonical <code>did:hanzo:&lt;name&gt;</code> (params stripped). The</li></ul>
<p> fields <code>profile_name</code>, <code>subidentity_type</code>, <code>subidentity_name</code> are unchanged.</p>
<ul><li><code>validate_name</code> gains a <code>did:hanzo:&lt;name&gt;</code> branch (the §2 regex) and **stops</li></ul>
<p> auto-correcting**: <code>correct_node_name</code>&#x27;s <code>@@</code>/<code>.hanzo</code> injection is gated behind a legacy-compat flag and is off by default in Phase 2+.</p>
<ul><li>Add <code>IdentityProtocolVersion { Legacy = 1, Did = 2 }</code> carried in the message</li></ul>
<p> envelope / handshake. A peer advertises which forms it can <em>verify</em>. Two <code>Did</code> peers sign/verify the DID form; if either side is <code>Legacy</code>-only, both fall back to the legacy string for that exchange (so signatures still match) until Phase 3.</p>
<ul><li><code>default_testnet_localhost()</code> returns</li></ul>
<p> <code>HanzoName::new(&quot;did:hanzo:localhost/main?network=local&quot;)</code>.</p>
<ul><li>Equality across forms: provide <code>HanzoName::same_identity(a, b)</code> that compares the</li></ul>
<p> canonical DID form after applying the §M1 legacy→DID mapping, so routing/dedup treat a legacy name and its migrated DID as one identity.</p>
<h3>8. DID Document</h3>
<p>A <code>did:hanzo:&lt;name&gt;</code> resolves to a document conforming to W3C DID Core 1.0. The identity is the identifier; the document is the key material and the endpoints it currently points at, and it MAY be rotated without the identity changing.</p>
<pre><code class="lang-json">{
&quot;@context&quot;: [
&quot;https://www.w3.org/ns/did/v1&quot;,
&quot;https://w3id.org/security/suites/jws-2020/v1&quot;,
&quot;https://hanzo.ai/ns/did/v1&quot;
],
&quot;id&quot;: &quot;did:hanzo:dev&quot;,
&quot;controller&quot;: &quot;did:hanzo:hanzo&quot;,
&quot;alsoKnownAs&quot;: [
&quot;did:lux:dev&quot;,
&quot;did:ai:dev&quot;
],
&quot;verificationMethod&quot;: [
{
&quot;id&quot;: &quot;did:hanzo:dev#key-1&quot;,
&quot;type&quot;: &quot;EcdsaSecp256k1VerificationKey2019&quot;,
&quot;controller&quot;: &quot;did:hanzo:dev&quot;,
&quot;blockchainAccountId&quot;: &quot;eip155:36963:0xAgentAddress&quot;
},
{
&quot;id&quot;: &quot;did:hanzo:dev#key-2&quot;,
&quot;type&quot;: &quot;JsonWebKey2020&quot;,
&quot;controller&quot;: &quot;did:hanzo:dev&quot;,
&quot;publicKeyJwk&quot;: {
&quot;kty&quot;: &quot;OKP&quot;,
&quot;crv&quot;: &quot;Ed25519&quot;,
&quot;x&quot;: &quot;base64url-encoded-public-key&quot;
}
},
{
&quot;id&quot;: &quot;did:hanzo:dev#key-pq&quot;,
&quot;type&quot;: &quot;MLDSAVerificationKey2025&quot;,
&quot;controller&quot;: &quot;did:hanzo:dev&quot;,
&quot;publicKeyMultibase&quot;: &quot;z6Mk...&quot;
}
],
&quot;authentication&quot;: [
&quot;did:hanzo:dev#key-1&quot;,
&quot;did:hanzo:dev#key-2&quot;
],
&quot;assertionMethod&quot;: [
&quot;did:hanzo:dev#key-1&quot;
],
&quot;keyAgreement&quot;: [
{
&quot;id&quot;: &quot;did:hanzo:dev#key-agree-1&quot;,
&quot;type&quot;: &quot;X25519KeyAgreementKey2020&quot;,
&quot;controller&quot;: &quot;did:hanzo:dev&quot;,
&quot;publicKeyMultibase&quot;: &quot;z6LS...&quot;
}
],
&quot;capabilityInvocation&quot;: [
&quot;did:hanzo:dev#key-1&quot;
],
&quot;capabilityDelegation&quot;: [
&quot;did:hanzo:dev#key-1&quot;
],
&quot;service&quot;: [
{
&quot;id&quot;: &quot;did:hanzo:dev#rpc&quot;,
&quot;type&quot;: &quot;AgentRPCService&quot;,
&quot;serviceEndpoint&quot;: &quot;https://bot.hanzo.ai/rpc/dev&quot;
},
{
&quot;id&quot;: &quot;did:hanzo:dev#wallet&quot;,
&quot;type&quot;: &quot;SafeWallet&quot;,
&quot;serviceEndpoint&quot;: &quot;safe:eip155:36963:0xSafeAddress&quot;
},
{
&quot;id&quot;: &quot;did:hanzo:dev#iam&quot;,
&quot;type&quot;: &quot;OIDCProvider&quot;,
&quot;serviceEndpoint&quot;: &quot;https://hanzo.id&quot;
}
]
}</code></pre>
<p>The <code>#key-2</code> ed25519 method is the node&#x27;s message-signing key from §4, and <code>#key-pq</code> is the <code>MLDSAVerificationKey2025</code> that makes the same identity verifiable post-quantum without a second rename.</p>
<p>Each verification relationship answers a different question, and a verifier MUST check the one that matches what it is about to allow:</p>
<p>| Relationship | Purpose | Example | |-------------|---------|---------| | <code>authentication</code> | Prove you are the DID subject | Node login to another node&#x27;s API | | <code>assertionMethod</code> | Sign Verifiable Credentials | Agent attesting it completed a task | | <code>keyAgreement</code> | Establish encrypted channels | Node-to-node encrypted messaging | | <code>capabilityInvocation</code> | Invoke capabilities on resources | Agent executing a delegated action | | <code>capabilityDelegation</code> | Delegate capabilities to others | Organization granting agent authority |</p>
<p>A single key MAY appear in several relationships. Separate keys for <code>authentication</code> and <code>keyAgreement</code> are RECOMMENDED, so compromising one does not hand over the other.</p>
<h3>9. Resolution</h3>
<p>The registry record of §5 is authoritative: <code>documentHash</code>, <code>controller</code>, <code>version</code>, <code>active</code>, keyed by the params-stripped <code>did:hanzo:&lt;name&gt;</code>. The document itself lives off-chain, so a resolver MUST recompute <code>SHA-256(document)</code> and compare it against the registry <code>documentHash</code> before returning it. A document that does not match its on-chain hash MUST NOT be returned.</p>
<p>Resolution follows the W3C DID Resolution specification, and the <code>versionId</code> and <code>versionTime</code> params of §2 are its query parameters:</p>
<p>| Method | Endpoint | Description | |--------|----------|-------------| | GET | <code>/1.0/identifiers/{did}</code> | Resolve to the current document | | GET | <code>/1.0/identifiers/{did}?versionId={n}</code> | Resolve a specific version | | GET | <code>/1.0/identifiers/{did}?versionTime={iso8601}</code> | Resolve as of a point in time | | POST | <code>/1.0/create</code> | Register a DID | | POST | <code>/1.0/update</code> | Publish a new document version | | POST | <code>/1.0/deactivate</code> | Deactivate a DID |</p>
<p>The response carries the document plus resolution metadata: content type, created and updated timestamps, version, and the deactivated flag. Like every other resolution hint, these params are stripped from the signed and registry-key forms (§3).</p>
<p>The lifecycle is four operations:</p>
<ul><li><strong>Create.</strong> The subject generates its keypair locally or in KMS (HIP-27),</li></ul>
<p> constructs the document, computes <code>documentHash</code>, calls <code>IHanzoDIDRegistry.register(did, documentHash)</code>, and publishes the document.</p>
<ul><li><strong>Resolve.</strong> The verifier fetches the document, checks it against the registry</li></ul>
<p> hash, and takes the verification method for the relationship it needs.</p>
<ul><li><strong>Update.</strong> The controller publishes a new document, computes the new hash, and</li></ul>
<p> calls <code>update(did, newDocumentHash)</code>. The version counter increments and prior versions stay in chain history, which is what makes <code>versionId</code> and <code>versionTime</code> answerable. Only the controller may update; control moves only via <code>changeController()</code>.</p>
<ul><li><strong>Deactivate.</strong> The controller calls <code>deactivate(did)</code>; resolution then returns</li></ul>
<p> <code>deactivated=true</code>. Credentials issued before deactivation remain historically verifiable, but a verifier MUST NOT accept a credential issued after it.</p>
<p>Deactivation is irreversible. A reactivated DID would leave verifiers unable to tell which validity window a credential belongs to; a subject that needs an identity after deactivation creates a new one.</p>
<h3>10. Verifiable Credentials</h3>
<p>Attributes that are not identity — capabilities, org membership, evaluation results — are Verifiable Credentials about the DID rather than fields inside it. IAM (HIP-26) is the issuer for identity and membership claims:</p>
<pre><code class="lang-json">{
&quot;@context&quot;: [
&quot;https://www.w3.org/ns/credentials/v2&quot;,
&quot;https://hanzo.ai/ns/credentials/v1&quot;
],
&quot;type&quot;: [&quot;VerifiableCredential&quot;, &quot;HanzoAgentCredential&quot;],
&quot;issuer&quot;: &quot;did:hanzo:iam&quot;,
&quot;issuanceDate&quot;: &quot;2026-02-23T00:00:00Z&quot;,
&quot;expirationDate&quot;: &quot;2027-02-23T00:00:00Z&quot;,
&quot;credentialSubject&quot;: {
&quot;id&quot;: &quot;did:hanzo:dev&quot;,
&quot;type&quot;: &quot;AIAgent&quot;,
&quot;name&quot;: &quot;dev&quot;,
&quot;organization&quot;: &quot;hanzo&quot;,
&quot;capabilities&quot;: [
&quot;code-generation&quot;,
&quot;code-review&quot;,
&quot;mcp-tool-use&quot;
],
&quot;safetyEvaluation&quot;: {
&quot;framework&quot;: &quot;HIP-0210&quot;,
&quot;result&quot;: &quot;pass&quot;,
&quot;evaluatedAt&quot;: &quot;2026-02-20T12:00:00Z&quot;
},
&quot;computeTier&quot;: &quot;tier-3&quot;,
&quot;maxTokenBudget&quot;: 1000000
},
&quot;credentialStatus&quot;: {
&quot;id&quot;: &quot;https://did.hanzo.ai/credentials/status/1&quot;,
&quot;type&quot;: &quot;StatusList2021Entry&quot;,
&quot;statusPurpose&quot;: &quot;revocation&quot;,
&quot;statusListIndex&quot;: &quot;42&quot;,
&quot;statusListCredential&quot;: &quot;https://did.hanzo.ai/credentials/status-list/1&quot;
},
&quot;proof&quot;: {
&quot;type&quot;: &quot;EcdsaSecp256k1Signature2019&quot;,
&quot;created&quot;: &quot;2026-02-23T00:00:00Z&quot;,
&quot;verificationMethod&quot;: &quot;did:hanzo:iam#key-1&quot;,
&quot;proofPurpose&quot;: &quot;assertionMethod&quot;,
&quot;proofValue&quot;: &quot;z58DAdFfa9SkqZMVPxAQpic7ndTn...&quot;
}
}</code></pre>
<p>The <code>proof.verificationMethod</code> MUST appear in the issuer&#x27;s <code>assertionMethod</code> set; a credential signed by a key the issuer never listed for assertion is invalid however well-formed it looks.</p>
<p>| Credential Type | Issuer | Subject | Purpose | |----------------|--------|---------|---------| | <code>HanzoAgentCredential</code> | IAM | Agent DID | Attest agent identity and capabilities | | <code>SafetyEvaluationCredential</code> | Safety framework (HIP-210) | Agent DID | Attest safety evaluation results | | <code>OrganizationMembershipCredential</code> | IAM | User or agent DID | Attest org membership and role | | <code>ComputeAuthorizationCredential</code> | Cloud (HIP-106) | Agent DID | Authorize compute resource access | | <code>ModelTrainingCredential</code> | Training pipeline | Model DID | Attest training data provenance | | <code>BiasAuditCredential</code> | Bias framework (HIP-220) | Model DID | Attest bias evaluation results |</p>
<p>Revocation is StatusList2021: a bitstring where flipping bit <em>n</em> revokes the credential holding <code>statusListIndex</code> <em>n</em>. A verifier downloads the whole list rather than asking about one credential, so checking revocation does not tell the issuer which credential is being verified.</p>
<h2>Backward Compatibility &amp; Migration</h2>
<p>This is a signed, on-chain identifier; the migration is explicitly versioned and phased. No flag day.</p>
<h3>M0 — Reserved-name and network-param remap (pre-flight)</h3>
<p>Existing <code>did:hanzo:&lt;network&gt;</code> selectors (<code>did:hanzo:mainnet</code>, <code>did:hanzo:sepolia</code>, <code>did:hanzo:local:node1</code>) are reinterpreted:</p>
<ul><li><code>did:hanzo:mainnet</code> → reserved; if it was a <em>network</em> selector it becomes</li></ul>
<p> <code>did:hanzo:&lt;node&gt;?network=mainnet</code>. Operators MUST update config to name the node.</p>
<ul><li><code>did:hanzo:local:node1</code> → <code>did:hanzo:node1?network=local</code>.</li></ul>
<h3>M1 — Deterministic legacy ↔ DID mapping (the bridge)</h3>
<p>A pure function maps any legacy name to its canonical DID form and back:</p>
<pre><code>legacy: @@&lt;name&gt;.&lt;suffix&gt;[/&lt;profile&gt;[/&lt;type&gt;/&lt;sub&gt;]]
canon: did:hanzo:&lt;name&gt;[/&lt;profile&gt;[/&lt;type&gt;/&lt;sub&gt;]] with params: network=&lt;from suffix&gt;
suffix → network/chain:
.hanzo → mainnet (chain 36963)
.sep-hanzo → sepolia (Base Sepolia) ; current default
.sepolia-hanzo → sepolia (Base Sepolia)
.arb-sep-hanzo → arb-sepolia</code></pre>
<p><code>&lt;name&gt;</code> is copied verbatim <strong>iff</strong> it already satisfies §2 (lowercase, no dots). Legacy names containing dots or uppercase are flagged for operator-assisted rename (they are rare; the dominant case <code>@@alice.sep-hanzo</code> maps cleanly to <code>did:hanzo:alice?network=sepolia</code>). This mapping is the basis for dual-read (§5.3) and <code>same_identity</code> (§7).</p>
<h3>Migration tooling</h3>
<ul><li><code>hanzod identity migrate</code> — reads the node&#x27;s current <code>@@…</code> identity, derives</li></ul>
<p> the <code>did:hanzo:</code> form via §M1 and re-registers it on-chain. It writes one key.</p>
<ul><li>Test vectors (canonical DID, signed preimage bytes) live in</li></ul>
<p> <code>hanzo-libs/hanzo-messages/tests/hanzo_name_tests.rs</code>.</p>
<h2>Rollout</h2>
<ol><li>Land <code>HanzoName</code> changes (DID branch, hints, <code>same_identity</code>,</li></ol>
<p> <code>IdentityProtocolVersion</code>) behind a feature flag; ship in a normal node release (Phase 1 behavior default).</p>
<ol><li>Update the ~60 call sites that build/validate <code>HanzoName</code> (identity manager,</li></ol>
<p> inbox/tool-router keys, payments managers, tests) to use canonicalized DID construction helpers; behavior stays Legacy-signed.</p>
<ol><li>Ship resolver dual-read + <code>hanzod identity migrate</code> + <code>did.hanzo.ai</code> lookup</li></ol>
<p> table.</p>
<ol><li>Flip default to Phase 2 once telemetry shows quorum of capable peers.</li><li>Announce Phase 3 cutover height/date; freeze Base Sepolia contract; converge on</li></ol>
<p> <code>IHanzoDIDRegistry</code> (chain <code>36963</code>).</p>
<h2>Security Considerations</h2>
<ul><li><strong>Signature-preimage determinism.</strong> Because §2 forbids uppercase/dots and removes</li></ul>
<p> auto-correction, each identity has exactly one canonical byte sequence; this closes the legacy ambiguity where multiple inputs canonicalized to the same lower-cased name, which is dangerous for a signed field.</p>
<ul><li><strong>No silent identity coercion.</strong> Invalid identities are rejected, never</li></ul>
<p> auto-completed into a valid-looking one (legacy <code>correct_node_name</code> could turn a typo into a different, valid node).</p>
<ul><li><strong>Network-confusion resistance.</strong> Stripping <code>?network</code>/<code>?chain</code> from the signed and</li></ul>
<p> registry forms means a signature or registration cannot be replayed as if it were for a different chain by swapping a suffix — the identity is chain-agnostic by construction.</p>
<ul><li><strong>Migration window risk.</strong> Dual-read and <code>Legacy</code> fallback are the only periods</li></ul>
<p> where two strings denote one node; <code>same_identity</code> (§M1 mapping) MUST be used for all auth/routing decisions to prevent a peer from being treated as two identities (or two peers as one).</p>
<ul><li><strong>PQ path.</strong> The DID form lets a node attach an <code>MLDSAVerificationKey2025</code> key</li></ul>
<p> (HIP-5) to the same identity, so the eventual move to PQ message signing needs no further rename.</p>
<h2>References</h2>
<ul><li>HIP-5 — Post-Quantum Security (<code>ML-DSA-65</code>, <code>MLDSAVerificationKey2025</code>)</li><li>HIP-24 — Hanzo Sovereign L1 (chain <code>36963</code>)</li><li>HIP-26 — IAM (credential issuer); HIP-27 — KMS (key custody)</li><li>W3C DID Core 1.0; W3C Verifiable Credentials Data Model 2.0</li><li><code>hanzo-libs/hanzo-messages/src/schemas/hanzo_name.rs</code> (current <code>HanzoName</code>)</li><li><code>hanzo-bin/hanzo-node/src/managers/identity_network_manager.rs</code> (Base Sepolia registration)</li><li><code>hanzo-libs/hanzo-did/</code> (existing W3C DID parser to converge on)</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-0097.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
</footer>
</div></body></html>