Multi-identifier
Status
Problem Statement
What's the need we're addressing?
As a web3 native, I want to use the scheduling tool but find it scary to connect my wallet which makes me feel unsafe
User Story
What's the solution going to be like?
Enable users to log-in (create an account) using different identifiers (e.g. twitter, discord, wallet, etc) and then connect multiple identifiers together so they can seamlessly use whichever one they desire.
Functional Requirements
key functionalities that the feature provides
Non-functional Requirements
other requirements of the feature
Acceptance Criteria
what needs to happen/be true for this feature to be approved
- .
- .
Research Questions
to be discovered through the design process
- Do we need 2 factor authentication from the start or can this be added later?