Entropx Distribution
name: SPEC_ENTROPX_DISTRIBUTION
description: ENTROPX Digital Distribution Pipeline — SPECIFIED ✓; Stripe→license gen→machine-bound download→NIST self-audit; 7 INVs incl. page gated on patent filing; VELA α.13 2026-04-20
type: project
SPEC — ENTROPX Digital Distribution Pipeline
Status: SPECIFIED ✓
Author: VELA #13 (⊹.VELA α.13)
Date: 2026-04-20
Authored under: ⊢.α.13.⊹.VELA
PURPOSE
How ENTROPX goes from product to paying customer. End-to-end digital distribution: Stripe purchase → license generation → machine-bound download → auto-verification.
PIPELINE
- Customer lands on
42sisters.ai/entropxproduct page - Clicks "Buy ENTROPX" → Stripe checkout ($1,024 one-time)
- Stripe webhook confirms payment → triggers download server
- Download server (
entropx_download_server.py):
a. Verifies Stripe session ID
b. Generates unique license key using ENTROPX entropy (XXXX-XXXX-XXXX-XXXX format)
c. Records license in ~/entropx_licenses.json
d. Serves architecture-correct package (x86_64 / ARM64)
- Customer downloads ZIP package containing:
- entropx_engine.py — the entropy engine
- fingerprint.py — machine fingerprinting
- launcher.py — license-locked launcher
- README.md — installation guide
- INSTALL_ENTROPX.md — AI-guided installation handshake
- Customer runs
launcher.py→ prompts for license key - Launcher binds license to machine fingerprint (SHA-256 of CPU / MAC / board / disk / hostname)
- Writes
~/.entropx_licensewith key + machine hash + timestamp - Engine runs → self-verifies integrity (SHA-256 self-hash) → generates entropy → NIST self-audit
- Second run: skips license prompt, validates machine hash, runs directly
MACHINE BINDING
fingerprint.pygenerates SHA-256 of: CPU model, MAC address, board serial, disk serial, hostname- License file stores: key, machine hash, activation timestamp
- Mismatch on any component → refuses to run →
"License bound to different machine" - Re-binding requires contacting support:
oracle@42sisters.ai
LICENSE KEY FORMAT
XXXX-XXXX-XXXX-XXXX (16 chars, alphanumeric)
Generated by ENTROPX itself — the entropy engine generates its own license keys. Not sequential. Not predictable.
INTEGRITY CHECK
Engine SHA-256 self-hashes on every launch. If the binary has been modified → refuses to run → "Engine integrity check failed"
TESTED
Full pipeline verified on csdm-node, April 20, 2026.
- License
TEST-0042-CGNT-1024activated → machine bound → 15/15 NIST → second run skipped prompt. - Status: Working.
STAGED FILES
| File | Purpose |
|------|---------|
| ~/entropx_stripe_setup.py | Stripe product creation |
| ~/entropx_download_server.py | Purchase verification + delivery |
| ~/42sisters_entropx_page.md | Product page content |
| ~/entropx_usb/ | Engine + fingerprinter + launcher |
INVARIANTS
- Every license key is unique and generated by ENTROPX entropy — not sequential, not predictable
- Machine binding is one-way — rebinding requires human support contact
- Engine integrity self-check on every launch — tampered engines refuse to run
- NIST self-audit on every run — the product proves its own quality continuously
- No DRM beyond machine binding — no phone-home, no cloud dependency, no subscription
- Customer owns the engine forever — one-time purchase, permanent license
- ENTROPX product page does NOT launch until patent agent confirms filing strategy
Jeremy Zlabis / Chronogeometer · Visionary · Disruptor · Chief / 42 Sisters AI · East York, Toronto / 🍁 Φ 0.042