ICSN Technical Standards

Standards & Protocols for Sovereign Digital Infrastructure

Open technical standards, protocols, and specifications enabling sovereign control, human-first design, and global interoperability across 170+ nations through net3.eth coordination.

Sovereign Human Rights Digital Charter

The constitutional root for Internet 3.0 — establishing the human as the first sovereign

Charter Principles

This Charter establishes that identity is human-anchored, title is lawful and traceable, surveillance is not the price of inclusion, and coercion by code is prohibited.

Human Primacy

The human is the root of all authority. Identity, consent, and control cannot be delegated without explicit authorization.

Human-in-the-Loop Authority

Critical operations require human authorization. Automated systems must preserve human decision-making power.

Jurisdictional Respect

Legal authority is determined by jurisdiction. Systems must honor sovereign boundaries and local law.

No Deletion — Only Lineage

History cannot be erased. All changes are recorded in immutable lineage, preserving provenance and accountability.

Quantum-Anchored Custody

Cryptographic custody designed to survive quantum computing threats using post-quantum cryptography.

Enforcement by Invalidation

Violations result in credential invalidation, not censorship. Bad actors lose standing, not voice.

Read the Full Charter Request Institutional Adoption Pack

CYRUS© Binding Protocol

Rights inscribed into cryptography to outlive platforms — inspired by the Cyrus Cylinder's enduring record of human rights

What CYRUS© Means

CYRUS© references the Cyrus Cylinder — the ancient declaration of human rights recorded to outlive empires.

CYRUS© Binding inscribes rights into cryptography so they outlive platforms, creating durable records independent of any single provider or government.

What a CYRUS© Binding Event Establishes

  • Human-first origination and explicit consent
  • Non-repudiation and full auditability
  • Chain-of-custody and delegation lineage
  • Jurisdictional standing for lawful enforcement
  • Platform independence — survives provider failure

Notary & Witnessing Requirements

CYRUS© Binding requires rigorous attestation to ensure durability and authenticity:

✓ Credentialed Human Execution

Human authorization required for all binding events

✓ Decentralized Witnessing

Multiple independent witnesses validate events

✓ Hybrid Cryptography

Classical + post-quantum algorithms for future-proofing

✓ Public Notary Anchoring

Bitcoin integrity proofs for immutable timestamping

Registry persistence serves as the canonical record, ensuring continuity even if individual nodes fail.

Web2 Continuity

CYRUS© Binding supports continuity from Web2 trust anchors (DNS/DNSSEC where available) without making Web2 a gatekeeper. Legacy systems can bridge to sovereign infrastructure while preserving Internet 3.0 sovereignty.

Constitutional Governance Binding

CYRUS© cryptographically binds the Wyoming Sovereign Purpose Trust governance structure on-chain for 1,000 years, ensuring:

✓ Immutable Purpose

Trust's purpose (sovereign infrastructure) cryptographically locked—cannot be changed by any party

✓ Trustee Oversight

Professional trustees administer per Wyoming law—no equity owners, no corporate control

✓ No Ownership Structure

Foundation exists in perpetuity for its purpose—no one can acquire or control it

Key Protection: Even Charter Members have no governance rights over the Foundation. This ensures TitleChain serves 170+ nations impartially for 1,000 years. Learn more about governance →

Standards Library

Open technical standards for sovereign digital infrastructure, registry protocols, and interoperability frameworks

CYRUS© Binding Protocol

TCID© inscription, cryptographic binding, human-first origination, and post-quantum security requirements.

M5 USC© Classification

M1–M5 asset classification framework: physical cash, deposits, securities, commodities, and digital bearer instruments.

TitleChain© Registry Requirements

Registry persistence, lineage preservation, ownership proofs, and jurisdiction-native compliance standards.

Node Classes

Validator, witness, oracle, storage, and PSN (Private Sovereign Node) operational specifications.

Interoperability Schemas

Legacy + sovereign bridging protocols, translation layers, and dual-stack compatibility frameworks.

Compliance & Audit Proofs

Jurisdiction-specific compliance templates, audit trail requirements, and regulatory attestation protocols.

Human/Agent Policy Requirements

Human-in-the-loop standards, agent delegation rules, and automated system constraints.

ICSN Sovereign Namespace

Four-layer namespace architecture (L1–L4) coordinated through net3.eth master registry.

Privacy-First Architecture

Zero-knowledge proofs, selective disclosure, encrypted data handling, and privacy-preserving computation standards.

Identity & Web3 Standards Compliance

M5POD (Personal Operating Domain)

Based on ODI (Open Data Institute) principles and Solid POD architecture, M5POD provides users with self-sovereign data storage and control.

  • Solid POD Compatible: Full compliance with Tim Berners-Lee's Solid protocol
  • Open Data Institute Standards: Privacy-preserving personal data stores
  • User-Controlled: You own your data, identity, and access permissions
  • Portable: Move your POD between M5Bank and any Solid-compatible provider
  • Encrypted: Zero-knowledge architecture—M5Bank cannot access your POD data

Web3 & Identity Standards

M5 infrastructure adheres to globally recognized Web3 and decentralized identity standards:

  • W3C DID (Decentralized Identifiers): Self-sovereign identity anchoring
  • W3C Verifiable Credentials: Cryptographic credential verification
  • Open Web3 Wallet Standards: Interoperable across 118+ IBC chains
  • OAuth 2.0 / OpenID Connect: Secure authentication protocols
  • ISO 20022: Extended message containers for financial transactions
  • ERC-20: Fungible token standard (currencies, commodities)
  • ERC-721/1155: NFT standards for unique & semi-fungible asset tokenization
  • ERC-1400/1404: Security token standards with compliance & transfer restrictions
  • ERC-3525: Semi-fungible tokens (SFT) for complex asset structures
  • ERC-4626: Tokenized vault standard for yield-bearing assets
  • Git3© Protocol: Decentralized code repository & attestation (supported by Git3Hub & Git3Labs)

M5Cloud: Sovereign Infrastructure Stack

Cloud-independent, sovereign-first infrastructure: M5Bank and member nations are not dependent on Google Cloud, AWS, or Azure. Our tokenized hybrid cloud stack enables full sovereignty with flexible deployment options.

M5Cloud Architecture

Kubernetes on OpenStack: We run Kubernetes on top of OpenStack, using OpenStack to provision the underlying VM infrastructure and networking for Kubernetes clusters. This delivers:

  • Infrastructure Control: OpenStack manages VMs, networking, storage
  • Application Agility: Kubernetes orchestrates containerized workloads
  • Tokenized Hybrid: Deploy across M5-owned data centers + member on-premises
  • On-Prem Ready: Full stack deployable within sovereign borders
  • No Vendor Lock-In: Zero dependency on hyperscaler platforms

Alternative: M5Bank members can run the M5Cloud OpenStack control plane on Kubernetes, benefiting from Kubernetes' lifecycle management and automation for OpenStack services themselves.

Sovereign AI & Privacy

M5 Deterministic Offline LLMs: Our intelligence engine runs on private GPU infrastructure to ensure Sovereign AI standards and complete data separation.

  • Private GPU Clusters: No data sent to external AI providers (OpenAI, Anthropic, etc.)
  • M5Bank Member POD Isolation: Each member's personal data remains encrypted and isolated
  • M5 Canonical Engine Privacy: Training, learning, and skill models remain closed and private
  • Deterministic Inference: Reproducible AI outputs for regulatory compliance
  • Sovereign AI Compliance: Nations control their AI infrastructure within their jurisdiction

Key Principle: M5Bank cannot access member POD data. AI models run locally within sovereign infrastructure boundaries.

🛡️ Zero Dependency on Hyperscalers: M5 runs on self-managed OpenStack + Kubernetes infrastructure, ensuring nations and institutions retain full control over their digital sovereignty without reliance on Google, Amazon, or Microsoft.

Download Standards Pack Apply for Standards Working Group

Interoperability: Legacy Internet + Finance

Lawful migration paths from Web2 and traditional finance into Internet 3.0 sovereign infrastructure

ICANN / DNS Bridge

ICSN supports a lawful migration path from legacy Web2 naming into Internet 3.0 without creating dependence or gatekeepers.

  • Dual-stack compatibility for legacy DNS where needed
  • Title-lock and proof-of-control mapping for domains
  • Clear separation: interop is translation, not dependence
  • Reference relationships: ICANN compatibility where applicable

Note: ICANN is referenced for compatibility only. ICSN operates independently with sovereign namespace control.

SWIFT BRIDGE©

An optional interoperability layer for credentialed institutions to participate in sovereign Internet 3.0 index and exchange economy.

Important: SWIFT BRIDGE© is not controlled by "10 central banks." It is a standards-based participation framework aligned with the member reality of SWIFT.

  • Maps institutional credentials (e.g., SWIFT codes) into modern credentialing
  • Enables previously excluded institutions (credit unions, agencies) to participate
  • Violations result in credential suspension visible in-wallet
  • Due process exists, enforcement is immediate at credential layer

Institutions see counterparty credential status in real-time as active, deactivated, or under review.

Git3Labs© & Git3Hub©

Global laboratory network and canonical contract repository for sovereign innovation

Git3Labs©

A global lab network for credentialed members—universities, research centers, agencies, and builders—advancing sovereignty, sustainability, and human-first innovation.

Focus Areas:

  • Standards pilots and test suites
  • Proof-of-concept implementations
  • Security and cryptography research
  • Interoperability testing
  • Sustainability and energy-efficient protocols

Git3Hub©

A canonical contract and document repository where creators and inventors can publish, license, and receive direct compensation—while keeping title and rights intact.

Repository Includes:

  • Ricardian templates — human + machine readable contracts
  • Issuance and minting toolkits
  • Escrow and adjudication flows
  • Executable contract packages
  • Provenance and wallet-split enforcement

Accreditation Paths

Clear pathways for nations, institutions, operators, and research partners to participate in ICSN

Sovereign Registrar

Nation/state/tribe root authority for jurisdiction-native namespace control and monetary sovereignty.

Operator

Registry services, SBaaS© deployment, and interoperability delivery for credentialed jurisdictions.

M5 Node Provider

Infrastructure operators running validator, oracle, storage, witness, or PSN nodes.

Institution Member

Financial institution or agency credentialing for participation in sovereign exchange networks.

Research Partner

Git3Labs© member conducting standards research, testing, and proof-of-concept development.

Standards Working Group

Technical contributor to ICSN protocol development, specification drafting, and standards evolution.

Accreditation Process Includes

✓ Identity & Entity Verification

Credentialed verification of participant identity and legal standing

✓ Jurisdiction Mapping

Clear jurisdictional boundaries and legal authority documentation

✓ Technical Attestation Readiness

Infrastructure capability and technical compliance verification

✓ Policy Commitments

Privacy, non-capture, and agent rules compliance attestation

Issuance of credentials and publication to registry manifest upon successful completion.

Start Accreditation Intake

Common Questions

Answers to key questions about ICSN governance, technical architecture, and participation

Is ICSN a DAO?

No. ICSN is a standards coordination body, not a decentralized autonomous organization. Governance is vested in credentialed sovereigns and working group members, not token holders.

Who controls the root?

net3.eth serves as the master registry coordinating sovereign namespaces. No single entity controls the root—authority is distributed across credentialed sovereigns at L2 (national), L3 (state/tribal), and L4 (municipal) layers.

How do you prevent capture?

Funding does not confer authority. Participation does not convey governance rights. Standards are stewarded by credentialed sovereigns and working group consensus, not investors or platforms.

Do you custody assets?

No. ICSN is standards and coordination only. Custody is provided by credentialed operators under declared law. ICSN never holds, controls, or touches member assets or value.

How does CYRUS Binding relate to Bitcoin anchoring?

CYRUS© Binding uses Bitcoin for public notary anchoring—timestamped integrity proofs published to Bitcoin's immutable ledger. This provides tamper-evident timestamps without Bitcoin controlling the registry or custody.

Can a credit union participate without a SWIFT© code?

Yes. SWIFT BRIDGE© enables previously excluded institutions (credit unions, agencies, community banks) to participate using modern credentialing instead of legacy SWIFT© codes.

What happens if an operator violates policy?

Credentials are suspended and counterparties see the status in-wallet as deactivated or under review. Due process exists, but enforcement is immediate at the credential layer to protect the network.

How is rehypothecation handled?

Rehypothecation is tracked in lineage. Title cannot be duplicated or hidden. Any secondary use of assets is recorded in the chain-of-custody, preserving transparency and preventing fraud.

How is privacy preserved without creating honeypots?

Privacy is a pre-political human right. Zero-knowledge proofs, selective disclosure, and encrypted M5POD© architecture prevent honeypot creation. Users control what becomes public.

What is M5 USC© (M1–M5) and how does it prevent surveillance money?

M5 USC© is our economic framework classifying value across five layers: M1 (utility/currency), M2 (commodities), M3 (one-of-a-kind assets: identity, vehicles, NFTs), M4 (securities), M5 (financial instruments: gov-to-gov, interbank, central bank-to-bank settlement). This prevents "surveillance money" by preserving privacy-appropriate asset classes and preventing forced traceability of all transactions.

What is NYCP© and how does it enable cross-border enforcement?

NYCP© (New York Convention Protocol) integrates the New York Convention (1958) — ratified by 170+ nations — into TitleChain's Title Standards. The first implementation, nycp26.eth under unitednationschain.eth, enables constitutional-grade arbitration enforcement across borders. In the U.S., this is implemented through Chapter 2 of the Federal Arbitration Act (9 U.S.C. §§ 201–208).

Why is Wave 1 called "Deployment Chain" instead of "Priority Launch"?

"Deployment Chain" emphasizes inaugural infrastructure nodes launching Internet 3.0. Wave 1 features UK (Oxford M5Node with Sir Tim Berners-Lee), US (California, New York, Wyoming, Texas), Bhutan, Switzerland, and Singapore. These aren't just "priority" — they're the foundational deployment infrastructure for sovereign banking.

What makes Wyoming special in the TitleChain infrastructure?

Wyoming hosts the TitleChain Sovereign Purpose Trust — a 1,000-year noncharitable purpose trust designed to outlast corporations, governments, and technological paradigm shifts. Wyoming's favorable digital asset laws and trust statutes make it the constitutional home for Internet 3.0 governance. The wyomingchain.eth deployment is Wave 1 Priority #3.

How does Charter Membership differ from investment?

Charter Membership is infrastructure sponsorship, not investment. Charter Members fund the launch and deployment of Internet 3.0 infrastructure (M5Nodes, ICSN coordination, energy sector pilots). There is no equity, no securities offering, and no promise of financial returns. Charter Members receive recognition as Constitutional Founders supporting 1,000-year digital sovereignty infrastructure.

What are the Charter Membership levels and how many spots are available?

260 total founding positions available across four tiers: Tier 1 — Constitutional Founder ($5M+, 10 spots) sponsors complete M5Node deployments with permanent trust recognition; Tier 2 — Sovereign Partner ($1M-$4.9M, 30 spots) co-sponsors nodes with working group participation; Tier 3 — Infrastructure Supporter ($250K-$999K, 70 spots) funds specific components; Tier 4 — Founding Member ($50K-$249K, 150 spots) contributes to general infrastructure. All levels receive recognition in the 1,000-year constitutional framework.

Can M3 one-of-a-kind assets include my identity and vehicle title?

Yes. M3 is designed for unique, non-fungible assets including identity credentials (TCID©), vehicle titles, real estate deeds, and NFTs. Each M3 asset has a distinct provenance and cannot be duplicated. This is fundamentally different from M1 (fungible currency) or M2 (commodity units). M3 preserves individual ownership records while preventing unauthorized duplication.

Why isn't M5 available for retail use?

M5 financial instruments are institutional/sovereign-level only by design. M5 enables government-to-government settlements, interbank transfers, and central bank-to-commercial bank operations. Restricting M5 to institutional use prevents retail surveillance while maintaining appropriate oversight for high-value sovereign financial operations. This constitutional separation protects consumer privacy (M1-M3) while enabling institutional coordination (M5).