QuanChainQuanChain
Back to Technology
Core Technology

DTQPE System

Dynamic Transcendent Quantum Proof Encryption - A parent identity + ephemeral child rotation architecture where no public key ever protects value on-chain. 20 security levels with variable-length address hashing, SpendAndRotate atomic transactions, and dual-path quantum threat assessment.

05101520CLASSICALHYBRIDPOST-QUANTUMLEVEL 2020 LevelsADAPTIVE SECURITY
Problem

The Quantum Problem — Solved Structurally

Every blockchain shares a fatal assumption: that a public key can safely guard value on-chain.Shor's algorithm on a quantum computer can derive a private key from its public key in polynomial time. The standard fix — post-quantum signatures — are enormous (up to 30KB each), crippling throughput. DTQPE solves both problems: all value is locked behind address hashes, never public keys. Ephemeral child keys rotate on every transaction via SpendAndRotate, so the public key is exposed only after funds have moved. The quantum threat reduces to Grover's quadratic speedup against hashes — not Shor's exponential break against keys.

20 Security Levels

1-5
Classical
64-96 bits
Algorithms
L1: ECDSA-secp256k1-SHA256L2: ECDSA-secp256k1-SHA384L3: Ed25519L4: ECDSA + RSA-2048L5: ECDSA + RSA-4096
Use Case

Micropayments, everyday transactions. Address hash: 128-192 bits (SHA3-256 truncated)

Key Size
33-545 bytes
Sig Size
64-576 bytes
6-11
Hybrid
128-192 bits
Algorithms
L6: Dilithium2 + ECDSA-secp256k1L7: Dilithium2 + ECDSA-P256L8: Dilithium3 + ECDSA-P384L9: Dilithium3 + Ed25519L10: Falcon-512 + RSA-4096L11: Falcon-512 + ECDSA-P384
Use Case

Significant holdings, active wallets. Address hash: 256-320 bits (SHA3-256/384)

Key Size
946 B - 2 KB
Sig Size
786 B - 3.4 KB
12-15
Post-Quantum
64-256 bits
Algorithms
L12: SPHINCS+-SHA2-128fL13: SPHINCS+-SHA2-192fL14: SPHINCS+-SHA2-256fL15: Dilithium5 + Falcon-1024
Use Case

High-value accounts, institutional custody. Address hash: 384-512 bits (SHA3-384/512)

Key Size
32 B - 4.4 KB
Sig Size
5.9 KB - 29.8 KB
16-19
Reserved
256+ bits
Algorithms
L16: Reserved (Round 4)L17: Reserved (Round 4+)L18: Reserved (Future)L19: Reserved (Future+)
Use Case

Reserved for future NIST standardization rounds and novel cryptographic constructions

Key Size
TBD
Sig Size
TBD
20
Parent Identity
512 bits
Algorithms
L20: Dilithium5 + SPHINCS+-256f (composite AND-construction)
Use Case

Permanent parent wallet identity. 1024-bit BLAKE3-extended address hash. Used once at registration + emergency recovery.

Key Size
2.6 KB
Sig Size
34.4 KB

Parent/Child Wallet Architecture

Parent Identity + Ephemeral Children

Parent Identity + Ephemeral Children

Permanent Level 20 parent wallet (Dilithium-5 + SPHINCS+-256f composite) generates ephemeral child wallets that rotate on every transaction. No public key ever protects value at rest.

SpendAndRotate

SpendAndRotate

Every transaction atomically spends from the current child, derives a new child, registers a forwarding rule, and updates the parent resolution table. Key rotation is invisible to the user.

Variable-Length Address Hashing

Variable-Length Address Hashing

Address hash scales with value: 128-bit (Level 1) to 1024-bit (Level 20). Format: QC{level}_{base58_hash}. Grover resistance from 64 to 512 bits.

Merkle Derivation Proofs

Merkle Derivation Proofs

Child wallets prove legitimacy via compact Merkle proofs (~640 bytes) without parent involvement. Tree depth 20 supports 1M+ children per parent.

Dual-Path Cracking Cost Model

Dual-Path Cracking Cost Model

Security quantified in dollars via min(Grover preimage 2^(n/2), BHT birthday 2^(n/3)). Three-tier triggers: Suggested (3x), Automatic (1.5x), Emergency (10x).

Recovery & Forwarding

Recovery & Forwarding

Parent composite signature enables emergency recovery. O(1) forwarding registry resolves any historical address to the current active child.

Invisible Migration via SpendAndRotate

1

Dual-Path Cost Analysis

Oracle calculates effective cracking cost via min(Grover preimage, BHT birthday collision, Shor key recovery) for each security level.

2

Three-Tier Triggers

Suggested (balance > cost/3), Automatic (balance > cost/1.5), Emergency (balance > cost/10). Each tier escalates response.

3

Invisible Upgrade

Next SpendAndRotate derives the new child at a higher level. No hard forks, no special transactions, no user action. Migration is just a normal transaction.