Fields like event id, sig, pubkey, p & e tags would be 50% smaller in binary vs utf-8 hex. Follow lists are currently quite large and their size would be basically cut in half.
But if we implemented NIP-114, we could save even 90% or more in bandwidth and some processing as well, depending on how many relays you connect to. Hoping to find some time for it again. https://github.com/nostr-protocol/nips/pull/1027
Martti Malmi /
npub1g5…3drvk
2024-10-05 19:18:25
in reply to nevent1q…rz7z
Author Public Key
npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvkPublished at
2024-10-05 19:18:25Event JSON
{
"id": "4fa1f9c50bd9669b393e7fc3511f02000d67338488a4c6a123768d64f7b829c3",
"pubkey": "4523be58d395b1b196a9b8c82b038b6895cb02b683d0c253a955068dba1facd0",
"created_at": 1728155905,
"kind": 1,
"tags": [
[
"q",
"aa9ccc0484ff5e2657e19a67d93de461a8625e396c9f83438e46f278fdb9b123"
],
[
"e",
"aa9ccc0484ff5e2657e19a67d93de461a8625e396c9f83438e46f278fdb9b123",
"",
"reply",
"e88a691e98d9987c964521dff60025f60700378a4879180dcbbb4a5027850411"
]
],
"content": "Fields like event id, sig, pubkey, p \u0026 e tags would be 50% smaller in binary vs utf-8 hex. Follow lists are currently quite large and their size would be basically cut in half.\n\nBut if we implemented NIP-114, we could save even 90% or more in bandwidth and some processing as well, depending on how many relays you connect to. Hoping to find some time for it again. https://github.com/nostr-protocol/nips/pull/1027",
"sig": "7494ecb7fd24bad97ed821a6b1e1448c6c4b8dffc051c9224e9ecb43500b38b73702f45e17eacb9c1e08cf80cf2987e254e2d79594cee6b3f88146f0d5207d4d"
}