@inkan
Relays (6)
- wss://relay2.inkan.cc/ – read & write
- wss://nostr.wine/ – read & write
- wss://nostr.land/ – read & write
- wss://relay.primal.net/ – read & write
- wss://relay.damus.io/ – read & write
- wss://nos.lol/ – read & write
Recent Notes
The way it usually goes, your online identity is your private key. If the key is compromised, there goes your identity. Inkan fixes that.
You keep a master key in cold storage and a signing key for everyday use. If the signing key ever leaks or gets lost, the master revokes it and delegates to a new one. Same identity, same followers, fresh signing key.
If you'd like to take a look at the prototype: https://www.inkan.cc. Log in with your NIP-07 extension and say hi to the test identities already walking around. Or make one of your own.
You keep a master key in cold storage and a signing key for everyday use. If the signing key ever leaks or gets lost, the master revokes it and delegates to a new one. Same identity, same followers, fresh signing key.
If you'd like to take a look at the prototype: https://www.inkan.cc. Log in with your NIP-07 extension and say hi to the test identities already walking around. Or make one of your own.
We need relays to have the ability to (i) verify OTS proofs, (ii) pick the best OTS proof they know about for a given reference event and (iii) splice that OTS proof into the reference event's json when returning the reference event.
This is a crucial piece of Nostr infrastructure. Delivery of events with both "created_at" and "ots" should be a standard option.
Here's an example of the shape, created by an experimental OTS-enabled relay:
{
"content": "Hey everyone.",
"created_at": 1779496582,
"id": "df2ab2b13de7b5c3b2b19c5f2d9a1a62bdd21187bab80ae9ca714657072514c5",
"kind": 1,
"pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
"sig": "136fa9ba91cc6353272a61c68b31dc32b66a3feeaf59e2b30d0c65231f62da8e62e4b2c471ef7716d94dbf2b96298922d94b6c6e54ae9d0e666d67c8bfdee8d5",
"tags": [],
"ots": {
"h": 950594,
"p": "AE9wZW5UaW1lc3RhbXBzAABQcm9vZgC/ieLohOiSlAEIWtcyBdiiH7GgEGoVRJIPc8DNzH7Z7RGtcg6/WpOJu1XwEA9v9HhTutucWA7w/ZGI2rcI8SAkKVNfWvH7gSKhnU/4vWIcLP2W6btnzaa3T0wET85tRAjwCASjHfEtZbrRCPAgkYRpMxK4g+/ZR2JyajbUpE/bsnvbL0xtp6yrjfIYQ+wI8BDAkdv1ZGZ+GAUJTUZ4qMRGCPAgS+QKBUJvUlLdCyvzMjLIqvLBBD3IoepiUmesn0mCNBMI8SAvI0Tf0k7vqLFDvIpe/UxZnQ7A5gwRkBUrF4ADZXiSNwjxBGoQ99zwCKolI080wUr+/wCD3+MNLvkMji4taHR0cHM6Ly9hbGljZS5idGMuY2FsZW5kYXIub3BlbnRpbWVzdGFtcHMub3JnCPEg/LQtTT8/+hqvCjHDGJ0mGXUyc8LrZgX9mlcbYpCE+kEI8SCtEFZWx6cNO0PhjLt+BhP5DqidihwBVhC3OYnWlE+GPwjwIEgz2gko9lK+h0ZnoKuCjME/UHskf9lSUD/X6vjqRXv7CPAgrRZwdXUYkcyXDJMPNrCXJUWOoOQrMtpls/k1N3oxp94I8CCfrdfZIQzyMswLsgUsUt6QAVIcLik8C6yBM9fMzj1i/QjxINlK6TBQpbHnLv2HjII4Xdnd7k44/spKcEozde0v/N22CPEguvGUeBCbEZi5mNym3ZBoMLYASs/qCTVzLzlt1lNgrEwI8SDFnrOH6S4wgampdkN+e/Nz68PkJiK4JKFEGhLnLlwOaQjxWQEAAAABd4ZxqpDBqGv1QVKo6a4h5OXyPsPZ+D7weiCvVQ8v1XsAAAAAAP7///8Cqm4AAAAAAAAWABTaRzyppy+5BvgYq1tTpSQA8+AUvwAAAAAAAAAAImog8ARBgQ4ACAjxIHUy9sLWy1kmFI7f6BIR8BC7vnr/z4BEVkfH0muJfJ2uCAjwIICmK+vIFKKIy/Hg8JOW/lQypJKJHwucYcNbr1JgSJydCAjwIId1d0xIdJa1a0zF9jMhDIghiov/957z7joB1Ml50J6rCAjwIEg363fprj/h/lBFOAu+oS5co1kmG+Vhj573jQznGTyZCAjxIIJTlHqo80FnmaYF3Jqe5wH5kkj8Q/kKTLn6xpB1wIO3CAjwINnw6Re4rCLlpKqDUfTci5q6gaxab3speYUOx3k1VqRMCAjwINT6RN9HA26lxlNWJqROea01L446Q6gN3G4Uj39/5E0iCAjxIHRcQlP6ix2DkV1BGcNNTiaqFWpJAp33gPBaNS/HrVzMCAjxIFtlzHfZmba11h0sqrDNmDAdUBJtXi/6A2pCzlprbuTJCAjwIGC3ZjfSFYdOHLbvI31/Qs88VqeAdbUxh4PR/T+I6MujCAjwIGu1SRrtLU+7cE79nEUkriJIvmaPV5gxkJIf5J9BribNCAjwIEAgQnKgE8QemGxL7IGZpLFXhGEFEMpv4fmmxvbFprUkCAjwICURMvkug3WVivpumgXFYGpLZnECEFmRm+DQsV9W8Ac1CAgABYiWDXPXGQEDwoI6",
"st": "complete",
"v": 3
}
#nostrdev
#ots
#opentimestamps
This is a crucial piece of Nostr infrastructure. Delivery of events with both "created_at" and "ots" should be a standard option.
Here's an example of the shape, created by an experimental OTS-enabled relay:
{
"content": "Hey everyone.",
"created_at": 1779496582,
"id": "df2ab2b13de7b5c3b2b19c5f2d9a1a62bdd21187bab80ae9ca714657072514c5",
"kind": 1,
"pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
"sig": "136fa9ba91cc6353272a61c68b31dc32b66a3feeaf59e2b30d0c65231f62da8e62e4b2c471ef7716d94dbf2b96298922d94b6c6e54ae9d0e666d67c8bfdee8d5",
"tags": [],
"ots": {
"h": 950594,
"p": "AE9wZW5UaW1lc3RhbXBzAABQcm9vZgC/ieLohOiSlAEIWtcyBdiiH7GgEGoVRJIPc8DNzH7Z7RGtcg6/WpOJu1XwEA9v9HhTutucWA7w/ZGI2rcI8SAkKVNfWvH7gSKhnU/4vWIcLP2W6btnzaa3T0wET85tRAjwCASjHfEtZbrRCPAgkYRpMxK4g+/ZR2JyajbUpE/bsnvbL0xtp6yrjfIYQ+wI8BDAkdv1ZGZ+GAUJTUZ4qMRGCPAgS+QKBUJvUlLdCyvzMjLIqvLBBD3IoepiUmesn0mCNBMI8SAvI0Tf0k7vqLFDvIpe/UxZnQ7A5gwRkBUrF4ADZXiSNwjxBGoQ99zwCKolI080wUr+/wCD3+MNLvkMji4taHR0cHM6Ly9hbGljZS5idGMuY2FsZW5kYXIub3BlbnRpbWVzdGFtcHMub3JnCPEg/LQtTT8/+hqvCjHDGJ0mGXUyc8LrZgX9mlcbYpCE+kEI8SCtEFZWx6cNO0PhjLt+BhP5DqidihwBVhC3OYnWlE+GPwjwIEgz2gko9lK+h0ZnoKuCjME/UHskf9lSUD/X6vjqRXv7CPAgrRZwdXUYkcyXDJMPNrCXJUWOoOQrMtpls/k1N3oxp94I8CCfrdfZIQzyMswLsgUsUt6QAVIcLik8C6yBM9fMzj1i/QjxINlK6TBQpbHnLv2HjII4Xdnd7k44/spKcEozde0v/N22CPEguvGUeBCbEZi5mNym3ZBoMLYASs/qCTVzLzlt1lNgrEwI8SDFnrOH6S4wgampdkN+e/Nz68PkJiK4JKFEGhLnLlwOaQjxWQEAAAABd4ZxqpDBqGv1QVKo6a4h5OXyPsPZ+D7weiCvVQ8v1XsAAAAAAP7///8Cqm4AAAAAAAAWABTaRzyppy+5BvgYq1tTpSQA8+AUvwAAAAAAAAAAImog8ARBgQ4ACAjxIHUy9sLWy1kmFI7f6BIR8BC7vnr/z4BEVkfH0muJfJ2uCAjwIICmK+vIFKKIy/Hg8JOW/lQypJKJHwucYcNbr1JgSJydCAjwIId1d0xIdJa1a0zF9jMhDIghiov/957z7joB1Ml50J6rCAjwIEg363fprj/h/lBFOAu+oS5co1kmG+Vhj573jQznGTyZCAjxIIJTlHqo80FnmaYF3Jqe5wH5kkj8Q/kKTLn6xpB1wIO3CAjwINnw6Re4rCLlpKqDUfTci5q6gaxab3speYUOx3k1VqRMCAjwINT6RN9HA26lxlNWJqROea01L446Q6gN3G4Uj39/5E0iCAjxIHRcQlP6ix2DkV1BGcNNTiaqFWpJAp33gPBaNS/HrVzMCAjxIFtlzHfZmba11h0sqrDNmDAdUBJtXi/6A2pCzlprbuTJCAjwIGC3ZjfSFYdOHLbvI31/Qs88VqeAdbUxh4PR/T+I6MujCAjwIGu1SRrtLU+7cE79nEUkriJIvmaPV5gxkJIf5J9BribNCAjwIEAgQnKgE8QemGxL7IGZpLFXhGEFEMpv4fmmxvbFprUkCAjwICURMvkug3WVivpumgXFYGpLZnECEFmRm+DQsV9W8Ac1CAgABYiWDXPXGQEDwoI6",
"st": "complete",
"v": 3
}
#nostrdev
#ots
#opentimestamps
Nostr is a protocol for distributing digitally signed content.
The primitives on which it is build closely trace the elements of public key cryptography. It's unlikely that these are going to change.
So Nostr is not just some fad or fashion. Whether it's popular or a lot of people use it is in a way secondary. It's the correct way to authenticate on the internet, and that's all that matters to my decision to use it.
The primitives on which it is build closely trace the elements of public key cryptography. It's unlikely that these are going to change.
So Nostr is not just some fad or fashion. Whether it's popular or a lot of people use it is in a way secondary. It's the correct way to authenticate on the internet, and that's all that matters to my decision to use it.
No more allow list!
You can now simply use NIP-7 to log in at https://www.inkan.cc and start interacting with the test identities.
This is for anyone who's interested in having revocable / replaceable keys.
You can now simply use NIP-7 to log in at https://www.inkan.cc and start interacting with the test identities.
This is for anyone who's interested in having revocable / replaceable keys.
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.
Inkan is open for testing and comment. Let me know if you'd like to try it out.
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.
Inkan is open for testing and comment. Let me know if you'd like to try it out.
This is Markus. And that's my pubkey:
0x047f2c82d6cc1b2d500071a9d426e6c9873ae51a9a774e52ee61b180e49bfa6fecfb9d108e7d0595c1adeea23cf41dfbd069b654310e57e4f82e533c934020a333
0x047f2c82d6cc1b2d500071a9d426e6c9873ae51a9a774e52ee61b180e49bfa6fecfb9d108e7d0595c1adeea23cf41dfbd069b654310e57e4f82e533c934020a333
Hey everyone.
My mac is dead right now so I’ll have to wait for a browser/iOS solution (or get a job) but thanks 🙏
Yes, I've been thinking about making in-browser construction of identities available as an option. There is nothing difficult about it in principle, but it sort of defeats the purpose of keeping the identity-securing keys airgapped. I may still decide to do so as a sort of toy-identity option so it becomes very easy to try it out. I first want to fortify the surrounding infrastructure, so it's more scaleable before I roll out an-easy-to-try option.
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.
Inkan is open for testing and comment. Let me know if you'd like to try it out.
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.
Inkan is open for testing and comment. Let me know if you'd like to try it out.