Pat/auth flowchart #680
Pat/auth flowchart #680
Conversation
🟡 Heimdall Review Status
|
|
|
||
|
|
||
| ## Choosing An Authentication Method | ||
| Users in the Base app are authenticated with passkey account using [Sign in with Ethereum](https://docs.login.xyz/) (SIWE) or their Farcaster account using [Sign in With Farcaster](https://docs.farcaster.xyz/developers/siwf/). |
There was a problem hiding this comment.
"Users in the Base app are authenticated with their Base Account using ..."
Is there a reason to say passkey instead of Base Account?
|
|
||
| If your app will be used on the open web, other wallets, or standalone mobile apps, use SIWE as your primary authentication. | ||
|
|
||
| You can still offer SIWF when the user arrives from a Farcaster client. |
There was a problem hiding this comment.
How are accounts linked between SIWE outside of a farcaster client and SIWF within a farcaster client?
Are builders supposed to create an association in the database that maps the user's FID to the ethereum wallet they're using?
|
|
||
| #### Utilizing Farcaster Social Graph | ||
|
|
||
| If your app does not rely on followers, FIDs, casts, or social graph logic, use SIWE and optionally support SIWF for enhanced social features. |
There was a problem hiding this comment.
The "optionally support SIWF" path is unclear to me technically... Are you allowing users to SIWF but not providing any of teh casts / social graph logic / notifications etc because doing so would break the experience for users who are only using SIWE?
|
|
||
| Quick Auth provides instant authentication by leveraging Farcaster's identity system - no passwords, email verification, or complex OAuth flows required. | ||
|
|
||
| When Quick Auth is called: |
There was a problem hiding this comment.
After the section between using SIWE vs SIWF we then go into a section that solely talks about SIWF via quick auth. What are the builders who selected SIWE going to do? What is their implementation path?
If we're trying to push builders towards SIWE, should we prioritize that implementation path over quick auth?
| ## Choosing An Authentication Method | ||
| Users in the Base app are authenticated with passkey account using [Sign in with Ethereum](https://docs.login.xyz/) (SIWE) or their Farcaster account using [Sign in With Farcaster](https://docs.farcaster.xyz/developers/siwf/). | ||
|
|
||
| When deciding between SIWE and SIWF, the core question is whether your app depends on Farcaster’s social context or must work outside Farcaster clients. |
There was a problem hiding this comment.
Is this just a "line"? because you can SIWF in a browser without needing to be inside of a farcaster client. Its the same as sign in with gmail or the like... so this statement isn't really the crux of the decision as I understand it
What changed? Why?
Notes to reviewers
How has it been tested?