Hey! How’s it going? I’m sharing some new ideas that came out of Sovereign Engineering (npub1s0v…rmq5) 6. They feel especially relevant given the recent news about compromised keys.
This is a new NIP for identity checkpoints. In simple terms, a checkpoint is a signed event that says: "this key is me at this moment" Over time, that checkpoint can gather evidence and attestations from other people, helping to maintain identity continuity.
https://github.com/nostr-protocol/nips/pull/2278
The idea is that anyone can create a checkpoint to show they control a key. Later, if something bad happens, like losing the key or having it compromised, they can publish a new checkpoint linked to the old one. That creates a lineage people can look at to decide whether the new identity claim seems legitimate or trustworthy.
When you combine this with OTS, social graphs, NIP-05, and other forms of evidence, you get a way to deal with identity recovery, which in decentralized networks like Nostr, is crucial since there is no central authority that can definitively say "this person kept their identity". The best we can do is evaluate the available evidence. This proposal is all about that
Alongside this, there is also a complementary Snapshots NIP, which lets users preserve a specific version of a replaceable event. That can strengthen the evidence and reduce some attack vectors.
https://github.com/nostr-protocol/nips/pull/2279
I’ll soon publish an app to help create, visualize, and use all of this. Hope you find it interesting.
#soveng #sec-6
Gzuuus
npub1gz…ea5ds
2026-03-21 18:48:31 UTC
Author Public Key
npub1gzuushllat7pet0ccv9yuhygvc8ldeyhrgxuwg744dn5khnpk3gs3ea5dsSeen on
wss://relay.damus.iowss://nos.lolwss://relay.nostr.netwss://lightning.redwss://relay.nostrcheck.mePublished at
2026-03-21 18:48:31 UTCEvent JSON
{
"id": "c9b6ab22f70dbdfe8ae3ea0a089f036fbd28ba9498ffa5c9e47cd38cab2ac997",
"pubkey": "40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451",
"created_at": 1774118911,
"kind": 1,
"tags": [
[
"t",
"soveng"
],
[
"t",
"sec"
],
[
"p",
"83d999a148625c3d2bb819af3064c0f6a12d7da88f68b2c69221f3a746171d19"
]
],
"content": "Hey! How’s it going? I’m sharing some new ideas that came out of nostr:npub1s0veng2gvfwr62acrxhnqexq76sj6ldg3a5t935jy8e6w3shr5vsnwrmq5 6. They feel especially relevant given the recent news about compromised keys.\n\nThis is a new NIP for identity checkpoints. In simple terms, a checkpoint is a signed event that says: \"this key is me at this moment\" Over time, that checkpoint can gather evidence and attestations from other people, helping to maintain identity continuity.\nhttps://github.com/nostr-protocol/nips/pull/2278\n\nThe idea is that anyone can create a checkpoint to show they control a key. Later, if something bad happens, like losing the key or having it compromised, they can publish a new checkpoint linked to the old one. That creates a lineage people can look at to decide whether the new identity claim seems legitimate or trustworthy.\n\nWhen you combine this with OTS, social graphs, NIP-05, and other forms of evidence, you get a way to deal with identity recovery, which in decentralized networks like Nostr, is crucial since there is no central authority that can definitively say \"this person kept their identity\". The best we can do is evaluate the available evidence. This proposal is all about that\n\nAlongside this, there is also a complementary Snapshots NIP, which lets users preserve a specific version of a replaceable event. That can strengthen the evidence and reduce some attack vectors.\nhttps://github.com/nostr-protocol/nips/pull/2279\nI’ll soon publish an app to help create, visualize, and use all of this. Hope you find it interesting.\n\n#soveng #sec-6",
"sig": "77233e658b60a28539d59957a3850c0adf172750930326308c049aa254dfa2f8b3b9244f3b75052570e10c313e7182491cd5c99b6eac514f721ee9cefe7befc9"
}