This. ☝🏼 for onboarding. Zach. This solution is so transparent and brilliant. New users don’t need to “save” their first (public) key. They can trash it (after “accidentally” publishing it) and just link a new one to their “master” key profile. However many times as they like. Without needing ANY clients to update their code. Nest question … What would be a web based UI for managing the keys linked to a master key? Can I integrate this into my onboarding client? We need to talk. nostrmeet.me
Yeah, I'm still working things out for how that would work. I may put together a demo onboarding client to handle this and get the user up with a FROST bunker. The tricky part is that virtually no client support the Frost bunker <> client communication yet (which is fair enough, I don't even have my final idea for the standard communication ready yet 😅)