Skip to content

RFC: NFT Sending (contacts) #514

Open
0 of 1 issue completed
Open

Description

@gp0p3

Description

Sending an NFT means moving it from one of my purses (#512) to a purse of the recipient. The sender picks a person from their contacts and knows nothing else about them. The recipient side is resolved without the sender learning the recipient's accounts: the item lands in the recipient's next free purse. NFT purses now have cheques, as Coinage has for coins; what is missing is a cheque addressed to a picked contact.

Motivation

A Static cheque needs the recipient’s static receive key and their identity account, which names their payment inbox, and the sending product seals and publishes the cheque to that inbox itself. A contact handle gives none of this: it resolves only inside createTransaction. The Contacts API (#484) tells us who the recipient is; nothing tells us where to send the item.

Requirements

  • Send an NFT to a picked contact without knowing any of their addresses.
  • The sender learns at most one receiving account and nothing else about the recipient's purses.
  • Sending works when the recipient is offline; delivery cannot require both people to be online at once.
  • The item appears on the recipient’s shelf without manual setup on their side, even if they have never opened the product.
  • Same behaviour on every host (desktop, mobile, web).

Activity

  1. added
    area:rfcAn RFC, or work tracked by one under docs/rfcs
    on Aug 26, 2026
  2. added theissue type on Aug 26, 2026
  3. changed the title [-]RFC: NFT Sending[/-] [+]RFC: NFT Sending (contacts)[/+] on Sep 3, 2026
  4. leonardocustodio commented on Sep 29, 2026

    @leonardocustodio
    Member

    I would say this is necessary for products in general, not just NFTs / Scarcity.
    Maybe something similar to this? Could be added to the Contacts API, idk, @filvecchiato ?

    **The host carries product payloads** (host-rust-core)
    
    contacts.sendProductPayload({ to: Username | ContactHandle, productId, payload (≤ 16 KiB) }) -> DeliveryId
    contacts.productPayloadSubscribe() -> stream { from: Username (host-verified), payload }
    
    - The host resolves the name, shows consent, and delivers.
    - The host already does this for attachments and for the coin-payment handoff channel (`truapi/src/v01/coin_payment.rs:114-121`).
    - **Effect:** proof, privacy and notification together, with no new crypto on our side.
    
  5. added
    R3+Can be done for R3 or further
    and removed on Oct 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

R3+Can be done for R3 or furtherarea:rfcAn RFC, or work tracked by one under docs/rfcsspa:scarcityScarcity SPA

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions