Write your message
Enter a message and choose a strong, unique passphrase. The message is encrypted in your browser before anything is sent to the service.
Private messages · Public ledger
Write a message, encrypt it on your device, and carry the encrypted memo on the XRP Ledger. The message stays encrypted on-ledger; transaction details remain public.
Enter a message and choose a strong, unique passphrase. The message is encrypted in your browser before anything is sent to the service.
death.box derives an encryption key with PBKDF2, SHA-256, and 250,000 iterations, then encrypts the message with AES-256-GCM. A fresh random salt and initialization vector are generated for each message.
The service receives the destination address and encrypted text, then submits an XRPL payment with the ciphertext attached as a memo. The configured death.box sender account submits the transaction and pays the network fee.
Search ledger transactions for a recipient address, or paste the encrypted text directly. Decryption happens in your browser with the passphrase; the passphrase is not sent to the service.
The passphrase is required to decrypt a message and cannot be recovered if lost. Use a strong passphrase that you have not used elsewhere. Anyone with both the ciphertext and its passphrase can read the message.
No. Encryption happens in your browser. The send request contains the destination address and ciphertext, not the plaintext or passphrase.
No. Ledger activity is public. Addresses, transaction timing, amount, and memo ciphertext are visible even though the message itself is encrypted.
There is no recovery mechanism. Keep a safe copy of the passphrase; without it, the encrypted message cannot be decrypted.
The configured death.box sender account submits a 1-drop payment and covers the XRPL network fee. The encrypted memo is attached to that transaction.