inkan on Nostr: Sorry I've been sleeping through this discussion. So it's like you say, you don't ...

Sorry I've been sleeping through this discussion.

So it's like you say, you don't have to abandon your current npub if you don't want to. You can create a new master key and delegate down from it, through a delegation chain, to the npub you already use on nostr.

You then keep posting with your current npub exactly as before. After the delegation this npub doubles as your inkan signing key, so everything you create with it from then on gets attributed to the new master key. If your current npub is ever compromised, the master key can then revoke it and delegate to a new one. The identity attached to the master key survives the compromise.

Full disclosure, this construction needs to be done with the Inkan Management Utility (https://www.inkan.cc/settings/inkan-management-utility), and it takes a bit more care than just creating a completely new identity from scratch. You basically prepare a small text file with your current private key in hex and feed it to the utility, and ideally you do all of this on an airgapped system, since you're handling private key material. If you want to try it, let me know and I'm happy to write up the exact steps, including the format that's required for the input file.

And if you'd first just like to get a better idea of how inkan works before connecting it to your current npub, you can create a throwaway toy identity on inkan's homepage. Recording it on Ethereum costs a small gas fee, and the wizard has a menu where you can ask me to sponsor that tiny amount, which I'm usually happy to do for people who don't hold any Ether (and seem reasonably good-natured, at least as far as posting to the inkan relay goes). Creating one happens right in the browser and takes about five minutes, and the result is the same cryptographic object the Management Utility would produce, just made in an insecure location rather than on an airgapped machine.