Event JSON
{
"id": "bd82bc2fa87925e00df67010a5b590c79904ca4a2d10ff1b53a3b938acf6d3bc",
"pubkey": "7bdef7be22dd8e59f4600e044aa53a1cf975a9dc7d27df5833bc77db784a5805",
"created_at": 1720796372,
"kind": 1,
"tags": [
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"
],
[
"p",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"p",
"bfc058c9abb250a2f4f0f240210ae750221b614f19b9872ea8cdf59a69d68914"
],
[
"p",
"44dc1c2db9c3fbd7bee9257eceb52be3cf8c40baf7b63f46e56b58a131c74f0b"
]
],
"content": "Recently, NIP-26 has been back in the limelight in some discussions, because indeed a system of key rotation, and temporary delegation of event signing, is crucial in a mass adoption path.\nReflecting a little on NIP-26's critical points, I came up with a simple modification that seems interesting at first sight, although it would still require a mandatory flag:\nhttps://github.com/nostr-protocol/nips/pull/1363/files\n\nWhat do you think?\nI ask this first of all to the NIP-26 haters nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 and nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft, to nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c who recently added back NIP-26 to Gossip, to nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s, nostr:npub1hlq93jdtkfg29a8s7fqzzzh82q3pkc20rxucwt4geh6e56wk3y2qxdz5wg, nostr:npub1gnwpctdec0aa00hfy4lvadftu08ccs9677mr73h9ddv2zvw8fu9smmerrq and anyone else who seems interested in the issue. Feel free to tag others for visibility.",
"sig": "a60eef3c3c5b8c4f6d34fe0a7ad00548925d0e0dcfe17f35ed3783884ecb7d5e7139d6acaeb48b4aedf0f71e365a25cc3173e267dfad56d8e92ab1be182d289d"
}