I say this because I just went to desktop to post a video and realized I wasn’t signed in and then decided it wasn’t worth it and went on to other work. I don’t have my nsec just lying around because I value the account and network… but because of that using this on all of my devices is both a pain and also unsafe to break out my private keys and copy paste them in a bunch of apps and web browsers. View quoted note →

Replies (12)

So I guess you considered #Frost if you have been thinking about this for a long time but you haven't mentioned it. Why? Key rotation on the nsec level will hardly be a thing unless there's some cryptographic breakthrough because it would centralize the protocol, see PLC in atprotocol and such. You basically must centralize key lineage tracking to a trusted party but that just doesn't go well in a distributed system. Frost shard-based signing UX can be very stable and fairly revocable, it's just not yet spread so much. Social rotation is the other way, it's been talked about many times. It is a viable alternative in a network like nostr, especially if communities get more popular. The reason why there's not too much anxiety over this is just the fact that there's not yet enough demand I think for nostr in general. We're building things out and if there's real pressure in the future from economically relevant users accruing, at some point it's gonna be figured out.
I’m not talking about key rotation. When I say delegation I mean “signing to approve other keys” so that client keys are ephemeral and specific to the client. In other words, my Nostr key only posts a list of attestation that say “these 10 keys are all me” same as I log into websites and say “these sessions are all mine” using cookies and account credentials. I’m not saying that’s foolproof or not without trade offs. As I said, I’m happy to hear about alternatives and don’t know why you jumped to “why are you ignoring Frost” like I’m aware there is some perfect solution and pretending it doesn’t exist on purpose. Specifically regarding frost, I’ve only loosely investigated it and how it could work with this UX issue. I thought of it as a different purpose tool but I think Max mentioned the same thing to me at one point but I haven’t had the time to get deep into it
And on the note of key delegation: Hyperbee seems the perfect fit and that’s what I’ve been exploring as the append only state for “signed in devices” if you will.
I'm not looking for a solution *for me.* I'm looking for a general solution to make the UX feel like the "sign in with apple" option and retain the general security and isolation of your core account keys. My own remote signer works fine, I'm just never going to get my mom to do that.
Thanks very much for flagging this. I checked just now and the cert is valid covering both inkan.cc and www.inkan.cc, and I haven't had this report from anyone else. It's likely something between your phone and the site. You may want to try in your regular browser and see if that fixes it. If it doesn't, please let me know.
The problem with append only state is that remember: From the other partie's perspective who only sees your signed event, delegated signing is key rotation. For your idea to work you must (as you mention) introduce an append only tracker of your key states. This is the exact point where you introduce a strict ordering burden on Nostr verification since now everyone must take a roundtrip: "Do I know this key? This could be xyz's subkey/delegated key so let's look up the original to verify the real identity" and this must be done each event. And if you leak the subkey it's even worse, now you have to introduce even more extra roundtrips and edge cases where a client must look up the history of revocations with each and every event verification process. So a delegation process producing a different signature will not work practically in my opinion. The delegated signing process must produce the same signature as the original key. This is what FROST solves. Your nsec is sharded and you define in the key ceremony what kind of quorum you will use. Let's say 2/3. Now you keep one on a server, one on your phone and one just in cold storage (for now). If the server or the phone is compromised you get the 3rd shard and never trust the compromised one again. These tools exist already you can experiment with them. The burden / complexity is now on you instead of the whole network to make sure that the compromised shard is being handled (you cannot revoke it) but realistically you can drop it, and use the other 2 or even add further keys to the quorum, making it practically 2 of 4 etc. Note that adapter signatures could be used differently but Frost has additional benefits. AtProto (Bluesky) solves this by introducing a trusted so called PLC server that tracks key rotations. You cannot practically run your own equivalent because that's hardcoded into each client solving the consistency / roundtrip problem I described above. It's that theoretical thing that doesn't work in practice, and they acknowledge that. All in all UX can go a long way so a co-signer FROST setup can be quite convenient to use with the right tooling, and services. And if all breaks we always fall back to meatspace, there will never be a perfect solution, that's alright I think. Bitcoin can be hardforked even with overwhelming consensus. Note that key rotation is essentially just that: You want the whole world to overwhelmingly accept that the state of your identity changed. That is an oracle problem and Bitcoin handles it the same way: Leaves it open. That's why altcoins exist. You fork an identity that's your alt identity. I don't have to accept but I cannot exclude others to accept it and enforce it practically. The difference is that rotation of your identity will not affects global trade so it will be alright.
By the way you can create a sign in with google experience today with frost fiatjaf had a demo I think. You can run a bunker signer for your mom, or later when ppl have much at stake there will be professional co-signing services.
↑