Reading as device:?
Reading as deviceEach message is sealed separately for every recipient device. Pick a device here to decrypt the transcript with that device's key — exactly what that person would see. In a real deployment only the device's owner holds its private key.
the Board Chair · Principal iPhonethe Board Chair · Principal MacBookChief of Staff · COS iPhoneComms Director · Comms iPhoneComms Director · Comms iPadSummit Lead · Summit Pixel
safety #: 37043 88203 22163 85376 26410 82034 51378 71729 90028 23576 41757 11290
- the Board Chair · 8/6/2026, 6:07:28 AMLocking the run-of-show by Friday. Keep this channel tight.
- Chief of Staff · 8/6/2026, 6:07:28 AMCopy. Green room and motorcade timing confirmed.
- Summit Lead · 8/6/2026, 6:07:28 AMStage and AV walk-through tomorrow at 0900.
- Comms Director · 8/6/2026, 6:07:28 AMEmbargoed remarks drafted — sending the sealed version here only.
What the server actually stores?
On-the-wire envelopeThis is the raw record the server keeps for the latest message: iv (a one-time nonce), eph_pub (the sender's per-message public key), and ciphertext (the sealed bytes). There is no plaintext column anywhere — only a holder of the recipient device's private key can read the message.
?
On-the-wire envelopeThis is the raw record the server keeps for the latest message: iv (a one-time nonce), eph_pub (the sender's per-message public key), and ciphertext (the sealed bytes). There is no plaintext column anywhere — only a holder of the recipient device's private key can read the message.
wire.envelope
$ halo show --raw --lastiv: it8jO6V65zelTwj6eph_pub: MCowBQYDK2VuAyEAN+FhnfYyLrW12elI5ZQQ4hO24O19…ciphertext:Bhz1aUYVICd8yf0tqszpGjuH2HnPlXtquumVsscM/bXN…plaintext: <never stored on server>