Not being able to quickly and safely sign into another client or device is such a friction with Nostr. I really think it’s the most important problem to solve in the short and medium term. And I do *not* think remote signing with another device or running nsecbunker or having your phone find some trick to stay alive in the background to be a signer is the solution. They are clever and useful for some, but ultimately only a tiny, tiny minority will deal with those things.
I’ve thought for years we just need a key signing delegation. It’s the equivalent of session cookies online. The problem simply requires a robust and decentralized way to sync and share active “session keys” that can be safely and quickly revoked when needed.
I’m also not saying that’s an easy problem either. I’m simply saying I don’t see anyway we get the “web experience” but also the security of signed messages and not needing to trust the host or relay without it. I’d love to hear other ideas for it though. I’m working on what I described above right now though.
Login to reply
Replies (7)
Jumble, alexandria, yakihonne, grain, all have pomegranate login.
> I’ve thought for years we just need a key signing delegation. It’s the equivalent of session cookies online. The problem simply requires a robust and decentralized way to sync and share active “session keys” that can be safely and quickly revoked when needed.
This is an important distinction though. "Session cookie" concept is a widely different architecture that rely on a central authority that determines authentication. Provide a common credential in exchange an authorization material.
There is no authority here, which makes distribution of authorization material difficult and requires absolute consensus across the entire work - ish. We have some proposals, but even with my design with backward compatibility, it only works if _every_ client implements it.
Let me brake down your statement. As if it was simple, we would have just done it.
1) sync and share active “session keys”. Just any event just just be signed and published. Cool so you sign a "session" or "delegation" event with your "root" identity. Your identity has been delegated iff this event is respected by clients, and relays... relay the event. How does a client know that the delegated event signed by your "session" key is "real" or can be trusted. Discovery becomes difficult but solvable but again must achieve total consensus for it to work at all.
2) safely and quickly revoked when needed.
This cannot happen efficiently, and most proposals don't respect the idea of revocation. What happens in the absense of the revocation? Nostr does NOT guarantee consistency with respect to time. So if the session is revoked, what if the revocation hasn't made it to the user yet?
3) These session keys must be treated as nearly ephemeral data, for security reasons, otherwise stale links to session tokens could cause a split. Requiring _every_ client churn it's cache all the time waiting for a possible revocation.
> I don’t see anyway we get the “web experience” but also the security of signed messages and not needing to trust the host or relay without it. I’d love to hear other ideas for it though. I’m working on what I described above right now though.
Correct. We simply cannot _have_ the web experience in a decentralized way. That's due to architecture, the web experience is only available now because all data is stored by the central authority on their servers, you have absolutely no responsibility to store anything yourself, you assume the server's got it.
The server owners bear
1) Managing your identity and other site information on their literal hard drives
2 Guarding your identity from your own mistakes.
Nostr _cannot_ do either of those things. Bitcoin cannot do either of those things.
There's no reason nor benefit for having an entire altcoin network running its own internal/circular security incentive structure just to have a list of keys or names for something. This could just as easily be done on bitcoin if all you needed was a hash of the canonical truth published somewhere reliable. But even then I still don't think that makes much sense.
Having an entirely separate blockchain for this, however, is like trying to use an excavator to carve a tiny wooden figurine. It's just not the tool for the job no matter how many individual pieces of it seem like they are relevant or similar. You don't need (or want) global consensus on all accounts and all keys and all networks. You want individual control and reliable syncing of state among those that care.
💯 the infrastructure is here now, just needs adoption.
💯 If a client can read the nsec it can lose it. The fix is keeping your nsec somewhere it can only sign hashes, with each app getting its own permission you can revoke. A bunker app gets part way but it's still an app living inside an OS that can read it, kill it or replace it. That's not your key, it's Google's. The real fix is hardware. Everyone already has a router and a hub humming away at home. One more box that holds your nsec and only ever says yes or no is not the burden people think.
i only just saw this and i totally disagree. 60% of btc mining pools also disagree. satoshi literally said keep this separate from bitcoin. I could argue but I think you need your domains stolen to actually understand.