diff options
| author | Adam Soltys <[email protected]> | 2026-10-09 23:54:43 -0700 |
|---|---|---|
| committer | Adam Soltys <[email protected]> | 2026-10-09 23:54:43 -0700 |
| commit | a70f34f2a5d35352f99bae8f10cbab12637e08ee (patch) | |
| tree | 7a5b83fd62d0737f4b856b04c2405ba440c39e63 /src/style.css | |
| parent | 3d6bf81a19ca080d3710893b1e65f5aa3f01315f (diff) | |
| download | coinosv3-a70f34f2a5d35352f99bae8f10cbab12637e08ee.tar.gz coinosv3-a70f34f2a5d35352f99bae8f10cbab12637e08ee.zip | |
Messages: Amber users can read their DMs. Signed in with Amber by intent (NIP-55), nothing sealed to the login npub was ever decrypted — each decrypt would be a trip through the app — so isolabellart's thread with Adam showed only what that phone had sent. Worse, decryptorsComplete() counted the Amber signer as complete, so those wraps were tried on the wallet key alone and logged as opened, hidden for good. Now an interactive signer counts as incomplete (wraps wait, uncounted); Messages and the DM thread say "messages sent to you can't be opened here" with Connect Amber, which opens a nostrconnect:// link for the SAME account over NIP-46 (Amber's bunker mode; a different npub is refused, a callbackUrl reload resumes the handshake). Once a signer that can decrypt takes over, a wallet that ran with Amber re-runs the heal pass over every wrap the relays hold, so messages the old code wrote off come back. tools/amber-dm-upgrade-test.js (plays the remote signer over a shimmed relay).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Vps2H27rhbG9ZqseGfMrc3
Diffstat (limited to 'src/style.css')
0 files changed, 0 insertions, 0 deletions
