An infographic of the Silent Payments flow (thanks, Codex!).

Raw JSON

{
  "kind": 1,
  "id": "aee8a88ddacf609185ba321508b1b2a27dc791ec206d95ba208a185b2baa4c1b",
  "pubkey": "06b7819d7f1c7f5472118266ed7bca8785dceae09e36ea3a4af665c6d1d8327c",
  "created_at": 1779367568,
  "tags": [
    [
      "t",
      "silentpayments"
    ],
    [
      "r",
      "wss://relay.getsafebox.app/"
    ],
    [
      "r",
      "wss://espelho.girino.org/"
    ],
    [
      "r",
      "wss://relay.nostrplebs.com/"
    ],
    [
      "r",
      "wss://relay.primal.net/"
    ],
    [
      "r",
      "wss://atlas.nostr.land/invoices"
    ],
    [
      "imeta",
      "url https://blossom.primal.net/6ec9c49a31b748e98f1e39d2b02a5061595d14c95452dc660148443310846ce4.png",
      "m image/png",
      "dim 864x1821",
      "service nip96"
    ],
    [
      "client",
      "Primal Web"
    ]
  ],
  "content": "An infographic of the Silent Payments flow (thanks, Codex!).\n\nWith Silent Payments, you get two additional properties:\n\n1. Verifiability - you can independently verify that the Silent  Payment address belongs to an npub (or NIP-05 address from a trusted provider)\n\n2. Deniability - only the npub owner (having the nsec) knows how to scan and identify transactions intended for sweeping/spending.\n\nOf course, this does not solve all the privacy issues related to downstream spending, but there is no way to implicate the npub or the sender of the funds. This is crucially important in high risk situations where the donor might be as at risk as the receiver.\n\nI have working code for all of this and am now testing various wallet implementations. More to come!\n\n#silentpayments\n\nhttps://blossom.primal.net/6ec9c49a31b748e98f1e39d2b02a5061595d14c95452dc660148443310846ce4.png ",
  "sig": "8b773d6d116fa7e1c1262b0409ad41e67c7c7b19dc91c7f937ed9b5e6e7af74bbf533a24ed58255af97e0cb97250b7a722a1bc33e4d2c1a96f6050cc84273b10"
}