Your message is encrypted in your browser and sent as a memo on the XRP Ledger. Nothing is stored here.
Step 1 of 3
How it works
How it works
death.box encrypts a message in the browser and publishes the ciphertext as a memo on an XRP Ledger (XRPL) payment. The message text is protected. Transaction metadata is public.
Procedure
Input. Enter a message and a passphrase. Use a long, random passphrase that is not used anywhere else.
Encryption (in the browser). A key is derived from the passphrase with PBKDF2-HMAC-SHA-256 (250,000 iterations, random 16-byte salt). The message is encrypted with AES-256-GCM using a random 12-byte IV. A new salt and IV are generated for every message.
Submission. The service receives only the destination address and the ciphertext. It submits an XRPL payment of 1 drop with the ciphertext attached as a memo. The death.box sender account signs the transaction and pays the network fee.
Retrieval. Look up transactions by recipient address, or paste the memo text. Decryption runs in the browser. The passphrase is never sent to the service.
What is visible on the ledger
Protected
Public and permanent
Message text
Ciphertext
Passphrase (never leaves the browser)
Destination address and sender account
–
Amount, timestamp, memo size
Notes
The service does not see the plaintext or the passphrase.
Sender and recipient are not hidden.
A lost passphrase cannot be recovered. Anyone who has both the ciphertext and the passphrase can read the message.
Sending is paid by the death.box sender account (1-drop payment plus network fee).