I'm not entirely against onchain zaps btw, but just wanna point out that silent payments don't have to be computationally intensive btw, since on-chain "zaps" are public anyway, the transaction and thus the receiving address can be public so the receiver won't have to scan at all.
Silent payments at least help us prevent address reuse.
One thing that bothers me is UTXO bloating. But well, nobody can stop anyone from doing anything.
redshift
npub1ft…redsh
2026-05-17 17:09:23 UTC
in reply to nevent1q…0d82
Author Public Key
npub1ftt05tgku25m2akgvw6v7aqy5ux5mseqcrzy05g26ml43xf74nyqsredshPublished at
2026-05-17 17:09:23 UTCEvent JSON
{
"id": "bccdab3953274836737c62046ea2d729d1b5593c4eb2aa14b9f4f2310783abc1",
"pubkey": "4ad6fa2d16e2a9b576c863b4cf7404a70d4dc320c0c447d10ad6ff58993eacc8",
"created_at": 1779037763,
"kind": 1,
"tags": [
[
"e",
"f34c834c27f005c4c0fb77f8059ba31aa1d74758f8b1595ad4fd7b6cec4d0a01",
"wss://nos.lol/",
"root",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
]
],
"content": "I'm not entirely against onchain zaps btw, but just wanna point out that silent payments don't have to be computationally intensive btw, since on-chain \"zaps\" are public anyway, the transaction and thus the receiving address can be public so the receiver won't have to scan at all. \n\nSilent payments at least help us prevent address reuse. \n\nOne thing that bothers me is UTXO bloating. But well, nobody can stop anyone from doing anything.",
"sig": "5e1d9cdb68e3c25db94cea39b8f1ce7779b082afa4b93d2963114d0206427a5f10459cdb0bde9476d8c5e509f46e3fae787fa64eb62cf57b458467ef48c5b5b7"
}