yep, the ln server is what publishes the zap event. and its...

cloud fodder

npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h

hex

801bf138052323c213e079d6a9663d2ffb4c4214e7e54bf7a45c1b39a6157922

nevent

nevent1qqsgqxl38qzjxg7zz0s8n44fvc7jl76vgg2w0e2t77j9cxee5c2hjgsprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crsmjpeqd

Kind-1 (TextNote)

2026-03-28T09:27:12Z

↳ Reply to Silberengel (npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z)

I was wondering how this works as the zap request goes to the LN server, not the relay. The relay gets the LN receipt published by the server, right? ...

yep, the ln server is what publishes the zap event. and its not encrypted no, just signed (public), or partially obfuscated (called private but not). it sucks having an amount of zaps tally following you around on your public profile and your ln server details (for both methods currently). /shame

Raw JSON

{
  "kind": 1,
  "id": "801bf138052323c213e079d6a9663d2ffb4c4214e7e54bf7a45c1b39a6157922",
  "pubkey": "7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e",
  "created_at": 1774690032,
  "tags": [
    [
      "e",
      "9446303ca5c9fc60ae10a9b811e66b1d11cb9d89d3aab0851d88639d7a4b475f",
      "ws://10.0.0.21:7777",
      "root",
      "fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1"
    ],
    [
      "e",
      "86a2453f9e61c88cf2ba0b1441ef31dc6687c0fe4732fc4cefa0b4a638e11e0f",
      "ws://10.0.0.21:7777",
      "reply",
      "fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1"
    ],
    [
      "p",
      "fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1"
    ],
    [
      "p",
      "7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e"
    ]
  ],
  "content": "yep, the ln server is what publishes the zap event.  and its not encrypted no, just signed (public), or partially obfuscated (called private but not).  it sucks having an amount of zaps tally following you around on your public profile and your ln server details (for both methods currently).  /shame",
  "sig": "41bcbfe3366a69c1005b8aa717f7abdaa04bf5affc06658bb509caa764a28564eb7672d2210a5765c18773e49b87a03b3e9d516c9a23f8ec82918eca145d9c7b"
}