Industry-standard cryptographic hash. The same algorithm used to anchor Bitcoin transactions. Your document's fingerprint is mathematically unique and impossible to fabricate.
0
Uploads Required
Files are hashed locally in your browser. The document never leaves your device. EPPE receives the hash, not the file. Sensitive documents stay sensitive.
0
Accounts or Sign-ups
No email. No password. No profile. No cookies. You open EPPE, you hash a document, you get a timestamped proof. That is the complete user journey.
Solana
Blockchain Anchor
The hash is submitted as a Solana transaction. The blockchain timestamp is immutable. The document's existence at that moment is permanently recorded on a public ledger.
CS
Relay Operation
The Solana relay server is operated by Celaya Solutions. No account or wallet requirement stands between the user and the timestamped proof flow.
972
Architecture Lines
The architecture document is 972 lines. Full iOS app source included. Relay server endpoints documented. Everything needed to verify or audit the system is in the documentation.
Design Principles
Nine absolutes.
01
No sign-up
Zero accounts. No email. No identity required to prove a document's existence.
02
No upload
Files never leave the device. The hash travels, not the document.
03
No tracking
Zero analytics. Zero telemetry. No third-party scripts. No session recording.
04
No analytics
EPPE does not know how many people use it. That is intentional.
05
SHA-256 only
One algorithm. Industry standard. Cryptographically sound. Not proprietary.
06
Solana-anchored
Public ledger. Immutable timestamp. Independent of Celaya Solutions servers.
07
CS-operated relay
The relay server is maintained by the lab. Civic access remains direct and uncomplicated.
08
Open architecture
972-line architecture document and full app source available for review.
09
El Paso first
Built for this community. Not a generic product. Civic infrastructure for home.
Access
Open. No account. Ready now.
EPPE is live. Bring a document you want to prove existed at a specific moment in time. Open it, drag a file, get a hash, get a Solana transaction ID. Done.
Drop a file into EPPE. Any file type. The file is read locally in your browser.
02
CryptoKit computes a SHA-256 hash of the file contents. The file is never sent anywhere.
03
The hash is sent to the Celaya Solutions relay server, which submits it as a Solana transaction.
04
You receive a transaction ID. The timestamp is permanent, public, and independent of any third party.
Build History
From a principle to infrastructure.
Principle
Evidence before claims.
The principle that drove EPPE: you should be able to prove a document existed at a specific moment before you make any public claim based on it. Hash it, anchor it, then speak. This is the Sealed Envelope Protocol.
Architecture
972-line specification document.
Full architecture documented before a single line of app code was written. SHA-256 implementation, Solana relay server endpoints, iOS app structure, privacy requirements, brand guidelines — all specified first.
Build
iOS app source complete.
SwiftUI app with CryptoKit SHA-256, PHPickerViewController for local file selection, zero external dependencies. Files never leave the device by architecture, not just policy.
Deployed
Relay server live. CS-operated.
Solana relay server deployed and operated by Celaya Solutions. No user wallet is required. The civic accountability flow stays direct: hash, anchor, verify.
Project Jupiter
First major use case: active litigation.
The Project Jupiter water analysis was anchored using the Sealed Envelope Protocol before publication. The resulting Solana transaction is now referenced in Case D-307-CV-2025-02766.