yas
Yaacov Akiba Slama

YAS

Public Key

npub1x8c26vdzu4v8my7ujljph2f73syql0kyd08ae0h4tk3gr22fdufqc38fl0

Profile Code

nprofile1qqsrru9dxx3w2kraj0wf0eqm4ylgczq0hmzxhn7uhm64mg5p49yk7ysprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hszrthwden5te0dehhxtnvdakqfxfvsf

Publishing to

relay.snort.social

relay.damus.io

nos.lol

Author Public Key

npub1x8c26vdzu4v8my7ujljph2f73syql0kyd08ae0h4tk3gr22fdufqc38fl0

Show more details

Last Notes

2026-01-13 14:29:18 UTC

- reply

Re 5. The passkey is used explicitly for the wallet.
Re 6. A regular user doesn't store his passkeys in his desktop, and the passkey stays in his phone or physical key and only the prf result is sent to the desktop.

2026-01-12 13:15:17 UTC

- reply

1. The client can regularly check the relays and republish the list of salts if they are deleted.
2. Every vendor can setup their own relay.
3. The list of salts is backup-ed automatically by ios/android because its in the app data and is not "secret".
4. The same list can be exported by the client to a simple text file if the user wants a wallet independent backup and doesn't want to run any app using this protocol for a long time.
5. Passkey rotation is generally not needed because the secret part of the passkey is not supposed to leave the TEE except when migrating from one vendor to another (using a secure protocol like CXP). In the exceptional case of a passkey compromise, the user can always move its funds to another wallet using a new passkey.
6. The UX cost of using iCloud/GDrive is very high (login, vendor auth)

2026-01-12 09:45:44 UTC

- reply

The primary salt is an hard coded string defined in the protocol. Using it the list of the salts used by the same passkey can be obtained from the relays.
If by "the user trusts his nostr relays to store the salt", you mean to trust the relays to not delete them, trusting iCloud/GDrive is not better.
Also, Breez intent is to mitigate the trust by handling a relay dedicated to store the salts.