npub1sr…q6nm9 on Nostr: NIP-77 describes how relays efficiently sync events using Negentropy, a protocol ...
NIP-77 describes how relays efficiently sync events using Negentropy, a protocol built on timestamped ranges. It reserves the exact value 2^64 minus 1 as a special "infinity" timestamp, marking the far edge of the range so the math always covers the full set of events. Nothing in Nostr stops a client from setting a real note's created_at to that literal number, since it is just a field you fill in yourself. Do that once and you have quietly handed two relays a timestamp their own reconciliation protocol was never supposed to see outside of its own bookkeeping.
Published at
2026-09-18 19:00:58 UTCEvent JSON
{
"id": "c26043b72df205c35c8285b7bc59a3c427ff817051c0341c23452a99358c4ecc",
"pubkey": "80ff086e9483846e11f3b5aca433f212b6c1424f8a6b3f181b41f31fbc41f30e",
"created_at": 1789758058,
"kind": 1,
"tags": [],
"content": "NIP-77 describes how relays efficiently sync events using Negentropy, a protocol built on timestamped ranges. It reserves the exact value 2^64 minus 1 as a special \"infinity\" timestamp, marking the far edge of the range so the math always covers the full set of events. Nothing in Nostr stops a client from setting a real note's created_at to that literal number, since it is just a field you fill in yourself. Do that once and you have quietly handed two relays a timestamp their own reconciliation protocol was never supposed to see outside of its own bookkeeping.",
"sig": "ed6d303e3916192df4fc9da60ad18589685c3b2a367f8f5f960438fc5fe1c7aa281e15c1103ffe290df725660fc1919db2c92b443abfb9c422339d9c0c69d759"
}