email: ______ phone: ______ DOB: ______ gender: ______ country: ______ ID: ______ [ ] agree to ToS [ ] allow tracking [ ] sell my soul [ SIGN UP ] Nostr ▸ create keypair ▸ add username [ DONE ] ☻

Replies (11)

As long as social clients are “Creating Keypairs” … they can be rugged for age verification. Best bet is for dedicated key managers (like separate apps or browser extensions or remote signers) to handle this. For new new (virgin) accounts, social clients can “suggest” a third party remote signer and forward keygen to there. (with an updated NIP-46 spec for redirecting back to the requesting client)