You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A product asks the host to let the user pick a contact. The host renders the picker itself, the user selects one person, and the product receives one opaque 32-byte handle — never the list, a name, or an account.
Motivation
Each user has a different alias and account per context, so the contact list is a private notebook no product can read, and users paste raw keys instead. Sending to a friend needs one recipient the user chose, not the address book.
Requirements
One method, pick, taking no arguments; the host owns the overlay and draws it from its own chat contacts.
Outcomes are Picked { handle }, Dismissed and NoContacts; a host with no picker answers Unsupported.
No permission is requested — the user selecting a contact is the consent.
The handle is stable per contact across every product and host, keyed on the user's entropy so it cannot be turned back into an account.
The handle is resolvable, not usable: the core substitutes the account when it builds the transaction.
Read-only, one contact per call, and hosts keep their own contact schema.
Tested #17 on the CLI: a handle only works inside createTransaction and always resolves to the one account the host stores for that contact. Our sends will be coinage-style with NFT purses (#512): we give the contact the private key of our own purse holding the item, and they move the NFT out of it into their own purse. So we need a way to send that key to the contact encrypted, e.g. a host call that seals a payload to a handle. Could the Contacts API (#484) cover that?
Activity
filvecchiato commentedon Aug 25, 2026
implementation and RFC: #17
gp0p3 commentedon Sep 24, 2026
Tested #17 on the CLI: a handle only works inside createTransaction and always resolves to the one account the host stores for that contact. Our sends will be coinage-style with NFT purses (#512): we give the contact the private key of our own purse holding the item, and they move the NFT out of it into their own purse. So we need a way to send that key to the contact encrypted, e.g. a host call that seals a payload to a handle. Could the Contacts API (#484) cover that?