SP-1
The Substrate Protocol

§1 Purpose and Scope

The current state of artificial intelligence deployment creates a fundamental problem: AI systems make consequential decisions with no cryptographic proof of what they decided, why they decided it, or whether they were authorized to decide at all.

This is not primarily a safety problem. It is an economic and legal accountability problem. Organizations deploying AI face liability exposure from decisions that cannot be reconstructed, audited, or defended in regulatory proceedings. Courts cannot evaluate AI decisions that leave no deterministic trail. Regulators cannot audit AI systems that operate as black boxes.

SP-1 defines the infrastructure layer that eliminates this problem. A system conformant with SP-1:

• Produces a cryptographic proof of every execution — before the result is returned
• Enforces governance constraints architecturally — violations are structurally impossible, not merely prohibited
• Compresses all state with post-quantum resistant algorithms — no plaintext persists or transits
• Anchors every proof to immutable external storage — no single party controls the audit record
• Settles economic value in direct proportion to verified utility — pricing is a proof, not an estimate

§2 The Substrate Atom (SA)

The fundamental unit of SP-1 is the Substrate Atom (SA). Every datum, event, proof, decision, delta, advisory, and system state in an SP-1-conformant system must be represented as an atom. Nothing flows through the system that is not an atom.

2.1 Atom Structure

2.2 Atom Validation Rules

Any SP-1 node MUST reject an atom that fails any of the following checks:

§3 Cryptographic Requirements

SP-1 mandates a hybrid classical + post-quantum cryptographic posture. Systems claiming SP-1 conformance that use only classical cryptography are NOT conformant. The hybrid approach is required: an adversary must break both classical and post-quantum schemes simultaneously to compromise an atom.

3.1 Required Algorithm Stack

3.2 HybridKEM Session Key Derivation

# Session key derivation — must break BOTH to compromise
x25519_ss   = X25519(ephemeral_sk, peer_pk)
ml_kem_ss   = ML-KEM-1024.Decapsulate(ciphertext, sk)
session_key = SHA3-256(
    x25519_ss ‖ ml_kem_ss
    ‖ DOMAIN_SEP            # "PBTG_GENESIS_SOVEREIGN_V1"
    ‖ CONSTITUTIONAL_ANCHOR  # "d38dad17"
)

3.3 HybridSig Binding

# Both signatures required — one is never sufficient
ed25519_sig  = Ed25519.Sign(msg ‖ anchor ‖ DOMAIN_SEP, sk, ts)
dilithium_sig = ML-DSA-87.Sign(msg ‖ anchor ‖ DOMAIN_SEP, sk, ts)
binding      = SHA3-256(
    ed25519_sig ‖ dilithium_sig
    ‖ DOMAIN_SEP ‖ CONSTITUTIONAL_ANCHOR
)

3.4 Key Rotation and Anti-Replay

Session keys MUST rotate every 3600 seconds. A nonce registry MUST prevent replay attacks. Any atom with a timestamp outside ±300 seconds of the receiver's current time MUST be rejected.

§4 FractalFold Compression

All atom content MUST be compressed before any other cryptographic operation. No plaintext content may ever appear in memory storage, wire transit, or log output. The only exception is at the precise moment of projection (use), after which the content must be immediately re-compressed.

4.1 FractalFold Algorithm

# Step 1: Compress
compressed = ZLIB(content, level=9)

# Step 2: Compute fold coordinate (content address)
h1         = BLAKE2b_k(content, key=PBTG_PQC_WM[:32], digest_size=32)
h2         = SHA3-256(content ‖ CONSTITUTIONAL_ANCHOR)
fold        = BLAKE2b_k(h1 ‖ h2 ‖ CONSTITUTIONAL_ANCHOR,
                         key=PBTG_PQC_WM[:32], digest_size=16)

# Step 3: Holographic coordinate
coord       = SHA3-256(
    content ‖ ts_ns ‖ domain ‖ origin_did
    ‖ CONSTITUTIONAL_ANCHOR ‖ DOMAIN_SEP
)

The fold coordinate is a content address — it uniquely identifies the atom content without revealing it. The holographic coordinate is a spacetime address — it encodes when, where, and by whom the atom was created.

§5 Proof of Legitimate Execution (PoLE)

Every execution in an SP-1-conformant system MUST produce a Proof of Legitimate Execution (PoLE) before returning its result. The PoLE is not an afterthought audit record. It is a precondition of execution.

5.1 PoLE Structure

5.2 Immutable Anchoring

PoLE receipts MUST be anchored to at least one external immutable store within 60 seconds of generation. SP-1 specifies two tiers:

§6 WEI Economy

SP-1 includes an economic model. A protocol without economic enforcement is not a protocol — it is a recommendation. WEI is the unit of substrate participation.

6.1 WEI Mechanics

§7 Deterministic Consensus Layer (DCL)

SP-1-conformant networks of more than one node MUST implement the Deterministic Consensus Layer. Single-node deployments MAY operate in self-consensus mode.

7.1 DCL Requirements

• Quorum: ⌈2/3 of active validators⌉ — Byzantine Fault Tolerant
• Vote timeout: 2 seconds. Timeout = REJECT (fail closed)
• All votes are PQ-signed (ML-DSA-87 + Ed25519)
• All votes are sealed atoms (AES-256-GCM + FractalFold)
• All consensus results ghost-chained for immutable record
• Slashing enforced on validators exceeding disagreement threshold

§8 Five Sovereign Laws

Every SP-1-conformant system MUST enforce the following laws architecturally. Enforcement by policy document is insufficient and does not constitute conformance.

§9 Conformance Levels

§10 Reference Implementation

The Genesis Protocol, operated by Point Break Trading Group LLC, serves as the reference implementation of SP-1. It is not the only valid implementation — it is the first.