NiuMeta: A Zero-Trust Network Towards a Type I Civilization

Languages / 语言: English · 简体中文

What is NiuMeta, in one sentence: a zero-trust network protocol built on a Ticket-based Sovereign Intranet (TSI) — letting individuals, institutions, and AI compute providers handle custody, cross-border settlement, and confidential computation without relying on any centralized custodian, while still satisfying nation-state-grade compliance.

Whose problem does it solve: regulators lack a ledger that is simultaneously compliant and tamper-proof; institutions lack a settlement channel that is zero-trust yet high-performance; developers lack audited, drop-in infrastructure crates for building on top of a zero-trust network.

⭐ If NiuMeta's design resonates with you, please consider giving this repo a Star — it's the most direct way to support open, community-audited infrastructure.

CRITICAL NOTE: This is not a future vision or a theoretical whitepaper—it is a fully developed, rigorously tested, and production-ready implementation. The workspace contains 312 Rust crates. tokei reports ~2.8 million lines of Rust Code: ~2.0 million production, ~400k in standalone test directories, and ~600k in in-src test modules. This core architecture has completed development and testing, and will be progressively fully open-sourced.

Ticket-based Sovereign Intranet (TSI)
Official Website: www.niumeta.com

While AI is displacing programmers, NiuMeta is creating 6 million stable, irreplaceable income opportunities for developers worldwide.

Supported by 25 immutable constitution files deployed to the core, we are launching a $5.5M global bounty program. We invite elite developers worldwide to co-audit the core infrastructure before our official launch and progressive full open-source release.

Try the mobile client: Install the v1.0 app to see first-hand that a decentralized wallet can match the everyday experience of a centralized one.

---

Three Structural Differences from Bitcoin

Bitcoin proved that a ledger without a trusted third party can exist. NiuMeta does not try to replace it. It answers a question Bitcoin's design never set out to answer: when the right to participate can be bought without limit, what stops decentralization from decaying into institutionalization? All three differences below follow from that question.

1. Redefining "decentralization": from distributed hashpower to distributed real people

Bitcoin defines decentralization as "anyone may join anonymously and vote with hashpower." That definition carries an implicit premise: that hashpower stays distributed. Fifteen years on, a handful of pools persistently command the majority of network hashrate, ASIC manufacturing sits with a few vendors, and spot ETFs have concentrated custody of a large share of BTC into a few institutions. Under "anonymous + purchasable participation," the equilibrium of one-CPU-one-vote is one-dollar-one-vote. That is not a failure of execution; it is an outcome the definition permits.

NiuMeta changes the atomic unit of participation from "a unit of hashpower" to "one KYC-verified real natural person or legal entity":

• One identity document, one number. A single real identity maps to exactly one Principal network-wide. An account that has not passed KYC cannot complete node binding or staking registration.
• One real subject → at most one seat in each of three node classes. At most 1 Guardian seat, 1 Expert node, and 1 AI node. The cap is enforced by the protocol in the identity domain — not a social convention, and not something capital can route around.
• No anonymous access. Every request must carry multi-dimensional authorization credentials; unauthorized traffic is physically dropped before it reaches the business layer, leaving the network invisible to scanners and DDoS.
• Exit burns the seat. After voluntary or forced exit, the identity is permanently barred from that role and the seat is never recycled — the cost of monopoly rises monotonically over time.
• Client isomorphism. Every Expert on the network runs the same image, attested against an on-chain whitelist; operators may not modify the client (tampering → rejected peering / slashing). Which class of work a node receives is assigned by the protocol, not cherry-picked by the operator.

The consequence: capital cannot be converted into protocol weight. A second seat requires a second real human willing to be identified. The slope of that curve is population, not money.

This is a deliberate trade. NiuMeta gives up permissionlessness to buy resistance to institutionalization. It is a Ticket-based Sovereign Intranet (TSI) — not a public chain, and it does not pretend to be one.

2. Redefining "the chain": from longest-chain probabilistic finality to independent finality at every height

In Bitcoin, ordering and finality emerge from cumulative work under the longest-chain rule. Finality is therefore probabilistic: roughly ten minutes per block, conventionally six confirmations, and in principle always reorganizable by a longer chain.

NiuMeta's finality does not come from "whose chain is longer." It comes from a threshold-signature certificate formed independently at every height: one block per height, no fork choice, no longest-chain rule, no reorgs. The trust anchor is the aggregate threshold signature together with permissioned admission, so confirmation requires no accumulation — final on arrival, with durability additionally stamped on the storage side by the sovereign storage nodes.

The parent chain also plays a different role in each system. In Bitcoin the parent hash is part of the finality mechanism itself (work accumulates along the chain). In NiuMeta the parent chain belongs to the verification layer — it serves chain-walking validation for light clients and replay, while fund safety, unforgeability, and finality are guaranteed independently by the threshold certificate. The two are decoupled. That yields a property Nakamoto's structure does not have: the chain-level commitment covers not only the contents of the previous block, but also which group of seats finalized it and the supervision records written into it after finality — the consensus proof and the supervision outcome are themselves objects of the chain commitment, not attachments hanging off-chain.

Because shard ledgers are independent, each shard forms its own parent chain rather than sharing one network-wide.

3. From one chain to many independent parallel chains, converging at the phone

Bitcoin is one global chain: every full node replays every transaction, throughput is bounded by the slowest full node, and everything depends on global broadcast.

NiuMeta is many independent parallel chains:

• Universal isomorphic sharding. Every node runs an identical image. No specialized shards, no super-nodes.
• Each shard is an independent ledger with an independent parent chain. There is no global business ledger and no global broadcast — the surface that requires global coordination is deliberately kept minimal.
• Cross-shard value moves over dedicated channels carrying threshold certificates, rather than through one global ledger.
• Parallelism only grows. Shard count increases monotonically with network scale; a capacity shortfall never shrinks it.

It converges at the phone. With no global ledger, where is "the truth of the world" anchored? On every handset:

• Each user's L0 meta node (the phone) independently verifies the ledger relevant to it using leap synchronization. The protocol provides a compressed historical commitment structure for this, putting a century's worth of verifiable history in the tens-of-megabytes range — low-end devices can complete the full verification.
• The phone verifies more than the aggregate signature: it also validates the legitimacy of the signer set itself. This is not "verify the signature and ignore who signed."
• The phone is simultaneously the sole source of identity (one document, one number; the credential issuer) and an independent verifier of the ledger. It never asks a node "what is my balance" — it computes it.

The anchoring surface for truth is therefore not one globally replicated chain, but hundreds of millions of endpoints, each holding a sovereign identity and verifying independently. Shard count grows with the network and the anchoring surface grows with the number of real people — neither is bounded by the bandwidth of a single chain.

At a glance

---

Real-World Problems Solved by NiuMeta

Every row below maps to domain modules already implemented in the workspace, and becomes independently verifiable as the progressive open-source phases land.

---

Architecture & Protocol Features

NiuMeta employs a highly decoupled Modular Domain Architecture alongside a high-concurrency, zero-dependency data structure engine. Combined with efficient threshold signatures and universal isomorphic sharding, it provides high-speed parallel channels tailored for diverse business scenarios.

flowchart TD
    Client["Client / SDK<br/>(L0 physical + L1 type layer only)"] -->|ticketed request| Firewall{"TSI Dual Admission Firewall<br/>physical + logical"}
    Firewall -->|unauthorized traffic| Drop(["physically dropped<br/>invisible to scanners / DDoS"])
    Firewall -->|authorized ticket| Gateway["High-Frequency Domain Gateway"]
    Gateway --> Router["Smart Routing Engine<br/>ms-level global load sensing"]
    Router --> Experts["Distributed Secure Computing<br/>Expert Clusters"]
    Router --> Guardians["Guardian Nodes<br/>Decentralized Sovereign Storage"]

• Ticket-based Sovereign Intranet (TSI) Every access request must carry multi-dimensional authorization credentials. Before reaching the business logic layer, requests are intercepted by a fully automated physical and logical dual admission firewall. Unauthorized traffic is physically dropped, ensuring the network remains invisible to scanners and DDoS attacks.
• Pure-Assembly Ultra-Lightweight Clients Desktop clients and SDKs rely exclusively on the underlying physical layer (L0) and type definition layer (L1). The core business logic remains an absolute black box to the client. Terminals are fortified with a financial-grade anti-tamper sandbox and a hardware-level physical defense line, guaranteeing zero user asset leakage.
• High-Frequency Domain Gateways & Smart Routing Utilizing High-Frequency Domain Gateways as the ingress, the intelligent routing engine senses the global network load in milliseconds and automatically dispatches requests to the optimal Distributed Secure Computing Service Providers (Expert Clusters).
• Decentralized Sovereign Storage Built upon a global network of Sovereign Data Storage Nodes (Guardians), ensuring absolute data perpetuity and self-healing capabilities.

---

$5.5M Developer Bounty Program & Constitution Audit

At its core, NiuMeta is governed by 25 immutable constitution files deployed post-genesis (encompassing foundational economic parameters, staking tier tables, and root-level protocol rules).

We have launched a global developer bounty program offering up to $5,500,000. We invite elite security experts and developers worldwide to co-audit these constitution files. Upon the successful completion of the audit, the protocol will officially launch and progressively transition to full open-source.

• Audit Objective: Scrutinize the determinism and security of the mc-constitution core module, verifying its exponential defense characteristics against Sybil attacks.
• How to Participate: Navigate to the mc-constitution directory to review the complete constitutional design philosophy and code implementation. Submit your vulnerability reports or optimization proposals according to the Audit Guidelines.

---

Repository Structure Overview

This public mirror houses the Phase 1 open-source components and audit tooling of the NiuMeta ecosystem. The primary directory structure is as follows:

Root-level study documents: PROTOCOL550_EXECUTION_PLAN_EN.md · 执行方案（中文）

Additional node daemons, gateways, and full-domain engines (client-expert, client-guard, mc-gateway, consensus cores, etc.) are released in later Progressive Open Source phases — see the roadmap below.

---

🚀 5-Minute Quickstart

Fastest way in: install the v1.0 mobile client. Using it yourself is the clearest way to see that a decentralized wallet can match a centralized one.

Developers can also get a local, buildable feel for the SDK layer published in this mirror — no live network endpoint required:

git clone https://github.com/niumeta/niumeta.git
cd niumeta/niumeta-sdk-rs

# Type-check the public SDK facade (L0 + L1 only — no L3 business logic pulled in)
cargo check -p niumeta-sdk

# Run a leaf client crate's own test suite as a smoke check
cargo test -p mc-wallet

Next steps:

• Browse niumeta-sdk-rs/README.md for the full optional-feature matrix (bridge, settlement, solver, storage clients, and more).
• Head to mc-constitution/ to review the immutable constitution files — the primary target of the $5.5M audit bounty.

---

Progressive Open Source Roadmap

NiuMeta is fundamentally positioned as a Ticket-based Sovereign Intranet (TSI). We believe open-source is a tool to earn trust, not a vector to transfer sovereignty. To defend against "resource hegemony" and malicious hard forks attempting to siphon network compute and ecosystem value during our early stages, NiuMeta will execute a progressive open-source rollout across four phases as the physical defense network scales:

flowchart LR
    P1["<b>Phase 1 · Now</b><br/>Trust &amp; Transparency<br/>mc-constitution, bridge,<br/>ZK modules, SDKs"]
    P2["<b>Phase 2 · 50K Guardians</b><br/>Verifying Capabilities<br/>Gateway peripherals, storage core,<br/>client-guard / client-desktop"]
    P3["<b>Phase 3 · 100K Guardians</b><br/>Advanced Domains<br/>Confidential supercompute,<br/>AI TEE, scheduling engines"]
    P4["<b>Phase 4 · 300K Guardians</b><br/>Full AA-Level Open Source<br/>mc-consensus, mc-tsi,<br/>kernel-space XDP"]
    P1 --> P2 --> P3 --> P4

• Phase 1: Establishing Trust and Fundamental Transparency (Current Phase)
  • Status: Open immediately.
  • Core Open-Source Content: mc-constitution (economic model and immutable constitution parameters), cross-network bridge proxies, ZK verification modules, and extensive no_std type definition crates and pure-function SDKs.
  • Objective: To prove to ecosystem participants the absolute purity and immutability of the economic foundation, while providing a complete suite of integration tools.
• Phase 2: Verifying Capabilities (Target: 50,000 Guardian Nodes)
  • Core Open-Source Content: Application-layer gateway peripherals, decentralized sovereign storage core logic (Blind Write), and all L4 client execution shells (e.g., client-guard, client-desktop).
  • Objective: By open-sourcing the desktop terminal and gateway, we conclusively prove to the community that all nodes adhere to the principle of being a read-only telemetry mirror, containing no privileged backdoors or centralized intervention mechanisms.
• Phase 3: Releasing Advanced Domains (Target: 100,000 Guardian Nodes)
  • Core Open-Source Content: Confidential supercomputing engine (Zone 0x3A), AI TEE verification computing agents, core business scheduling engines, and high-frequency domain gateway proxy tools.
  • Objective: To unleash high-value compute economic domains, facilitating the seamless audit and integration of large-scale bare-metal computing clusters.
• Phase 4: Full Component AA-Level Open Source (Target: 300,000 Guardian Nodes)
  • Core Open-Source Content: mc-consensus (Turbulence consensus core), mc-tsi (Sovereign Intranet state machine), anti-DPI traffic shaping modules, and all kernel-space XDP interception code.
  • Objective: Once the globally distributed physical network and computing capacity form an insurmountable historical moat, we will entirely open-source all underlying engine code.

Code can be copied, but the historical reputation database of global TEE devices, the concurrent defense web formed by 300,000 nodes, and the sovereign ticket threshold issued via multi-dimensional cryptography constitute the true, unreplicable barrier that no forked network can bypass.

---

About NiuMeta

The intellectual property of NiuMeta belongs to all of humanity. We have not registered any trademarks in any global jurisdiction, nor have we applied for any software patents. NiuMeta is a fully open-source, publicly shared protocol. A tribute to Satoshi Nakamoto, for the advancement of human civilization.

---

Last updated: 2026-08-31