dtonon on Nostr: This proposal is quite similar to NIP-26, unfortunately it requires a huge update ...
This proposal is quite similar to NIP-26, unfortunately it requires a huge update from clients to track the correlation between keys, so it's not really backward compatible.
I also speculated about this problem:
https://github.com/nostr-protocol/nips/pull/1363Published at
2024-11-29 07:07:39Event JSON
{
"id": "a3f2489cf718f401926df4a1d9d66d8c12259dfb52a3af8b98751dfd8fa94aae",
"pubkey": "7bdef7be22dd8e59f4600e044aa53a1cf975a9dc7d27df5833bc77db784a5805",
"created_at": 1732864059,
"kind": 1,
"tags": [
[
"e",
"99d70f89c3702df8ee09f3746bda42d7fe5099321558fc6daeaf9d147e4a5e61",
"",
"root"
],
[
"p",
"45904b28ffe0e5cb9132f9a08e976ed7f0fc57d8387781ea9c80f256c412c1b4"
],
[
"r",
"https://github.com/nostr-protocol/nips/pull/1363"
]
],
"content": "This proposal is quite similar to NIP-26, unfortunately it requires a huge update from clients to track the correlation between keys, so it's not really backward compatible.\n\nI also speculated about this problem:\nhttps://github.com/nostr-protocol/nips/pull/1363",
"sig": "95c4bc114e04468492879fb697ae09e3e6ac3031d5539edd5c1496df652ea498e6dec43d76622d6b71f417c70d030bc0d30dce52719273b1f68dc679e4d585e0"
}
