So I’ve been thinking about the question “What if Nostr keys were revocable and replaceable?”
The thing I came up with is Inkan. I’ve now set up a lab bench for it at 
There are a few ways you can poke at it:
1. If you just go to and log in with NIP-07, you’ll get a very plain Nostr client. You should be able to read, post, follow people, etc. For posting you’ll need to add your own relays under Settings > Network, as the Inkan relay isn't wired in at this access level. The client is pretty basic, but if it works for you, feel free to use it.
2. Once you’re logged in, you’ll see an “Inkan Agent” status light in the top right. That’s the thing that drives the identity logic. By default this light will be red: you’re not on the allow-list. The key to understanding Inkan is to watch how the Agent behaves; if you’d like to get access, let me know and I’ll try to cycle people through a small temporary allow-list so the backend doesn’t melt.
3. If, after watching it, you’d like to run an experimental identity of your own, let me know. If there’s enough interest (and capacity), I’ll publish a short “how to”.
And if anything doesn’t work — broken site, can’t log in, can’t access the Agent, etc. — please tell me.
#nostrdev
Inkan
A user-friendly Nostr client for exploring relay feeds
Inkan
A user-friendly Nostr client for exploring relay feeds