Sovereign naming. Systems-grade Rust. Infrastructure without gatekeepers.

handshake-rs is an independent, community-led, Rust-centered collection of libraries, services, and applications for the Handshake ecosystem. Each product has its own repository, version history, qualification gates, and release boundary. The ecosystem repository coordinates them; it is not a monorepo or an umbrella package.

hns-rs ─┬─ exact immutable pin ──> hns-node-rs ───────> MeshMine
        │                           runtime authority      mining application
        └─ exact immutable pin ──> hns-dane-engine
  canonical types/registry        DNSSEC/DANE, dual-root,
                                  transport policy, authority
                                  lifecycle, and observability
                                           ├──────────> hns-dane-browser-mobile
                                           └──────────> hns-dane-browser-extension
                                             platform lifecycle, UI,
                                             proxy, and packaging

hns-dane-crawler ── observed gap/handoff ──> hns-dane-bootstrap-generator
  topology and evidence                       operator-authored DNS records

ecosystem ── audits compatibility, integration, and release evidence for all

The authority direction is intentional. The browser-to-engine and MeshMine-to-node boundaries are implemented at the current audited checkpoints, and both hns-node-rs and hns-dane-engine consume exact immutable hns-rs revisions:

• protocol numbers, canonical encodings, and the experimental registry have one owner in hns-rs;
• in the generic node/runtime policy, opaque P2P relaying is default-on with an opt-out, HIP-76 requester eligibility defaults to Auto with its own opt-out, and every plaintext DNS/network output role remains a separate explicit opt-in. Durable persistence of those choices is still a platform/release gate;
• node runtime and chain authority belong in hns-node-rs;
• the node's current HIP-76 boundary transports strict correlated DNS messages but labels returned bytes untrusted—Brontide peer authentication does not replace local DNSSEC, TLSA, or DANE validation;
• MeshMine consumes a coherent external-node snapshot and never becomes consensus authority;
• TLSA-owner derivation, DANE via ICANN DoH, dual-root namespace selection, typed transport admission, the authority state graph, runtime session and generation/event admission, and schema-v2 security status stay below browser UI code in hns-dane-engine; its complete Cargo graph builds from a standalone checkout without an adjacent hns-rs tree;
• both browser products intentionally start their persisted requester switch false/off and require explicit user opt-in; false maps to Disabled, true maps to direct-first Auto, their P2P VERSION service mask remains zero, and every provider/output role remains disabled;
• each portable browser adapter binds one checked nonzero runtime session to the active proxy generation. Shared admission/publication tests reject stale requests, responses, and trusted status after policy change, degradation, revocation, or restart; the installed per-class matrix remains open;
• browser shells do not classify a hostname from an IANA suffix list. They resolve the complete hostname through HNS and ICANN, retain one complete connection/trust plan, and fail closed on bogus or indeterminate evidence;
• each product's portable whole-request Rust boundary requires and tests that shared decision for navigation, redirects, subresources, Service Workers, downloads, and WebSockets; and
• crawler reports can guide an operator into the bootstrap generator, but neither cached crawler data nor generated instructions can replace live browser DNSSEC/DANE validation.

Platform proxy/resolver implementation consolidation and installed-browser or signed-device qualification remain open; portable contract adoption is not a claim that those release gates have passed.

Canonical source and review policy live in handshake-rs. Release publishing and binary signing are separate responsibilities: Denuo Web LLC may continue to publish/sign the browser products, MeshMine, and auxiliary DANE services or appliances without owning every source repository or receiving organization-wide owner access. Signed artifacts must identify the exact canonical source commit or tag.

This ecosystem is under active construction and is not yet release-ready as a whole. Passing primitive or portable build tests does not imply full-node, wallet, marketplace, installed-browser, signed-device, mainnet, or production qualification. Current evidence and remaining blockers are tracked in the ecosystem qualification matrix and remaining gaps.

Some repositories do not yet have a finalized top-level license; public source availability alone does not grant additional rights. Start with the ecosystem integration state and each repository's own README and license terms.

This is an independent project and does not claim to be the official Handshake organization.

The canonical brand assets are maintained with this profile.