N.KOJIRA.IO
Timeline

npub16xnpfx85k8w…

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l
"it means nothing without broader adoption"

The way I think of it, there's only upside and absolutely no downside to using it now, regardless of whether there's broader adoption.

The reason is that you can simply create an airgapped master key now and delegate down to your current regular nostr key.

Then you just go on using your current nostr key as usual, except you make sure that your events get OTS timestamped (for example by including the inkan relay in your write relays).

So then you just use your current nostr key as usual, you don't even notice that you're using inkan. But in the background, all your events are attributed to your master identity, and if you ever switch away from your current signer key to a new one, you simply redelegate at that point to the new key, so your events will keep getting attributed to your master key.

So your identity lives in the background, even if there are no clients (other than inkan) looking at it. Maybe in five years you decide to make your own client that can see the identity, and when you do so its history and activities from the last five years will be visible in that client.

The point is that these identities have a sort of objective existence, regardless of whether there are any clients around that look at them. You or anyone else can always make an identity and its history visible later if you want to.
"over engineering" would be one of those names it gets called by people who don't know anything about it. It's like people insisting that they don't need encrypted email etc.
People are pretty resistant to giving it a try. It involves a bit of learning / effort at the beginning. Also, it uses blockchains, Bitcoin for timestamping and Ethereum for recording delegation and revocation declarations. A lot of people around here *really* don't like the Ethereum part and won't touch it for that reason.

If you'd like to try it out, the easiest way to get started is to create a throwaway "toy identity" on the homepage at https://www.inkan.cc. There's an option to send me the identity creation transaction and I can pay the $0.15 or so in gas fees and record the identity on-chain.

I'm also always happy to answer questions about it.
You can delegate down to an existing key.

So the cold storage identity key would be new, but the delegatee key that does the everyday signing on behalf of the identity can be your current key.

For example, the key I'm currently using is the signer for a cold storage identity. So if this signer key gets compromised, my identity will revoke and replace it.

The easiest way to get a feeling for it is to make a throwaway "toy identity" on the inkan homepage from scratch. There's an option to send me the transaction to record it on-chain, I'm happy to pay the $0.15 gas fees for it. Once you have a better feel for how it works, you can then decide whether you want to create a more serious setup where you delegate down to your existing key (you can't do that from the "toy identity" wizard, you'd need to use the Inkan Management Utility that supports more bespoke configurations).

Also, by the way, you can meet some cold storage identities under the "Explore" tab in the nav bar at https://www.inkan.cc if you're curious.
Inkan has something called a "permanent invalidation" of a key. It's probably not exactly what you're thinking, but it it may be related. The nip draft below talks about it, among other things.


nostr:naddr1qvzqqqr4gupzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqyghwumn8ghj7mn0wd68ytnhd9hx2tcpz9mhxue69uhkummnw3ezumrpdejz7qpgvdhkcepdwd6x7unpvajj66tyv4h8g6t5d9jhxttxdaez6mn0wd68ytthffxkvd2k5hlk5l
I'm here for the method of authentication, which I guess is the tech. It's not just key pairs but key pairs + PKI, the second part being only inkan currently.

I do want to make money with it, if only to draw attention to it.

But regardless of that, I'll stick to this method of authenticating for as long as I use the internet at all and the math of public key cryptogaphy holds up.
There's also this option 👇


nevent1qvzqqqqqqyp…
Hi.