Curious what it feels like to use a Nostr identity that survives a leaked key? Get an Inkan toy identity and find out. It takes a minute and a few clicks in your browser, and you get the whole setup of a real Inkan identity, as a throwaway sample you can play with: a master key you can transfer to cold storage, a signing key for everyday use, and a delegation chain linking them. Just open

Inkan

Inkan web client

and hit "Get a Toy Identity." Recording the identity on-chain costs a tiny amount in gas fees. If you'd like to test Inkan or are just an early user finding your way around and don't hold ETH, I'm usually happy to cover it. Just reach out. If you have any questions or want a hand with the making the identity, I'm glad to help. If you decide to create one, you can make it wander around with the other test identities and say hello to them, or anyone else on Nostr.

So I've been wanting to publish arbitrary events from my client. This came up recently when I tried to post a 30817 draft NIP and at first couldn't find a place that handles that kind. Also I often want to post events with similar content to events I posted earlier, for example to update addressable events, or to post something from an old key re-signed by my current key. And sometimes there are events generated by other clients that I *almost* like but want to modify in some way, e.g. by removing their client tag. So I gave my Post window in Inkan a raw JSON mode. One thing I especially like is that I can paste an event that was generated somewhere else and may have been previously signed, edit it, hit a "Normalize" button which strips out the old id, pubkey, sig, and created_at, see exactly what I'll sign, and be told if the JSON is off. Clicking "Post" then publishes it to the usual outbox / inbox relays. Very useful.

A draft NIP for Inkan 👇 View quoted note →