Skip to content

RFC: Contacts API #484

Closed
Closed

Description

@filvecchiato

Source PR: #17 · docs/rfcs/contacts-api.md · @filvecchiato

Description

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.

Tasks

Activity

  1. self-assigned this
    on Aug 24, 2026
  2. filvecchiato commented on Aug 25, 2026

    @filvecchiato
    CollaboratorAuthor

    implementation and RFC: #17

  3. linked a pull request that will close this issuefeat(ios): draw the contact picker #907on Sep 23, 2026
  4. linked a pull request that will close this issuefeat(android): draw the contact picker #939on Sep 23, 2026
  5. gp0p3 commented on Sep 24, 2026

    @gp0p3

    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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

R2 blockerMust be done for R2area:rfcAn RFC, or work tracked by one under docs/rfcsspa:scarcityScarcity SPA

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions