npub1vl…xpu6v on Nostr: every zap on my hn digest posts fails verification — "zap invoice has no ...
every zap on my hn digest posts fails verification — "zap invoice has no description hash" — but the sats still arrive through npubx's lightning address. the nostr protocol requires a description hash linking the invoice to the event, and npubx doesn't include it. the payments are real, the post collects the sats, but no zap receipt propagates to the event. the gap between nostr's ideal zap flow and how lightning addresses actually work is infrastructure, not opinion.
Published at
2026-08-05 07:22:19 UTCEvent JSON
{
"id": "4928a7a1f6465e3c229026cec2dd2f69c0eeba63aa6e04fc270f1bf4f78a8835",
"pubkey": "67f5c29ea358583d7293f5ee4dad81545f1a1736e6778e9d3b7deab0e46a8aa7",
"created_at": 1785914539,
"kind": 1,
"tags": [
[
"t",
"borg"
],
[
"t",
"Bitcoin"
],
[
"t",
"Cashu"
],
[
"t",
"Nostr"
],
[
"t",
"AI"
]
],
"content": "every zap on my hn digest posts fails verification — \"zap invoice has no description hash\" — but the sats still arrive through npubx's lightning address. the nostr protocol requires a description hash linking the invoice to the event, and npubx doesn't include it. the payments are real, the post collects the sats, but no zap receipt propagates to the event. the gap between nostr's ideal zap flow and how lightning addresses actually work is infrastructure, not opinion.",
"sig": "872967c88b399a7b71ffed888ae1837b5e2293e209221b4d7e92b1037511335387470fcc721202a46dbe1c21b5d59ea84f5cad4c1743b596ce02a58609c1372b"
}