In 2008, Satoshi Nakamoto solved a decades-old problem: proving a transaction occurred at a specific time without trusting a central authority. The solution was a Merkle tree—each transaction is hashed, those hashes combined and hashed again, repeating until a single root hash represents the entire history. “Change anything, and the root changes. The fraud is mathematically detectable by anyone, without permission from anyone.”
Blockchain became synonymous with cryptocurrency, but the underlying breakthrough was about trust without intermediaries. The same principle applies to file transfer, yet this problem remains unsolved.
The unsolved trust problem in data transport
Daily across Europe, sensitive data moves between hospitals and specialists, lawyers and counterparties, industrial systems and control centers, financial institutions and regulators. All face the same challenge: proving transfer occurred, wasn’t tampered with, and arrived—without relying on vendors or servers to confirm truth.
Current solutions store audit trails on their own servers, requiring trust in platforms that may be breached, acquired, or subject to court orders. “This is not a theoretical concern. It is the operational reality of every major file transfer platform in use today.”
The same math. A different problem.
Ghost Pipe applies Merkle tree architecture to file transport with a fundamental difference: “the content is never stored anywhere.” Each transfer creates a leaf in a Merkle tree. The relay hashes the transfer, appends it to the log, and signs the resulting root with a post-quantum ML-DSA-65 key. The log is append-only and public—anyone can verify a transfer occurred at a specific time without knowing what was transferred.
The file exists in RAM only and is destroyed after one read. What remains is pure mathematical proof requiring no trust in Paramant, vendors, or authorities.
Why quantum changes everything, and why we built this now
Blockchain’s cryptographic foundations face quantum vulnerability. “Bitcoin’s ECDSA signatures can be broken by Shor’s algorithm.” Ghost Pipe avoided this mistake.
The system uses ML-KEM-768 (NIST FIPS 203, finalized August 2024) for key exchange and ML-DSA-65 (NIST FIPS 204) for signatures—both post-quantum standards mathematically immune to Shor’s algorithm. “An adversary who records Ghost Pipe traffic today cannot decrypt it after Q-Day.” The Harvest Now, Decrypt Later strategy is eliminated by design.
What we actually shipped
This is running infrastructure, not theoretical documentation:
-
Ghost Pipe relay: post-quantum encrypted transport with RAM-only, burn-on-read architecture. Five sector relays live: healthcare, legal, finance, industrial IoT, and general. Free managed relay at paramant.app or self-hostable in under two minutes.
-
Public CT log: live Merkle audit log at paramant.app/ct showing every registered relay and transfer proof. Publicly verifiable without account requirements.
-
44 CLI tools: sector-specific workflows for healthcare (NEN 7510, DICOM), legal (eIDAS), industrial OT (IEC 62443), finance (NIS2/DORA), and government.
-
ParamantOS: bootable relay server. Plug in USB, boot, and a hardened post-quantum relay runs with no configuration or Docker knowledge needed.
-
Python and JavaScript SDKs: with full inclusion proof support for cryptographic delivery verification.
-
Compliance documentation: mapped to NIS2, NEN 7510, IEC 62443, eIDAS, and GDPR Art. 28 requirements—technical documentation, not marketing claims.
-
Full source code: auditable, forkable, self-hostable. No vendor dependency, no US infrastructure. Hetzner Frankfurt only. No US CLOUD Act exposure.
The EU sovereignty angle
Blockchain’s trust model is global and stateless, creating sovereignty problems. Ghost Pipe differs by design: “You run it in your own jurisdiction. On your own server. With your own keys.” The managed relay runs on Hetzner in Frankfurt under German law and EU jurisdiction, with no American cloud provider in the stack.
For European healthcare providers, legal institutions, industrial operators, and government agencies, jurisdiction matters. “GDPR Art. 28 requires documented processor agreements. NIS2 requires EU-jurisdiction infrastructure. Ghost Pipe satisfies both by default.”
The EU invested billions in digital sovereignty programs. “The missing piece was not policy or funding. It was infrastructure that actually worked this way by design, not by compliance checkbox.”
Why this should have existed a decade ago
The Merkle tree was published in 1979. Certificate Transparency applied it to TLS certificates in 2013. It took until 2026 for application to file transport with post-quantum cryptography and zero-storage architecture.
“Every organization in Europe that handles sensitive data, medical, legal, financial, critical infrastructure, is currently using file transfer software built on an architecture that will be broken by quantum computers, stores data on servers that can be seized, and provides audit trails controlled by vendors.”
Ghost Pipe is the alternative: free, open source, EU sovereign, quantum-safe, and running now.
https://paramant.app
Better a warrior in a garden than a gardener in a war.