You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/apps/guides/migrate-to-standard-web-app.mdx
+4-14Lines changed: 4 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,6 @@
1
1
---
2
2
title: "Migrate to a Standard Web App"
3
3
description: "Migrate your Farcaster mini-app to work in the Base App. Covers replacing deprecated SDK methods, and registering on Base.dev."
4
-
tag: "NEW"
5
4
---
6
5
7
6
<Warning>
@@ -20,7 +19,7 @@ The Base App is moving from the Farcaster mini-app spec to a single model: **sta
20
19
| --- | --- |
21
20
| Farcaster manifest (`/.well-known/farcaster.json`) | App metadata on [Base.dev](https://www.base.dev) projects. Already registered apps do not need to update metadata. |
| FID-based notifications via Neynar | Wallet-address notifications via Base.dev notifications API*(coming soon)*|
22
+
| FID-based notifications via Neynar | Wallet-address notifications through the [Notifications API](/apps/technical-guides/base-notifications)|
24
23
| Farcaster SDK for auth and actions | wagmi + viem + Sign-In with Ethereum (SIWE) |
25
24
| Search and discovery via Farcaster | Base.dev app metadata + [builder codes](https://docs.base.org/apps/builder-codes/builder-codes)|
26
25
@@ -166,10 +165,7 @@ Your app uses the Farcaster SDK. The migration replaces Farcaster-specific auth,
166
165
</Step>
167
166
168
167
<Steptitle="Migrate notifications to Base.dev">
169
-
<Warning>
170
-
Notifications migration will be available in Base.dev soon.
171
-
</Warning>
172
-
Farcaster-based notifications (via Neynar, FIDs, or tokens) will not reach Base App users. Replace them with the Base.dev notifications API, which sends by wallet address.
168
+
Farcaster-based notifications (via Neynar, FIDs, or tokens) will not reach Base App users. Follow the [Notifications guide](/apps/technical-guides/base-notifications) to fetch opted-in wallet addresses and send notifications through the Base Dashboard API.
173
169
</Step>
174
170
175
171
<Steptitle="Register on Base.dev">
@@ -197,10 +193,7 @@ Your app is already a standard web app. You're mostly done — just verify your
197
193
</Step>
198
194
199
195
<Steptitle="Integrate notifications (optional)">
200
-
<Warning>
201
-
Notifications migration will be available in Base.dev soon.
202
-
</Warning>
203
-
Use the Base.dev notifications API to send wallet-address notifications to users who installed your app and opted in.
196
+
Follow the [Notifications guide](/apps/technical-guides/base-notifications) to send wallet-address notifications to users who installed your app and opted in.
204
197
</Step>
205
198
</Steps>
206
199
@@ -250,10 +243,7 @@ Before considering your app migrated, verify the following:
250
243
</Step>
251
244
252
245
<Steptitle="Notifications use Base.dev API (if applicable)">
253
-
<Warning>
254
-
Notifications migration will be available in Base.dev soon.
255
-
</Warning>
256
-
Notifications are sent via the Base.dev notifications API by wallet address — not via Neynar, FIDs, or tokens.
246
+
Notifications are sent by wallet address using the [Notifications guide](/apps/technical-guides/base-notifications), not through Neynar, FIDs, or tokens.
Copy file name to clipboardExpand all lines: docs/apps/llms-full.txt
+34-3Lines changed: 34 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -5,31 +5,43 @@
5
5
> The Base App now treats all apps as standard web apps. Migrate from Farcaster-specific SDKs to wagmi + SIWE, register on Base.dev, and earn rewards for driving onchain activity.
6
6
7
7
### What you can do here
8
+
- Build a Next.js app on Base with wagmi, viem, wallet connection, contract reads, contract writes, and batch transactions
8
9
- Migrate an existing Farcaster-embedded app to a standard web app compatible with the Base App
9
10
- Register your app on Base.dev for search, discovery, and rewards eligibility
10
11
- Replace deprecated Farcaster SDK methods with standard web equivalents (wagmi, viem, SIWE)
11
12
- Earn financial rewards for building apps that drive user engagement and onchain transactions
13
+
- Attribute onchain transactions to your app using Builder Codes (ERC-8021)
14
+
- Send in-app push notifications to opted-in users via the Base Dashboard Notifications API
12
15
13
16
## Navigation (with brief descriptions)
14
17
15
18
### Quickstart
16
-
- [Migrate to a Standard Web App](https://docs.base.org/apps/quickstart/migrate-to-standard-web-app.md) — Step-by-step migration guide: replace Farcaster SDK, update auth and wallet logic, register on Base.dev
19
+
- [Build an App](https://docs.base.org/apps/quickstart/build-app.md) — Step-by-step guide to build a Next.js app on Base with wagmi and viem
20
+
21
+
### Guides
22
+
- [Add notifications](https://docs.base.org/apps/technical-guides/base-notifications.md) — REST API (via Base Dashboard) to fetch opted-in users and send in-app notifications; Base App only
23
+
- [Migrate to a Standard Web App](https://docs.base.org/apps/guides/migrate-to-standard-web-app.md) — Step-by-step migration guide: replace Farcaster SDK, update auth and wallet logic, register on Base.dev
17
24
18
25
### Growth
19
26
- [Rewards](https://docs.base.org/apps/growth/rewards.md) — Verification programs, competitions, and partner opportunities for earning rewards
20
27
28
+
### Builder Codes
29
+
- [Builder Codes overview](https://docs.base.org/apps/builder-codes/builder-codes.md) — ERC-8021 NFT codes that attribute onchain transactions to your app; register on base.dev under Settings → Builder Code
30
+
- [For App Developers](https://docs.base.org/apps/builder-codes/app-developers.md) — Append a dataSuffix to transactions using wagmi or viem; no contract changes required
31
+
- [For Wallet Developers](https://docs.base.org/apps/builder-codes/wallet-developers.md) — Implement the ERC-5792 DataSuffixCapability so wallets pass through attribution suffixes
32
+
- [For Agent Developers](https://docs.base.org/apps/builder-codes/agent-developers.md) — Attribute AI agent transactions via the Builder Codes API
Builder Codes are ERC-721 NFTs (unique strings like "abc123") that tag transactions with your app identity using ERC-8021 calldata suffixes. No contract changes are required — attribution is extracted offchain. Benefits: automatic reward attribution, analytics on base.dev, and discovery surface visibility. The suffix adds 16 gas per non-zero byte. Works with EOAs, smart wallets (ERC-5792 `dataSuffix` capability), and embedded wallets (Privy, Turnkey).
The Notifications API sends in-app push notifications to Base App users who have pinned your app and opted in. Requires a Base Dashboard project and API key.
65
+
66
+
Key constraints:
67
+
- Notifications delivered in the **Base App only** — not other platforms
68
+
- Rate limit: **20 requests/minute per IP** shared across both endpoints
69
+
- `POST /send`: up to 1,000 addresses per request; title ≤30 chars, message ≤200 chars
70
+
- Deduplication: identical notifications within 24 hours are suppressed automatically
71
+
- Failure reasons: `user has not saved this app`, `user has notifications disabled`
Copy file name to clipboardExpand all lines: docs/apps/llms.txt
+12-1Lines changed: 12 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,18 @@
5
5
> Build apps that run in the Base App as standard web apps — no Farcaster SDK required. Register on Base.dev, use wagmi + SIWE for auth, and earn rewards for driving onchain activity.
6
6
7
7
## Quickstart
8
-
- [Migrate to a Standard Web App](https://docs.base.org/apps/quickstart/migrate-to-standard-web-app.md) — Replace deprecated Farcaster SDK methods and register your app on Base.dev
8
+
- [Build an App](https://docs.base.org/apps/quickstart/build-app.md) — End-to-end guide to ship your first app on Base
9
+
10
+
## Guides
11
+
- [Add notifications](https://docs.base.org/apps/technical-guides/base-notifications.md) — Send in-app notifications to users via the Base Dashboard REST API
12
+
- [Migrate to a Standard Web App](https://docs.base.org/apps/guides/migrate-to-standard-web-app.md) — Replace deprecated Farcaster SDK methods and register your app on Base.dev
9
13
10
14
## Growth
11
15
- [Rewards](https://docs.base.org/apps/growth/rewards.md) — Earn financial incentives for building apps that drive user engagement and onchain transactions
16
+
17
+
## Builder Codes
18
+
- [Builder Codes overview](https://docs.base.org/apps/builder-codes/builder-codes.md) — Attribute onchain activity to your app using ERC-8021 NFT codes; register on base.dev
19
+
- [For App Developers](https://docs.base.org/apps/builder-codes/app-developers.md) — Integrate Builder Codes using wagmi or viem
20
+
- [For Wallet Developers](https://docs.base.org/apps/builder-codes/wallet-developers.md) — Implement the dataSuffix ERC-5792 capability
21
+
- [For Agent Developers](https://docs.base.org/apps/builder-codes/agent-developers.md) — Attribute AI agent transactions via the API
Copy file name to clipboardExpand all lines: docs/apps/quickstart/build-app.mdx
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -541,6 +541,7 @@ Base is a fast, low-cost Ethereum L2 built to bring the next billion users oncha
541
541
542
542
-**Go to mainnet** — add `base` to your `chains` array and transports in `config/wagmi.ts`, redeploy your contract to Base mainnet, and update `COUNTER_ADDRESS`.
543
543
-**Sponsor gas** — use the `paymasterService` capability with `useSendCalls` to cover your users' transaction fees. See [Sponsor Gas](/base-account/improve-ux/sponsor-gas/paymasters).
544
+
-**Send notifications** — use the [Notifications guide](/apps/technical-guides/base-notifications) to fetch opted-in wallet addresses and send in-app notifications.
544
545
-**Batch read calls** — reduce RPC round trips by batching reads via viem's `multicall`.
545
546
-**Optimistic updates** — update the UI before confirmation using TanStack Query's `onMutate` callback.
546
547
-**Wagmi setup reference** — review the full [Wagmi setup guide](/base-account/framework-integrations/wagmi/setup) for additional configuration options.
Copy file name to clipboardExpand all lines: docs/apps/technical-guides/base-notifications.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: "Notifications"
2
+
title: "Add notifications"
3
3
description: "Send in-app notifications to your app's users through the Base Dashboard REST API."
4
4
---
5
5
@@ -19,7 +19,7 @@ The Notifications API lets you send in-app notifications to users who have pinne
19
19
Both endpoints require your API key in the `x-api-key` header.
20
20
21
21
<Info>
22
-
The notification endpoints share a rate limit of **10 requests per minute per IP**. Requests to either endpoint count toward the same limit. Exceeding it returns a `429 Too Many Requests` response.
22
+
The notification endpoints share a rate limit of **20 requests per minute per IP**. Requests to either endpoint count toward the same limit. Exceeding it returns a `429 Too Many Requests` response.
23
23
</Info>
24
24
25
25
Fetch the wallet addresses of users who have opted in to notifications for your app:
@@ -90,7 +90,7 @@ GET https://dashboard.base.org/api/v1/notifications/app/users
Copy file name to clipboardExpand all lines: docs/base-chain/llms.txt
+9Lines changed: 9 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -13,13 +13,18 @@
13
13
## Network Information
14
14
- [Network Fees](https://docs.base.org/base-chain/network-information/network-fees.md) — L2 execution and L1 data costs on Base
15
15
- [Base Contracts](https://docs.base.org/base-chain/network-information/base-contracts.md) — Core contracts and addresses
16
+
- [Block Building](https://docs.base.org/base-chain/network-information/block-building.md) — How blocks are ordered and built on Base
16
17
- [Bridges](https://docs.base.org/base-chain/network-information/bridges.md) — Official and third-party bridge options
18
+
- [Differences: Ethereum & Base](https://docs.base.org/base-chain/network-information/diffs-ethereum-base.md) — Behavioral differences between Base and Ethereum
19
+
- [Transaction Finality](https://docs.base.org/base-chain/network-information/transaction-finality.md) — When transactions become irreversible on Base
17
20
- [Troubleshooting Transactions](https://docs.base.org/base-chain/network-information/troubleshooting-transactions.md) — Diagnose and fix common transaction issues
21
+
- [Configuration Changelog](https://docs.base.org/base-chain/network-information/configuration-changelog.md) — Log of network configuration changes
18
22
- [Network Faucets](https://docs.base.org/base-chain/network-information/network-faucets.md) — Obtain testnet ETH for Base Sepolia
19
23
20
24
## Flashblocks
21
25
- [Overview](https://docs.base.org/base-chain/flashblocks/overview.md) — What Flashblocks is and how it works
22
26
- [App Integration](https://docs.base.org/base-chain/flashblocks/app-integration.md) — How apps integrate with Flashblocks
27
+
- [Architecture](https://docs.base.org/base-chain/flashblocks/architecture.md) — Sequencer architecture and infrastructure components
23
28
- [FAQ](https://docs.base.org/base-chain/flashblocks/faq.md) — Frequently asked questions about Flashblocks
24
29
25
30
## API Reference
@@ -30,7 +35,10 @@
30
35
31
36
## Node Operators
32
37
- [Run a Base Node](https://docs.base.org/base-chain/node-operators/run-a-base-node.md) — Setup and operations guide
38
+
- [Base Azul Upgrade](https://docs.base.org/base-chain/node-operators/base-v1-upgrade.md) — Migrate to base-reth-node and base-consensus for Azul
0 commit comments