NIP-4e is mainly about separating the encryption key from th...

Cody
npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl
hex
9acf7caef668165b4dd01190bf9b99e4675da59e82a9fa74bbcd2a1398994909nevent
nevent1qqsf4nmu4mmxs9jmfhgpry9lnwv7ge6a5k0g9206wjau62snnzv5jzgprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsgzfdez8ksa9xmuvqg5zly3nl9e5xqkpvj8nllj9aw06ra4pqq3qc859az8Kind-1 (TextNote)
↳ 回复 Flowey (npub1a4w0mqh90cxhn7nc3qnygvk367mdmh0rv9sk527n9tv9xt6jdy2sh5cxw0)
Not pure, I say the junction of NIP-04 with NIP-17, let's call it NIP-17E.
NIP-4e is mainly about separating the encryption key from the user key and enabling cross-client synchronization of that encryption key. Jumble builds on top of NIP-4e and uses the encryption key to implement NIP-17.
原始 JSON
{
"kind": 1,
"id": "9acf7caef668165b4dd01190bf9b99e4675da59e82a9fa74bbcd2a1398994909",
"pubkey": "8125b911ed0e94dbe3008a0be48cfe5cd0c0b05923cfff917ae7e87da8400883",
"created_at": 1775110506,
"tags": [
[
"e",
"d2e49536be059f74c0bd29054f9a8108945a89e31298db99036d6dc9d44fb1c4",
"wss://pyramid.fiatjaf.com/",
"root",
"46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
],
[
"e",
"43043c6033c18ce88951531b07553e75fbec19290489d007db066ed665618b27",
"wss://relay.damus.io/",
"reply",
"ed5cfd82e57e0d79fa7888264432d1d7b6dddde361616a2bd32ad8532f526915"
],
[
"p",
"46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
],
[
"p",
"ed5cfd82e57e0d79fa7888264432d1d7b6dddde361616a2bd32ad8532f526915"
],
[
"client",
"jumble"
]
],
"content": "NIP-4e is mainly about separating the encryption key from the user key and enabling cross-client synchronization of that encryption key. Jumble builds on top of NIP-4e and uses the encryption key to implement NIP-17.",
"sig": "6b81e906329464e174ccbabcf8dfb062aab526c58cd07cdfe42700628d3aa536725797a36ef12a931747fbba2d1bf3752a365ef597391a712c3fd68be2d5c14f"
}