1) Drop files ➜ 2) Set password ➜ 3) Export encrypted vault
Drag & drop PDFs, images, docs, zips — anything. SkyeProofx computes SHA-256 for each file, then encrypts everything with AES‑GCM using a key derived from your password (PBKDF2). Nothing leaves your browser.
PBKDF2 iterations: 250000 • Salt: random 16 bytes • Cipher: AES-GCM If you forget the password, the vault cannot be recovered. Keep a secure copy.
Output includes: manifest.json, proof.json, HASHES.txt, and encrypted/*.
Open an encrypted vault zip and decrypt on demand
Drop your SkyeProofx vault zip here. Then enter the password to decrypt files. The app verifies encrypted-file SHA-256 + plaintext SHA-256 receipts.
Verify originals against receipts
This mode verifies SHA-256 for original files against a SkyeProofx manifest.json (or a full vault zip). No password needed for original-hash verification.
Drop manifest.json or a SkyeProofx vault .zip. Then drop the original files you want to verify.
Drag & drop original files here. SkyeProofx will compute SHA-256 and compare to the manifest receipts.
Runtime board: checking for same-folder operator review runtime…
No runtime review board loaded.
Staged Files
0 files0 bytes
SkyeProofx is client-side. Your files stay in your browser memory, then you download an encrypted vault zip. The zip can be stored anywhere (Drive, local disk, external). Verification works offline.
Proof boundary: this folder proves local hashing, encryption, decryption, and verification logic in the browser. It does not provide account sync, password recovery, remote attestation, or third-party timestamping.
Local receipt trail: this folder also keeps a browser-local activity log for vault builds, vault opens, decrypts, and verification runs. You can export that trail as JSON from this page.
When
Event
Vault
Detail
No local activity yet.
Review Pack
Status
Owner
Target
Checkpoint / Notes
No runtime review packs yet.
Name
Size
Type
SHA-256
Actions
Drop files to begin.
Tip: For “proof wall” style evidence, export the vault zip + keep HASHES.txt and proof.json with it. Hashes prove integrity; encryption enforces confidentiality.