Demonstration · Data movement
SFTTM: Secure File Transfer
A one-directional, quantum-safe way to move a file from a sensor, a reporting system, or a ground node into a protected store. Each file is sealed as a single record: a lattice key establishes the session, a symmetric record layer encrypts the bytes, and a device signature binds the sender. The receiver opens it and checks integrity before trusting a single byte.
The sealed record
One file, one sealed record
The private key never leaves the node that generated it. The receiver verifies the signature and the integrity tag before the plaintext is released.
Try it
Seal a file and open it back
Choose a file from your device or use the sample telemetry batch, then seal it. The page encrypts the bytes with real AES-256-GCM, builds the transfer manifest, and immediately opens the record back to prove the integrity tag.
Transfer manifest
-
Opened content
-
Self-test pending.
What is real and what is sample
Honest about the layers
Real, in your browser
The AES-256-GCM record layer is performed by the native Web Crypto API on this page. The ciphertext, nonce, and integrity check you see are genuine, and the file never leaves your device.
Sample, from the enclave
ML-KEM-1024 session establishment and the ML-DSA-87 device signature run inside the enclave on an authenticated node. Their sizes and fingerprints are shown here as labeled sample values so the record workflow is complete end to end.
One direction
Secure File Transfer is built for one-way flows: sensor telemetry, financial reporting, and government feeds that move into a protected store without opening a return path.
FLAG: not a live transfer service. This page seals and opens a record locally to demonstrate the workflow. A live deployment runs the lattice layer and the signed, hash-chained audit inside the enclave, gated by XQ Zero Trust policy. Locators and fingerprints on this page are sample values, not live credentials.
See it on your feeds