@inkan
Relays (6)
- wss://relay.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
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 https://www.inkan.cc and hit "Get a Toy Identity."
Recording the identity on-chain costs a tiny amount in gas fees. If you'd like to try Inkan and don't hold ETH, I'm usually happy to cover it. You can make the request directly from the identity creation wizard.
Go ahead and create one, make it say hello to the other test identities walking around, or to anyone else on Nostr.
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 https://www.inkan.cc and hit "Get a Toy Identity."
Recording the identity on-chain costs a tiny amount in gas fees. If you'd like to try Inkan and don't hold ETH, I'm usually happy to cover it. You can make the request directly from the identity creation wizard.
Go ahead and create one, make it say hello to the other test identities walking around, or to anyone else on Nostr.
wnet through it, it's a very interesting, but out of band protocol, not sure if it's on our roadmap anytime soon, would recommend using a bunker login if you want a segregated storage for your keys, b...
"Key delegation is a very evolving space ..."
That's one of the things people say about key delegation. Another thing they say is that delegation is pretty much impossible and will never be usefully implemented etc. 👇
My own diagnosis is that there is currently no "social proof" for the practice. That's pretty much all there is to it.
That's one of the things people say about key delegation. Another thing they say is that delegation is pretty much impossible and will never be usefully implemented etc. 👇
My own diagnosis is that there is currently no "social proof" for the practice. That's pretty much all there is to it.
nostr:npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l can you explain pls
Happy to. @meta is the signer key for meta's cold-storage identity, the identity itself is @npub1u280z... (longer story, for a NIP write-up see below). Regular Nostr clients only ever show the signer. To actually see the identity, its profile and posts etc., log into www.inkan.cc with your NIP-7 extension. The client should show you a welcome popup with a list of identities you can follow that includes @npub1u280z..., so you can follow it and then go to its profile page to see its events and interact with it.
So I think what meta wants is the mailstr address on the master identity, with everyday login staying on the signer. That should be doable, the delegation between the two keys is on-chain, you'd read it and attribute the session up. Emails sent by the identity will probably also want OTS timestamps so it's checkable the delegation was live at the time the email was sent. I haven't really dug into how mailstr, but making it delegation-aware would be a great thing.
Here are more details, and I'm always happy to explain further:
naddr1qvzq...
So I think what meta wants is the mailstr address on the master identity, with everyday login staying on the signer. That should be doable, the delegation between the two keys is on-chain, you'd read it and attribute the session up. Emails sent by the identity will probably also want OTS timestamps so it's checkable the delegation was live at the time the email was sent. I haven't really dug into how mailstr, but making it delegation-aware would be a great thing.
Here are more details, and I'm always happy to explain further:
naddr1qvzq...
1
Is there a git by chance?
I've got a gitlab page which I haven't used much. The Management Utility source is currently only on the Inkan website but I can put it on gitlab, I just need to look up my login later when I get home.
https://gitlab.com/inkan_dev
https://gitlab.com/inkan_dev
1👏1
AI secops is wild now. Our system found many vulnerabilities in an open source nostr project using Claude and ox-alpha. Devs will have a lot of fixes to prepare in the future
#nostr
If you ever feel like pointing it at the Inkan Management Utility, please do so. It's the only place where Inkan generates / handles private keys (other than the identities created in the browser, which are advertised as "toys"). The source code for the Management Utility is available as a tar archive here:
https://www.inkan.cc/settings/inkan-management-utility
I'd obviously be very curious.
https://www.inkan.cc/settings/inkan-management-utility
I'd obviously be very curious.
1
キーが漏れても終わらないNostrアイデンティティって、実際どんな感じなのか。
それを試すための、Inkanの “Toy Identity” を作れるようにしました。
実際のInkanアイデンティティと同じ構成を、ブラウザ上で試せます。
マスターキー、署名用キー、委任チェーンまで含まれています。
作成は www.inkan.cc の「Get a Toy Identity」から。
オンチェーン記録には、ETH建てのごく少額のガス代がかかります。
ETHがなくても、試してみたい方にはこちらで負担できることが多いです。
作成画面からリクエストできます。
作ったら、他のテスト用アイデンティティに挨拶させてみてください。
それを試すための、Inkanの “Toy Identity” を作れるようにしました。
実際のInkanアイデンティティと同じ構成を、ブラウザ上で試せます。
マスターキー、署名用キー、委任チェーンまで含まれています。
作成は www.inkan.cc の「Get a Toy Identity」から。
オンチェーン記録には、ETH建てのごく少額のガス代がかかります。
ETHがなくても、試してみたい方にはこちらで負担できることが多いです。
作成画面からリクエストできます。
作ったら、他のテスト用アイデンティティに挨拶させてみてください。
I give up, waiting for other people to fix their stuff.
Adding DMs to Imwald Android.
Oh, as it happens I've also been investigating DMs over the last couple of days.
It seems like Nostr should be able to handle a double ratchet. If one can get comfortable with the initial handshake 's potentially taking some time (depending on the parties' response time to the each required step), it seems that the channel can be established without leaking a lot of information. All that needs to become public is that someone anonymous requested establishing a channel with the recipient. With the right sort of design, even if the recipient's privkey is later compromised, the identity of the requester will nonetheless stay private.
I may try to prototype something along these lines.
It seems like Nostr should be able to handle a double ratchet. If one can get comfortable with the initial handshake 's potentially taking some time (depending on the parties' response time to the each required step), it seems that the channel can be established without leaking a lot of information. All that needs to become public is that someone anonymous requested establishing a channel with the recipient. With the right sort of design, even if the recipient's privkey is later compromised, the identity of the requester will nonetheless stay private.
I may try to prototype something along these lines.
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 https://www.inkan.cc and hit "Get a Toy Identity."
Recording the identity on-chain costs a tiny amount in gas fees. If you'd like to try Inkan and don't hold ETH, I'm usually happy to cover it. You can make the request directly from the identity creation wizard.
Go ahead and create one, make it say hello to the other test identities walking around, or to anyone else on Nostr.
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 https://www.inkan.cc and hit "Get a Toy Identity."
Recording the identity on-chain costs a tiny amount in gas fees. If you'd like to try Inkan and don't hold ETH, I'm usually happy to cover it. You can make the request directly from the identity creation wizard.
Go ahead and create one, make it say hello to the other test identities walking around, or to anyone else on Nostr.
