base · soheimam · Apr 28, 2026 · Apr 30, 2026 · Apr 30, 2026 · Apr 30, 2026
diff --git a/docs/agents.md b/docs/agents.md
@@ -11,11 +11,13 @@ Base is an Ethereum L2 by Coinbase. Docs for: Base Chain, Smart Wallet, OnchainK
 |ai-agents/skills/trading:alchemy-agentic-gateway,coingecko,swap-execution
 |ai-agents/skills/wallets:bankr,cdp-agentic-wallet,sponge-wallet
 |ai-agents/trading:data-fetching,trade-execution
+|apps/builder-codes:agent-developers,app-developers,builder-codes,wallet-developers
 |apps/growth:rewards
-|apps/quality-and-publishing:overview,quality-bar,submission-guidelines
-|apps/quickstart:build-checklist,building-for-the-base-app,create-new-app,migrate-existing-apps,migrate-to-standard-web-app,template
-|apps/technical-guides:accept-payments,base-notifications,building-chat-agents,neynar-notifications,sharing-and-social-graph,sign-manifest
-|base-account/basenames:basename-transfer,basenames-faq,basenames-wagmi-tutorial
+|apps/guides:migrate-to-standard-web-app
+|apps/quickstart:build-app
+|apps/resources:design-resources,templates
+|apps/technical-guides:base-notifications
+|base-account/basenames:basename-transfer,basenames-faq
 |base-account/contribute:contribute-to-base-account-docs,security-and-bug-bounty
 |base-account/framework-integrations:cdp,rainbowkit,reown,thirdweb
 |base-account/framework-integrations/privy:authentication,setup,spend-permissions,sub-accounts,wallet-actions
@@ -40,12 +42,11 @@ Base is an Ethereum L2 by Coinbase. Docs for: Base Chain, Smart Wallet, OnchainK
 |base-chain/api-reference/debug-api:debug_traceBlockByHash,debug_traceBlockByNumber,debug_traceTransaction
 |base-chain/api-reference/ethereum-json-rpc-api:eth_blockNumber,eth_call,eth_chainId,eth_estimateGas,eth_feeHistory,eth_gasPrice,eth_getBalance,eth_getBlockByHash,eth_getBlockByNumber,eth_getBlockReceipts,eth_getBlockTransactionCountByHash,eth_getBlockTransactionCountByNumber,eth_getCode,eth_getLogs,eth_getStorageAt,eth_getTransactionByBlockHashAndIndex,eth_getTransactionByBlockNumberAndIndex,eth_getTransactionByHash,eth_getTransactionCount,eth_getTransactionReceipt,eth_maxPriorityFeePerGas,eth_sendRawTransaction,eth_subscribe,eth_syncing,eth_unsubscribe,net_version,web3_clientVersion
 |base-chain/api-reference/flashblocks-api:base_transactionStatus,eth_simulateV1,flashblocks-api-overview,newFlashblockTransactions,newFlashblocks,pendingLogs
-|base-chain/builder-codes:agent-developers,app-developers,builder-codes,wallet-developers
-|base-chain/flashblocks:app-integration,architecture,faq,overview,run-a-flashblocks-node
+|base-chain/flashblocks:app-integration,architecture,faq,overview
 |base-chain/network-information:base-contracts,block-building,bridges,configuration-changelog,diffs-ethereum-base,ecosystem-contracts,network-faucets,network-fees,transaction-finality,troubleshooting-transactions
-|base-chain/node-operators:node-providers,performance-tuning,run-a-base-node,snapshots,troubleshooting
+|base-chain/node-operators:base-v1-upgrade,node-providers,performance-tuning,run-a-base-node,snapshots,troubleshooting
 |base-chain/quickstart:base-solana-bridge,connecting-to-base,deploy-on-base,why-base
 |base-chain/security:avoid-malicious-flags,bug-bounty,report-vulnerability,security-council
-|get-started:base-mentorship-program,base-services-hub,base,block-explorers,build-app,concepts,country-leads-and-ambassadors,data-indexers,deploy-smart-contracts,docs-llms,docs-mcp,get-funded,launch-token,learning-resources,mistakes,prompt-library,resources-for-ai-agents
+|get-started:base-mentorship-program,base-services-hub,base,block-explorers,concepts,country-leads-and-ambassadors,data-indexers,deploy-smart-contracts,docs-llms,docs-mcp,get-funded,launch-token,learning-resources,mistakes,prompt-library,resources-for-ai-agents
 |onchainkit:migrate-from-onchainkit
 |root:agents,changes,cookie-policy,privacy-policy,terms-of-service,tone_of_voice
diff --git a/...uickstart/migrate-to-standard-web-app.mdx → ...ps/guides/migrate-to-standard-web-app.mdx b/...uickstart/migrate-to-standard-web-app.mdx → ...ps/guides/migrate-to-standard-web-app.mdx
@@ -1,7 +1,6 @@
 ---
 title: "Migrate to a Standard Web App"
 description: "Migrate your Farcaster mini-app to work in the Base App. Covers replacing deprecated SDK methods, and registering on Base.dev."
-tag: "NEW"
 ---
 
 <Warning>
@@ -20,7 +19,7 @@ The Base App is moving from the Farcaster mini-app spec to a single model: **sta
 | --- | --- |
 | 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. |
 | Neynar webhooks for add/remove events | Base-owned backends (Base Account / address preferences) |
-| FID-based notifications via Neynar | Wallet-address notifications via Base.dev notifications API *(coming soon)* |
+| FID-based notifications via Neynar | Wallet-address notifications through the [Notifications API](/apps/technical-guides/base-notifications) |
 | Farcaster SDK for auth and actions | wagmi + viem + Sign-In with Ethereum (SIWE) |
 | Search and discovery via Farcaster | Base.dev app metadata + [builder codes](https://docs.base.org/apps/builder-codes/builder-codes) |
 
@@ -166,10 +165,7 @@ Your app uses the Farcaster SDK. The migration replaces Farcaster-specific auth,
 </Step>
 
 <Step title="Migrate notifications to Base.dev">
-  <Warning>
-  Notifications migration will be available in Base.dev soon.
-  </Warning>
-  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.
+  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.
 </Step>
 
 <Step title="Register on Base.dev">
@@ -197,10 +193,7 @@ Your app is already a standard web app. You're mostly done — just verify your
 </Step>
 
 <Step title="Integrate notifications (optional)">
-  <Warning>
-  Notifications migration will be available in Base.dev soon.
-  </Warning>
-  Use the Base.dev notifications API to send wallet-address notifications to users who installed your app and opted in.
+  Follow the [Notifications guide](/apps/technical-guides/base-notifications) to send wallet-address notifications to users who installed your app and opted in.
 </Step>
 </Steps>
 
@@ -250,10 +243,7 @@ Before considering your app migrated, verify the following:
 </Step>
 
 <Step title="Notifications use Base.dev API (if applicable)">
-<Warning>
-  Notifications migration will be available in Base.dev soon.
-</Warning>
-  Notifications are sent via the Base.dev notifications API by wallet address — not via Neynar, FIDs, or tokens.
+  Notifications are sent by wallet address using the [Notifications guide](/apps/technical-guides/base-notifications), not through Neynar, FIDs, or tokens.
 </Step>
 
 </Steps>

diff --git a/docs/apps/llms-full.txt b/docs/apps/llms-full.txt
@@ -5,31 +5,43 @@
 > 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.
 
 ### What you can do here
+- Build a Next.js app on Base with wagmi, viem, wallet connection, contract reads, contract writes, and batch transactions
 - Migrate an existing Farcaster-embedded app to a standard web app compatible with the Base App
 - Register your app on Base.dev for search, discovery, and rewards eligibility
 - Replace deprecated Farcaster SDK methods with standard web equivalents (wagmi, viem, SIWE)
 - Earn financial rewards for building apps that drive user engagement and onchain transactions
+- Attribute onchain transactions to your app using Builder Codes (ERC-8021)
+- Send in-app push notifications to opted-in users via the Base Dashboard Notifications API
 
 ## Navigation (with brief descriptions)
 
 ### Quickstart
-- [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
+- [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
+
+### Guides
+- [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
+- [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
 
 ### Growth
 - [Rewards](https://docs.base.org/apps/growth/rewards.md) — Verification programs, competitions, and partner opportunities for earning rewards
 
+### Builder Codes
+- [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
+- [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
+- [For Wallet Developers](https://docs.base.org/apps/builder-codes/wallet-developers.md) — Implement the ERC-5792 DataSuffixCapability so wallets pass through attribution suffixes
+- [For Agent Developers](https://docs.base.org/apps/builder-codes/agent-developers.md) — Attribute AI agent transactions via the Builder Codes API
 
 ## Key Concepts (excerpts)
 
-Source: `https://docs.base.org/apps/quickstart/migrate-to-standard-web-app.md`
+Source: `https://docs.base.org/apps/guides/migrate-to-standard-web-app.md`
 
 After April 9, 2026, the Base App treats all apps as standard web apps regardless of Farcaster manifests. Key changes:
 
 | Before | After |
 | --- | --- |
 | Farcaster manifest (`/.well-known/farcaster.json`) | App metadata on Base.dev |
 | Neynar webhooks for add/remove events | Base-owned backends (Base Account / address preferences) |
-| FID-based notifications via Neynar | Wallet-address notifications via Base.dev notifications API |
+| FID-based notifications via Neynar | Wallet-address notifications through the Notifications API |
 | Farcaster SDK for auth and actions | wagmi + viem + Sign-In with Ethereum (SIWE) |
 | Search and discovery via Farcaster | Base.dev app metadata + builder codes |
 
@@ -43,6 +55,25 @@ Base.dev rewards developers who build apps that deliver real value and drive mea
 1. Submit your app for verification on Base.dev — validates ownership by adding a Base builder address in the manifest
 2. Access earning opportunities — partner programs, competitions, and special campaigns
 
+Source: `https://docs.base.org/apps/builder-codes/builder-codes.md`
+
+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).
+
+Source: `https://docs.base.org/apps/technical-guides/base-notifications.md`
+
+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.
+
+Key constraints:
+- Notifications delivered in the **Base App only** — not other platforms
+- Rate limit: **20 requests/minute per IP** shared across both endpoints
+- `POST /send`: up to 1,000 addresses per request; title ≤30 chars, message ≤200 chars
+- Deduplication: identical notifications within 24 hours are suppressed automatically
+- Failure reasons: `user has not saved this app`, `user has notifications disabled`
+
+Workflow:
+1. `GET /v1/notifications/app/users?app_url=<url>&notification_enabled=true` — fetch opted-in wallet addresses (paginated, cursor-based)
+2. `POST /v1/notifications/send` — send title + message + optional `target_path` to up to 1,000 addresses
+
 
 ## Related indexes
 - Root index: `../llms.txt`

diff --git a/docs/apps/llms.txt b/docs/apps/llms.txt
@@ -5,7 +5,18 @@
 > 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.
 
 ## Quickstart
-- [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
+- [Build an App](https://docs.base.org/apps/quickstart/build-app.md) — End-to-end guide to ship your first app on Base
+
+## Guides
+- [Add notifications](https://docs.base.org/apps/technical-guides/base-notifications.md) — Send in-app notifications to users via the Base Dashboard REST API
+- [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
 
 ## Growth
 - [Rewards](https://docs.base.org/apps/growth/rewards.md) — Earn financial incentives for building apps that drive user engagement and onchain transactions
+
+## Builder Codes
+- [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
+- [For App Developers](https://docs.base.org/apps/builder-codes/app-developers.md) — Integrate Builder Codes using wagmi or viem
+- [For Wallet Developers](https://docs.base.org/apps/builder-codes/wallet-developers.md) — Implement the dataSuffix ERC-5792 capability
+- [For Agent Developers](https://docs.base.org/apps/builder-codes/agent-developers.md) — Attribute AI agent transactions via the API
+
diff --git a/docs/get-started/build-app.mdx → docs/apps/quickstart/build-app.mdx b/docs/get-started/build-app.mdx → docs/apps/quickstart/build-app.mdx
@@ -541,6 +541,7 @@ Base is a fast, low-cost Ethereum L2 built to bring the next billion users oncha
 
 - **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`.
 - **Sponsor gas** — use the `paymasterService` capability with `useSendCalls` to cover your users' transaction fees. See [Sponsor Gas](/base-account/improve-ux/sponsor-gas/paymasters).
+- **Send notifications** — use the [Notifications guide](/apps/technical-guides/base-notifications) to fetch opted-in wallet addresses and send in-app notifications.
 - **Batch read calls** — reduce RPC round trips by batching reads via viem's `multicall`.
 - **Optimistic updates** — update the UI before confirmation using TanStack Query's `onMutate` callback.
 - **Wagmi setup reference** — review the full [Wagmi setup guide](/base-account/framework-integrations/wagmi/setup) for additional configuration options.
diff --git a/docs/apps/technical-guides/base-notifications.mdx b/docs/apps/technical-guides/base-notifications.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Notifications"
+title: "Add notifications"
 description: "Send in-app notifications to your app's users through the Base Dashboard REST API."
 ---
 
@@ -19,7 +19,7 @@ The Notifications API lets you send in-app notifications to users who have pinne
 Both endpoints require your API key in the `x-api-key` header.
 
 <Info>
-  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.
+  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.
 </Info>
 
 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
 </ParamField>
 
 <ParamField query="limit" type="integer">
-  Maximum users per page. Capped at 100.
+  Maximum users per page. Capped at 500.
 </ParamField>
 
 #### Response

diff --git a/docs/base-chain/llms-full.txt b/docs/base-chain/llms-full.txt
@@ -48,6 +48,7 @@
 
 ### Node Operators
 - [Run a Base Node](https://docs.base.org/base-chain/node-operators/run-a-base-node.md) — Node setup
+- [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
 - [Performance Tuning](https://docs.base.org/base-chain/node-operators/performance-tuning.md) — Optimization
 - [Snapshots](https://docs.base.org/base-chain/node-operators/snapshots.md) — Snapshot sync
 - [Troubleshooting](https://docs.base.org/base-chain/node-operators/troubleshooting.md) — Common fixes

diff --git a/docs/base-chain/llms.txt b/docs/base-chain/llms.txt
@@ -13,13 +13,18 @@
 ## Network Information
 - [Network Fees](https://docs.base.org/base-chain/network-information/network-fees.md) — L2 execution and L1 data costs on Base
 - [Base Contracts](https://docs.base.org/base-chain/network-information/base-contracts.md) — Core contracts and addresses
+- [Block Building](https://docs.base.org/base-chain/network-information/block-building.md) — How blocks are ordered and built on Base
 - [Bridges](https://docs.base.org/base-chain/network-information/bridges.md) — Official and third-party bridge options
+- [Differences: Ethereum & Base](https://docs.base.org/base-chain/network-information/diffs-ethereum-base.md) — Behavioral differences between Base and Ethereum
+- [Transaction Finality](https://docs.base.org/base-chain/network-information/transaction-finality.md) — When transactions become irreversible on Base
 - [Troubleshooting Transactions](https://docs.base.org/base-chain/network-information/troubleshooting-transactions.md) — Diagnose and fix common transaction issues
+- [Configuration Changelog](https://docs.base.org/base-chain/network-information/configuration-changelog.md) — Log of network configuration changes
 - [Network Faucets](https://docs.base.org/base-chain/network-information/network-faucets.md) — Obtain testnet ETH for Base Sepolia
 
 ## Flashblocks
 - [Overview](https://docs.base.org/base-chain/flashblocks/overview.md) — What Flashblocks is and how it works
 - [App Integration](https://docs.base.org/base-chain/flashblocks/app-integration.md) — How apps integrate with Flashblocks
+- [Architecture](https://docs.base.org/base-chain/flashblocks/architecture.md) — Sequencer architecture and infrastructure components
 - [FAQ](https://docs.base.org/base-chain/flashblocks/faq.md) — Frequently asked questions about Flashblocks
 
 ## API Reference
@@ -30,7 +35,10 @@
 
 ## Node Operators
 - [Run a Base Node](https://docs.base.org/base-chain/node-operators/run-a-base-node.md) — Setup and operations guide
+- [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
 - [Performance Tuning](https://docs.base.org/base-chain/node-operators/performance-tuning.md) — Optimize node performance
+- [Snapshots](https://docs.base.org/base-chain/node-operators/snapshots.md) — Snapshot sync to speed up initial node setup
+- [Troubleshooting](https://docs.base.org/base-chain/node-operators/troubleshooting.md) — Diagnose and fix common node issues
 - [Node Providers](https://docs.base.org/base-chain/node-operators/node-providers.md) — RPC node providers for Base
 
 ## Protocol Specs
@@ -59,6 +67,7 @@
 ## Security
 - [Report a Vulnerability](https://docs.base.org/base-chain/security/report-vulnerability.md) — Security contact and disclosure
 - [Security Council](https://docs.base.org/base-chain/security/security-council.md) — Governance and process overview
+- [Avoid Malicious Flags](https://docs.base.org/base-chain/security/avoid-malicious-flags.md) — How to avoid app-blocklist flags
 
 ## Builder Codes
 - [Builder Codes](https://docs.base.org/apps/builder-codes/builder-codes.md) — Overview of the Builder Codes program