armstrys on Nostr: To me it does beg the question if nip57 could use more generic naming. It seems like ...
To me it does beg the question if nip57 could use more generic naming. It seems like zaps and whatever we want to call this could follow a similar data flow over nostr and there might not be a point in having separate nips. Effectively zaps would just be the lightning implementation of nip57
Published at
2024-07-13 17:04:39Event JSON
{
"id": "d9b96c77080e2c17d793e820dd5906d16669f2c7b7312e4600a3662b3d5f124d",
"pubkey": "c80b5248fbe8f392bc3ba45091fb4e6e2b5872387601bf90f53992366b30d720",
"created_at": 1720890279,
"kind": 1,
"tags": [
[
"e",
"184b388443875d652f5600ce3bd877a2bdb2c49ee86efe83b72a2eb716e8eaca",
"",
"root"
],
[
"e",
"f0f89e44f7e3f2cfebd8e11a2c9b26c703e58986f84384112e530f4024a97022",
"",
"reply"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content": "To me it does beg the question if nip57 could use more generic naming. It seems like zaps and whatever we want to call this could follow a similar data flow over nostr and there might not be a point in having separate nips. Effectively zaps would just be the lightning implementation of nip57",
"sig": "45916de00cf0ffbd3da9ffe0642e2ceabc30e7a8f9dae59aab0854400b629701e609de03fc8589771d109204bcf2382a23545ff91eedf83e7e712662c58fee50"
}
