Opaque envelopes
Text, files and images are encrypted on the client. The server sees the route, type and size — but not the content or the names.
Invite-only · E2E · Zero-knowledge
End-to-end encryption on your device: the server relays only opaque envelopes and deletes offline messages after confirmation. Keys never leave the device, and access opens by paid invitation — no ads, no strangers, no message reading.
Platforms: Web · Android APK · iPhone — no app by policy · why
How the protection works
Three things set EDEL apart from an ordinary messenger: opaque relaying, local keys and disappearing offline messages.
Text, files and images are encrypted on the client. The server sees the route, type and size — but not the content or the names.
Ed25519 + X25519, XChaCha20-Poly1305 and a master password. The private key never goes online; the QR backup is sealed with your password.
A message waits on the server only until the recipient signs a confirmation — then it is deleted. History is an encrypted blob.
Three steps
A code from a member or a paid access package. There is no random registration — the circle stays closed.
A master password and a name. The key pair is generated locally; only the public address goes to the server.
The web client via QR approval from your phone, or the Android APK. One identity — your keys on every screen.
Paid access
Payment opens invitations, not ads. Packages: $10 / 2 invites, $20 / 5 invites, $35 / 10 invites. Credits are issued after the transfer is confirmed.
From $3.50 per invite. Exact package prices are loaded from the server and may change.
$10 / 2 invites
$20 / 5 invites
$35 / 10 invites
Access is paid directly in USDC or USDT on Base to the treasury address. Packages: $10 / 2 invites, $20 / 5 invites, $35 / 10 invites. Credits are issued after the transfer is confirmed; keep the transaction hash. Packages, prices and payout rules may change. This is not an investment product: no income, buyback or liquidity is guaranteed. Terms — Terms, Privacy, Risk and Referrals.
Verifiable security
Verifiable security
Every security claim is tied to an artifact you can fetch: a signed web manifest, an APK hash and a server build endpoint. What we do not claim is listed too.
FAQ
Yes. Content is encrypted on the device before sending, and the server receives only an opaque envelope. Only you and the recipient hold the decryption keys.
Registration is closed: you need an invitation from a member or a package of invitation codes. Payment is direct in USDC or USDT on Base.
They are stored encrypted on the server until the recipient sends a signed confirmation, then deleted. Chat history is a separate encrypted blob.
No. The Android app installs from an APK directly and does not depend on Google Play Services; the web client runs in a browser.
The profile is restored from a QR key backup (SCB2) with your master password. Without the backup and password, the correspondence cannot be recovered — that is the price of zero knowledge.
No. We do not plan an iOS app: our threat model requires an OS we control and can reason about, and documented cases of data access at the OS level make iOS unsuitable for confidential messaging. The web client remains available in Safari.
Paid access funds development and support. Packages are one-time purchases, not a subscription; there is no recurring membership fee.
Fetch manifest.json and manifest.sig, verify the Ed25519 signature with the pinned key, then compare SHA-256 of every .js/.mjs/.html. APK hashes are in /api/v1/version. Full table: /verification.html.