Skip to content

Commit 5197ed5

Browse files
committed
add callout for notificaitons that AI can read
1 parent b2f37c2 commit 5197ed5

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

docs/mini-apps/core-concepts/authentication.mdx

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,14 @@ When deciding between SIWE and SIWF, the core question is whether your app depen
1111

1212
![auth-flow-chart](/images/miniapps/auth-flowchart.png)
1313

14+
#### Sending Notifications
15+
16+
If your app plans to send notifications to users, you must use SIWF.
17+
Notifications require a Farcaster identity (FID), which is only available through Sign-in With Farcaster.
18+
19+
You can still support SIWE if your app also needs a universal wallet-based identity, but SIWF is required for any notification functionality.
20+
21+
1422
#### App location
1523

1624
If your app will be used on the open web, other wallets, or standalone mobile apps, use SIWE as your primary authentication.

0 commit comments

Comments
 (0)