Inkan enables you to revoke and replace key pairs when your private key has been lost or stolen. You can also perform periodic key rotations preemptively. You can do all this in a decentralized manner. That way Inkan gives you a permanent online identity that only you control, and that you can be confident you can keep over the long-term. For example 50 years. Inkan is open for testing and comment. Let me know if you'd like to try it out.

Inkan enables you to revoke and replace key pairs when your private key has been lost or stolen. You can also perform periodic key rotations preemptively. You can do all this in a decentralized manner. That way Inkan gives you a permanent online identity that only you control, and that you can be confident you can keep over the long-term. For example 50 years. Inkan is open for testing and comment. Let me know if you'd like to try it out.

There's two types of Nostr users. those who like social media and those who don't.

Has anyone thought about how to disseminate Opentimestamps OTS proof data attesting to Nostr events across the relay network? I've been trying to implement this such that OTS data is by default treated as trusted if it's signed by the same key as the reference event that is being attested to. The idea is that you are already trusting the pubkey that signs the reference event - if you didn't, you wouldn't be interested in the reference event (or its OTS data) at all. So if you see a purported OTS proof that's signed by the same key as the reference event, you can by default treat this as trusted without the need to perform a verification against what's recorded on Bitcoin. In that situation, the only time you need to perform an audit against Bitcoin is when there is some positive reason to suspect that the OTS data you were provided with is incorrect. #nostrdev #asknostr #OpenTimestamps