Event JSON
{
"id": "136024751fe98b8f8460adc4120f008a0bbc06aec9329bcd4673df4ab7dc8cae",
"pubkey": "fcf70a45cfa817eaa813b9ba8a375d713d3169f4a27f3dcac3d49112df67d37e",
"created_at": 1772185289,
"kind": 1,
"tags": [
[
"r",
"wss://nos.lol/"
],
[
"r",
"wss://nostr.mom/"
],
[
"r",
"wss://nostr.oxtr.dev/"
],
[
"r",
"wss://premium.primal.net/"
],
[
"r",
"wss://relay.primal.net/"
],
[
"r",
"wss://relay.nostr.net/"
],
[
"r",
"wss://relay.damus.io/"
],
[
"r",
"wss://relay.mostr.pub/"
],
[
"r",
"wss://bcast.girino.org/"
],
[
"r",
"wss://relay.snort.social/"
],
[
"r",
"wss://relay.coinos.io/"
],
[
"r",
"wss://relay.nos.social/"
],
[
"r",
"wss://offchain.pub/"
],
[
"r",
"wss://nostr-pub.wellorder.net/"
],
[
"r",
"wss://bostr.shop/"
]
],
"content": "Receiving in Lightning is not private; even with private channels, you can obtain the source tx depending on how the invoice was generated.\n\nBlinded Paths should be the de facto standard.\n\nBut there also comes a time when all this has a cost.\n\nSpark, ARK, Boltz, routing—in the end, it's more expensive to send through Lightning than on-chain.\n\nIt's a shame that no one is thinking about these things.\n\nIf you don't want to complicate things too much, the most compatible option is LNproxy for receiving, but it doesn't have much liquidity either.",
"sig": "2236ddeb04aaf08aa7d604ca0be6630982e52c1390e9dbf616ea404ba90b78b3f79e9bc79c6e92a086688814ebcb23377f812cac61b69b8de65ff3d2a4cef267"
}