Say hello to Nstart, Nostr's onbarding tool!
Nstart aims to guide new users to Nostr offering a easy and no-nonsense onboarding wizard, with useful hints about the protocol and some really exclusive features:
- Easy local backup of your nsec or ncryptsec
- Email yourself your ncryptsec, as additional backup location
- Create a multi-signer bunker URL for Nostr Connect (more info below)
- Auto follow the contacts list of some old and trusted Nostr users
- Customize of contact suggestions, useful for onboarding friends & family
Try Nstart live at https://start.njump.me or watch the video below to understand how it works.
A note about the multi-signer bunker. This is really cool stuff made by nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6, that uses FROST to split your nsec in 3 (or more) and distribute each shard to an independent trusted remote signer. This will give you a bunker code that you can use to log in to many web, mobile and desktop apps without exposing your nsec. If you ever lose your bunker code, if the signers vanish from Earth, and it stops working, or if it gets stolen by a malware virus, you can use your nsec to create a new one and invalidate the old one.
More info and source code: https://github.com/dtonon/nstart
Enjoy it and send back any feedback!
https://chronicle.dtonon.com/77b9a397cbbcd63f3bfc78ff2b2c0607e4ffa698a1fad33ab4736593c8ad4f90.mp4
Thank you for working on this!
I wanted to try FROST but can't login with it, probably because I got a bunker string w/ promenade.fiatjaf.com as relay, and that relay requires auth to read, so subscription on replies gets CLOSED. Am I doing something wrong?
Ah ok, it's outdated ndk subscribing to wrong kind.
What client?
FROST bunker requires a little update: all bunker uris before had the user pubkey on them, so instead of calling get_public_key clients were just taking the pubkey from the uri; FROST bunker can't support that, it uses a different key for each user, not the actual user's key, so clients have to call the get_public_key method.
Yeah thanks, I know about that upgrade - just didn't get to that issue due to old ndk misbehavior. Now implementing it in nostr-login, thanks for the push.
Btw frost bunker can't do nip04/nip44 encryption/decryption, right?
Exactly, it is an inherent limitation.
Imho we put too much into that identity stuff. It makes onboarding unnecessarily difficult.
What do you mean?
What's the meaning of that characters?
Nice answer 😁 Anyway, if there should be accountable adaption, nostr needs different Auth. Nobody wants to share their secret with one or many service. I.e. a delegation signing key per service, created while onboarding, secured by passkey etc. Every other approach imho is distortion...
Bunkers have exactly this goal, they are revocable tokens used to sign events.
Thanks nostr:nprofile1qqs8hhhhhc3dmrje73squpz255ape7t448w86f7ltqemca7m0p99spgpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgmwaehxw309a3ksun0de5kxmr99ej8gmmwdahzucm0d5hsz8rhwden5te0vdhh2mn5wf5k2uewve5kzar2v9nzucm0d5hss3mr7u, and sorry that I was to lazy to read the complete thread. Than bunkers are great 😁
