Due to the various flows that take you to the 'create checkbook' page it is possible to get their without an email or to try and use an email which is already 'taken'. For now we just want to do the simplest thing and prevent these 'lost souls' from trying to create another account. (We could create another key/pair and account but that would get confusing hella fast so we'll skip for now).
[ ] If anon attempts to register an email address but that address is already registered (and verified) to an email user they get redirected to a gentle, friendly error message, indicating that they really need to find that login button in their email or else they are SOL
[ ] If anon attempts to register an email address but that address is already registered (and verified) to an web3 user they see a message indicating that they need to connect their wallet first (data they entered already is lost).
[ ] If anon attempts to register an email address but that address is not yet verified, they see a pop up or toast or similar that explains that doing this might overwrite that existing user's data (if any).
Ideally it would be nice to have to just check if the user already has any data against the existing account and if not actually go ahead and register it again after a much less scary warning - not sure if needed.
Summary
Due to the various flows that take you to the 'create checkbook' page it is possible to get their without an email or to try and use an email which is already 'taken'. For now we just want to do the simplest thing and prevent these 'lost souls' from trying to create another account. (We could create another key/pair and account but that would get confusing hella fast so we'll skip for now).
Ideally it would be nice to have to just check if the user already has any data against the existing account and if not actually go ahead and register it again after a much less scary warning - not sure if needed.