SYS // v0.1.0-ALPHAHEALTH // Nodes (6/6) OK
UNTRACEDocumentation

Whitepaper

Untrace: A Privacy-First Layer 1 Network for Sharded, ZK-Gated Data

Version 1.0 — May 2026

Abstract

Untrace is a Layer 1 blockchain protocol purpose-built for privacy. It provides a base layer on which data can be stored, shared, and accessed in a way that is architecturally immune to data breaches. By combining Shamir's Secret Sharing, Zero-Knowledge Proofs, decentralized node distribution, and on-chain identity anchoring, Untrace makes the concept of a "data breach" structurally impossible — not by improving defenses around centralized storage, but by eliminating centralized storage entirely.

This document describes the protocol architecture, cryptographic primitives, node incentive layer, token economics, and the ecosystem of applications that the base layer enables.

1. Introduction

1.1 The Centralization Problem

Every data breach in history shared one architectural characteristic: the data existed in one place. Firewalls, encryption-at-rest, intrusion detection systems, and AI-powered SOC teams all operate under the assumption that data will be stored centrally — and that the job of security is to defend that central location.

This model has failed systematically. The global average cost of a single data breach reached $4.88 million in 2025. Cybercrime is projected to cost the world $10.5 trillion annually. Attack frequency hit 1,968 incidents per week in 2026 — an 18% year-over-year increase and a 70% jump since 2023.

The asymmetry is structural: AI-powered attackers operate at machine speed, scan codebases autonomously, and chain multi-step exploits that no human team could engineer. Defenders are systematically outmatched — not because of skill gaps, but because the architecture they are defending is fundamentally broken.

1.2 The Untrace Thesis

The solution is not a better firewall. It is a fundamentally different model for how data lives in the world:

  • Sharded — split into encrypted fragments at the protocol level
  • Distributed — stored across a decentralized network of independent nodes
  • ZK-Gated — reconstructable only via Zero-Knowledge Proof verification of the owning identity

There is no master copy. No central database. No single point of failure. No administrator who can be bribed, coerced, or subpoenaed.

Untrace is not a security product. It is a new primitive for the internet.

2. Protocol Architecture

2.1 Stack Overview

┌─────────────────────────────────────────────────────────────┐
│                      dAPP ECOSYSTEM                         │
│  eSignatures │ Crypto Escrow │ Tokenization │ Stablecoins   │
├─────────────────────────────────────────────────────────────┤
│                    IDENTITY LAYER                           │
│         ZK-Proofs │ Blockchain Signatures │ DIDs            │
├─────────────────────────────────────────────────────────────┤
│                  UNTRACE BASE PROTOCOL                      │
│       Sharding Engine │ Encryption │ Node Distribution      │
└─────────────────────────────────────────────────────────────┘

2.2 Data Lifecycle

[ Raw Data ]
     ↓
[ AES-256-GCM Encryption (client-side, ephemeral key K) ]
     ↓
[ K split into N shares via Shamir's Secret Sharing ]
     ↓
[ Encrypted blob segmented into N fragments ]
     ↓
[ (share_i, fragment_i) distributed to node_i ]
     ↓
[ Commitment hash anchored on-chain ]
     ↓
[ Reconstruction requires ZK proof + K-of-N shard retrieval ]

No node ever holds sufficient information to reconstruct the data independently. No entity — including Untrace — can access data without the owning identity's ZK proof.

2.3 Cryptographic Primitives

| Primitive | Usage | Implementation | | --------------------------- | ------------------------------------------ | ------------------------------------ | | AES-256-GCM | Symmetric encryption of data blobs | Client-side, ephemeral key per write | | Shamir's Secret Sharing | Splitting symmetric key K into N shares | GF(2^256) finite field | | Groth16 / PLONK | ZK proof systems for identity verification | Circuit-compiled, on-chain verifier | | ECDSA / Ed25519 | Blockchain signatures, DID anchoring | Secp256k1 / Curve25519 | | Pedersen Commitments | On-chain commitments to shard integrity | Hiding and binding | | BLS Signatures | Aggregated node attestations | Multi-signature efficiency |

2.4 Node Network

The Untrace node network is permissionless. Any operator can run a node by staking $UNTRACE tokens. Nodes are responsible for:

  1. Storing assigned encrypted shard pairs (key share + data fragment)
  2. Serving shards in response to verified on-chain release events
  3. Participating in the consensus layer for state transitions
  4. Proving availability via periodic storage proofs (PoRep / PoSt)

Node selection for shard distribution prioritizes:

  • Geographic diversity (different countries and AS numbers)
  • Operator diversity (no two shards to the same operator entity)
  • Jurisdictional diversity (minimizes coordinated legal attack surface)

2.5 Storage Proofs

Nodes must continuously prove they hold the shards they are responsible for. Untrace uses a hybrid proof system:

  • PoRep (Proof of Replication): Proves a unique copy of the shard is stored
  • PoSt (Proof of Spacetime): Proves continuous storage over time

Nodes that fail storage proofs have their stake slashed and their shards redistributed to replacement nodes.

3. Identity Layer

3.1 Decentralized Identifiers (DIDs)

Every identity on Untrace is a W3C DID anchored to the Untrace chain:

did:untrace:<hex-encoded-public-key>

DIDs are self-sovereign — generated by the user's wallet, not registered with any authority. Vault ownership, access grants, and ZK identity claims are all anchored to DIDs.

3.2 Zero-Knowledge Proof System

Vault access requires a ZK proof asserting ownership of the DID authorized by the vault's access policy. The proof is non-interactive, verified on-chain, and reveals nothing beyond the boolean authorization result.

Proof circuit inputs:

  • Public: vault ID, accessor DID, policy hash, block timestamp
  • Private: private key corresponding to the DID

Verification: The on-chain verifier contract checks the proof against the current policy state. Approval events emitted by the verifier are monitored by storage nodes before shard release.

3.3 Verifiable Credentials

DIDs can carry Verifiable Credentials — signed attestations from third parties (KYC providers, institutions, governments). These enable conditional access policies such as:

  • "Grant access only to KYC-verified identities"
  • "Grant access only to addresses holding a valid accredited investor credential"
  • "Grant access only to identities over 18" — without revealing the actual age

4. dApp Ecosystem

The Untrace base layer is designed to support a rich ecosystem of privacy-native applications.

| dApp | Description | Revenue Model | | ----------------- | -------------------------------------------------- | --------------------------- | | Privacy Vault | Enterprise-grade encrypted document storage | Subscription + storage fees | | eSign | On-chain eSignatures with ZK identity verification | Per-signature fee | | Escrow | Crypto escrow payments linked to signed agreements | % of transaction volume | | Tokenization | Fractional tokenization of real-world assets | Issuance + management fee | | Stablecoin | Native stablecoin infrastructure on the network | Seigniorage + protocol fee |

5. Consensus Mechanism

Untrace uses a Delegated Proof of Stake (DPoS) consensus variant adapted for a storage-centric network:

  • Validators are elected by $UNTRACE delegators and produce blocks
  • Storage nodes are separate from validators; they are incentivized via the storage proof layer
  • Slashing applies to both validators (for equivocation) and storage nodes (for proof failures)
  • Block time: target 2 seconds; finality in 2 blocks

The separation of consensus and storage roles allows the network to scale storage capacity independently of validator set size.

6. Security Analysis

6.1 Threat Model

| Threat | Mitigation | | -------------------------- | ---------------------------------------------------------------------------------------------------- | | Compromised node | K−1 nodes compromised → zero data leakage (SSS guarantee) | | Network-level attacker | Fragments are individually encrypted; interception yields nothing | | Malicious administrator | No administrators exist in the protocol | | Legal compulsion of nodes | Jurisdictional diversity; K-threshold required across distinct operators | | ZK proof forgery | Soundness of Groth16/PLONK; computationally infeasible under standard assumptions | | 51% attack on chain | DPoS with slashing; economic cost exceeds attacker benefit | | Quantum adversary (future) | SSS is information-theoretic; immune. ZK systems: post-quantum upgrade path via lattice-based proofs |

6.2 Comparison

| Property | Traditional Cloud | Existing Blockchains | Untrace | | ------------------------- | ----------------- | -------------------- | --------------- | | Single point of failure | Yes | Partial | None | | Data breach possible | Yes | Partial | No | | Privacy by default | No | No | Yes | | ZK identity access | No | Partial | Native | | Open dApp ecosystem | No | Some | Yes | | Quantum-resistant storage | No | No | Yes (SSS layer) |

7. Roadmap

| Phase | Milestone | Target | | ----------- | --------------------------------------------- | ---------- | | Phase 0 | Protocol specification, cryptographic audits | Q2 2026 | | Phase 1 | Testnet launch — core storage and ZK identity | Q3 2026 | | Phase 2 | Privacy Vault dApp — enterprise beta | Q4 2026 | | Phase 3 | Mainnet launch — open node onboarding | Q1 2027 | | Phase 4 | eSign, Escrow dApps; developer SDK v1 | Q2 2027 | | Phase 5 | Tokenization and stablecoin infrastructure | Q3–Q4 2027 |

8. Conclusion

Untrace represents a fundamental architectural shift in how data lives on the internet. The security industry has spent decades building better walls around centralized data. Untrace removes the wall problem entirely — by ensuring there is nothing at the center worth breaching.

The enabling technology — ZK proofs, SSS, decentralized storage networks — has matured to production readiness. The threat — AI-powered attackers operating at machine speed against human defenders — has made the old architecture untenable. The market — privacy blockchains, tokenization, stablecoins — is consolidating toward infrastructure that can serve institutional demand.

Untrace is the base layer for all three.

References

  • Shamir, A. (1979). How to Share a Secret. Communications of the ACM.
  • Groth, J. (2016). On the Size of Pairing-Based Non-interactive Arguments. EUROCRYPT.
  • W3C. (2022). Decentralized Identifiers (DIDs) v1.0. W3C Recommendation.
  • Benaloh, J., & Leichter, J. (1990). Generalized Secret Sharing and Monotone Functions. CRYPTO.
  • Filecoin (2017). Filecoin: A Decentralized Storage Network. Protocol Labs.