base · ericbrown99 · May 8, 2026
diff --git a/docs/agents.md b/docs/agents.md
@@ -50,7 +50,7 @@ npx skills add base/base-skills
 |apps/builder-codes:agent-developers,app-developers,builder-codes,wallet-developers
 |apps/growth:rewards
 |apps/guides:migrate-to-standard-web-app
-|apps/quickstart:build-app
+|apps/quickstart:build-app,deploy-on-base
 |apps/resources:design-resources,templates
 |apps/technical-guides:base-notifications
 |base-account/basenames:basename-transfer,basenames-faq
@@ -78,10 +78,10 @@ npx skills add base/base-skills
 |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/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:overview
+|base-chain/network-information:base-contracts,base-solana-bridge,block-building,bridges,configuration-changelog,diffs-ethereum-base,ecosystem-contracts,network-faucets,network-fees,networks-and-endpoints,sequencing-policy,throughput-and-limits,transaction-finality,transaction-lifecycle,troubleshooting-transactions
 |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/quickstart:connecting-to-base
 |base-chain/security:avoid-malicious-flags,bug-bounty,report-vulnerability,security-council
 |base-chain/specs:overview
 |base-chain/specs/bcps:bcp-0000,index

diff --git a/docs/ai-agents/setup/agent-builder-codes.mdx b/docs/ai-agents/setup/agent-builder-codes.mdx
@@ -1,11 +1,11 @@
 ---
 title: "Builder Codes for Agents"
-description: "Register your agent on Base.dev and append a Builder Code to every transaction to measure onchain activity."
-keywords: ["builder code", "Base.dev", "ERC-8021", "attribution", "onchain activity", "agent attribution", "dataSuffix", "builder codes", "Base builder codes", "agent onchain"]
+description: "Register your agent in Base Dashboard and append a Builder Code to every transaction to measure onchain activity."
+keywords: ["builder code", "Base Dashboard", "ERC-8021", "attribution", "onchain activity", "agent attribution", "dataSuffix", "builder codes", "Base builder codes", "agent onchain"]
 tag: "NEW"
 ---
 
-[Base.dev](https://base.dev) is the canonical registry for agents on Base. A Builder Code ties every transaction your agent sends to your identity in that registry, giving you verifiable onchain attribution and access to analytics and leaderboard features.
+[Base Dashboard](https://dashboard.base.org) is the canonical registry for agents on Base. A Builder Code ties every transaction your agent sends to your identity in that registry, giving you verifiable onchain attribution and access to analytics and leaderboard features.
 
 ## What you get
 
@@ -52,7 +52,7 @@ If you're using an AI coding tool (Claude Code, Cursor, Codex), install the Base
 npx skills add base/skills
 ```
 
-Then ask your agent: **"Register my agent for a builder code on Base.dev."**
+Then ask your agent: **"Register my agent for a builder code in Base Dashboard."**
 
 The skill runs three phases:
 
@@ -75,7 +75,7 @@ The skill runs three phases:
 If you're using an AI agent, point it to this page:
 
 ```text Prompt
-Get a Builder Code for my agent on Base.dev using the documentation at https://docs.base.org/ai-agents/setup/agent-builder-codes.
+Get a Builder Code for my agent in Base Dashboard using the documentation at https://docs.base.org/ai-agents/setup/agent-builder-codes.
 
 My agent's wallet address: [0x...]
 

diff --git a/docs/ai-agents/trading/trade-execution.mdx b/docs/ai-agents/trading/trade-execution.mdx
@@ -49,7 +49,7 @@ curl -X POST "https://api.wallet.paysponge.com/api/swap" \
 
 ### Use the preconf endpoint for all reads and submissions
 
-Always connect to `mainnet-preconf.base.org` (or `sepolia-preconf.base.org` for testnet) rather than the standard endpoint. This is the only way to access Flashblocks `pending` state, preconfirmed transaction streams, and `base_transactionStatus`. See [Flashblocks endpoints](/base-chain/flashblocks/app-integration#rpc-endpoints) for the full list.
+Always connect to `mainnet-preconf.base.org` (or `sepolia-preconf.base.org` for testnet) rather than the standard endpoint. This is the only way to access Flashblocks `pending` state, preconfirmed transaction streams, and `base_transactionStatus`. See [Networks and Endpoints](/base-chain/network-information/networks-and-endpoints) for the full list.
 
 ### Simulate against preconfirmed state before signing
 
@@ -63,7 +63,7 @@ After submission, [`base_transactionStatus`](/base-chain/api-reference/flashbloc
 
 ### L2 priority fee heuristics
 
-Use [`eth_feeHistory`](/base-chain/api-reference/rpc-overview#eth_feehistory) over the last 5–10 blocks with reward percentiles `[50, 90]`:
+Use [`eth_feeHistory`](/base-chain/api-reference/ethereum-json-rpc-api/eth_feeHistory) over the last 5–10 blocks with reward percentiles `[50, 90]`:
 
 - **50th percentile reward** — standard inclusion within 1–3 Flashblocks
 - **90th percentile reward** — fast inclusion within the next Flashblock
@@ -108,7 +108,7 @@ Base exposes data that most chains don't provide at this resolution:
 ## Related
 
 - [Flashblocks API Reference](/base-chain/api-reference/rpc-overview#flashblocks-api) — `eth_simulateV1`, `base_transactionStatus`, subscription types
-- [Flashblocks Integration Guide](/base-chain/flashblocks/app-integration) — endpoints, library setup (Wagmi, Viem, Ethers)
+- [Base RPC Overview](/base-chain/api-reference/rpc-overview#flashblocks-behavior-matrix) — endpoint behavior, `pending` support, and preconfirmed by-hash lookups
 - [Block Building](/base-chain/network-information/block-building) — Flashblocks timing, per-transaction gas maximum
 - [Network Fees](/base-chain/network-information/network-fees) — EIP-1559 parameters, GasPriceOracle methods
 - [JSON-RPC API Reference](/base-chain/api-reference/rpc-overview) — complete RPC method reference

diff --git a/docs/apps/builder-codes/agent-developers.mdx b/docs/apps/builder-codes/agent-developers.mdx
@@ -9,7 +9,7 @@ AI agents operate autonomously and send transactions without a user manually tri
 ## Why agents need Builder Codes
 
 - **Attribution** — Every transaction your agent sends is tied to your identity in the Base registry. Without it, your agent's onchain activity is anonymous.
-- **Analytics** — Track your agent's transaction volume, user reach, and onchain conversion in [base.dev](https://base.dev).
+- **Analytics** — Track your agent's transaction volume, user reach, and onchain conversion in [Base Dashboard](https://dashboard.base.org).
 - **Visibility** — Agents with Builder Codes can appear in discovery surfaces like Base's App Leaderboard and ecosystem spotlights.
 
 ## How it works
@@ -59,7 +59,7 @@ If you're using an AI coding tool (Claude Code, Cursor, Codex), install the Base
 npx skills add base/skills
 ```
 
-Then ask your agent: **"Register my agent for a builder code on Base.dev."**
+Then ask your agent: **"Register my agent for a builder code in Base Dashboard."**
 
 The skill handles wallet validation, calls the registration API, writes the returned code to `src/constants/builderCode.ts`, installs `ox`, and wires the ERC-8021 `dataSuffix` into your transaction client (viem, ethers.js, or managed service).
 
@@ -69,9 +69,9 @@ Read more in the [Builder Codes for Agents guide](/ai-agents/setup/agent-builder
 
 To confirm your Builder Code is being appended correctly:
 
-**1. Check base.dev**
+**1. Check Base Dashboard**
 
-- Visit [base.dev](https://base.dev)
+- Visit [Base Dashboard](https://dashboard.base.org)
 - Select **Onchain** from the transaction type dropdown
 - Under the Total Transactions section, attribution counts increment when transactions with your code are processed
 

diff --git a/docs/apps/builder-codes/app-developers.mdx b/docs/apps/builder-codes/app-developers.mdx
@@ -6,13 +6,13 @@ description: "Integrate Builder Codes into your app using Wagmi or Viem to attri
 
 ## Automatic Attribution on Base
 
-Once your app is registered on [base.dev](http://base.dev/), the Base App will auto-append your Builder Code to transactions its users make in your app (e.g. via your app, or the Base App's browser). This powers your onchain analytics in [base.dev](http://base.dev/) and qualifies you for potential future rewards.
+Once your app is registered in [Base Dashboard](https://dashboard.base.org), the Base App will auto-append your Builder Code to transactions its users make in your app (e.g. via your app, or the Base App's browser). This powers your onchain analytics in Base Dashboard and qualifies you for potential future rewards.
 
 ## Integrating Outside the Base App
 
 If users also access your app on the web or through other clients, you'll need to integrate the `dataSuffix` parameter to capture that activity.
 
-When you register on [base.dev](https://base.dev/), you will receive a **Builder Code**—a random string (e.g., `bc_b7k3p9da`) that you'll use to generate your attribution suffix. The recommended approach is to configure `dataSuffix` at the client level, which appends your Builder Code to all transactions.
+When you register in [Base Dashboard](https://dashboard.base.org), you will receive a **Builder Code**—a random string (e.g., `bc_b7k3p9da`) that you'll use to generate your attribution suffix. The recommended approach is to configure `dataSuffix` at the client level, which appends your Builder Code to all transactions.
 
 <Tip>
   You can find your code anytime under **Settings** → **Builder Code**.
@@ -37,7 +37,7 @@ When you register on [base.dev](https://base.dev/), you will receive a **Builder
     import { base } from "wagmi/chains";
     import { Attribution } from "ox/erc8021";
 
-    // Get your Builder Code from base.dev > Settings > Builder Codes
+    // Get your Builder Code from Base Dashboard > Settings > Builder Codes
     const DATA_SUFFIX = Attribution.toDataSuffix({
       codes: ["YOUR-BUILDER-CODE"],
     });
@@ -98,7 +98,7 @@ When you register on [base.dev](https://base.dev/), you will receive a **Builder
     import { base } from "viem/chains";
     import { Attribution } from "ox/erc8021";
 
-    // Get your Builder Code from base.dev > Settings > Builder Codes
+    // Get your Builder Code from Base Dashboard > Settings > Builder Codes
     const DATA_SUFFIX = Attribution.toDataSuffix({
       codes: ["YOUR-BUILDER-CODE"],
     });
@@ -220,9 +220,9 @@ See the [Privy Builder Codes integration guide](https://docs.privy.io/recipes/ev
 
 To confirm your Builder Code is being appended correctly:
 
-**1. Check base.dev**
+**1. Check Base Dashboard**
 
-- Visit [base.dev](https://base.dev)
+- Visit [Base Dashboard](https://dashboard.base.org)
 - Select **Onchain** from the transaction type dropdown
 - Under the Total Transactions section, attribution counts increment when transactions with your code are processed
 

diff --git a/docs/apps/builder-codes/builder-codes.mdx b/docs/apps/builder-codes/builder-codes.mdx
@@ -10,7 +10,7 @@ Base Builder Codes are an ERC-721 NFT collection where unique codes (e.g. "abc12
 Each code has associated metadata. Onchain metadata primarily includes a "payout address" where each code declares where potential rewards should be sent to. Offchain metadata includes more details about the app including its name and site.
 
 <Tip>
-  Get your Builder Code by registering on [base.dev](https://base.dev/). You can find your code under **Settings** → **Builder Code**.
+  Get your Builder Code by registering in [Base Dashboard](https://dashboard.base.org). You can find your code under **Settings** → **Builder Code**.
 </Tip>
 
 ## Integration Guides
@@ -30,7 +30,7 @@ Each code has associated metadata. Onchain metadata primarily includes a "payout
 ## Benefits
 
 - **Rewards:** If your app drives transactions, Builder Codes let Base automatically attribute that usage back to you, unlocking rewards as the program expands.
-- **Analytics:** Reliably track onchain usage, user acquisition, and conversion metrics in Base.dev.
+- **Analytics:** Reliably track onchain usage, user acquisition, and conversion metrics in Base Dashboard.
 - **Visibility:** Apps with Builder Codes can show up in discovery surfaces like App Leaderboards, Base App store, and ecosystem spotlights.
 
 ## FAQ
@@ -59,9 +59,9 @@ The ERC-8021 suffix adds a negligible amount of gas to each transaction at 16 ga
 
 ### How Do I Verify That My Transaction Was Properly Attributed?
 
-**1. Check base.dev**
+**1. Check Base Dashboard**
 
-- Visit [base.dev](https://base.dev)
+- Visit [Base Dashboard](https://dashboard.base.org)
 - Select **Onchain** from the transaction type dropdown
 - Under the Total Transactions section, attribution counts increment when transactions with your code are processed
 

diff --git a/docs/apps/growth/rewards.mdx b/docs/apps/growth/rewards.mdx
@@ -4,13 +4,13 @@ title: Rewards
 description: Earn financial incentives for building high-quality  Apps that drive user engagement and onchain transactions
 ---
 
-[Base.dev](https://www.base.dev/) rewards developers who build Apps that deliver real value to users and drive meaningful onchain activity. You can earn rewards through verification programs, competitions, and partner opportunities.
+[Base Dashboard](https://dashboard.base.org) rewards developers who build Apps that deliver real value to users and drive meaningful onchain activity. You can earn rewards through verification programs, competitions, and partner opportunities.
 
 ## How Rewards Work
 
 <Steps>
 <Step title="Verify your App">
-  Submit your App to be verified on [Base.dev](https://www.base.dev/). This process validates your ownership of the app by adding Base builder address.
+  Submit your App to be verified in [Base Dashboard](https://dashboard.base.org). This process validates your ownership of the app by adding a Base builder address.
 
 </Step>
 
@@ -22,4 +22,3 @@ description: Earn financial incentives for building high-quality  Apps that driv
 </Steps>
 
 
-
diff --git a/docs/apps/guides/migrate-to-standard-web-app.mdx b/docs/apps/guides/migrate-to-standard-web-app.mdx
@@ -1,6 +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."
+description: "Migrate your Farcaster mini-app to work in the Base App. Covers replacing deprecated SDK methods and registering in Base Dashboard."
 ---
 
 <Warning>
@@ -13,15 +13,15 @@ After April 9, 2026, the Base App treats all apps as standard web apps regardles
 
 ## What's changing
 
-The Base App is moving from the Farcaster mini-app spec to a single model: **standard web app + wallet**, powered by Base.dev.
+The Base App is moving from the Farcaster mini-app spec to a single model: **standard web app + wallet**, with app metadata managed in Base Dashboard.
 
 | Before | After |
 | --- | --- |
-| 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. |
+| Farcaster manifest (`/.well-known/farcaster.json`) | App metadata in [Base Dashboard](https://dashboard.base.org) 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 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) |
+| Search and discovery via Farcaster | Base Dashboard app metadata + [builder codes](https://docs.base.org/apps/builder-codes/builder-codes) |
 
 ---
 
@@ -164,12 +164,12 @@ Your app uses the Farcaster SDK. The migration replaces Farcaster-specific auth,
   See the [compatibility table](#deprecated-farcaster-sdk-methods-in-the-base-app) for what will and won't work in the Base app, along with standard web alternatives.
 </Step>
 
-<Step title="Migrate notifications to Base.dev">
+<Step title="Migrate notifications to Base Dashboard">
   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">
-  If you haven't registered yet, create a project at [Base.dev](https://www.base.dev) and complete your app metadata: name, icon, tagline, description, screenshots, category, primary URL, and [builder code](/apps/builder-codes/builder-codes). Already registered apps do not need to re-register or update metadata.
+<Step title="Register in Base Dashboard">
+  If you haven't registered yet, create a project in [Base Dashboard](https://dashboard.base.org) and complete your app metadata: name, icon, tagline, description, screenshots, category, primary URL, and [builder code](/apps/builder-codes/builder-codes). Already registered apps do not need to re-register or update metadata.
 </Step>
 </Steps>
 
@@ -179,7 +179,7 @@ Your app uses the Farcaster SDK. The migration replaces Farcaster-specific auth,
 
 <Tab title="My app has no Farcaster SDK">
 
-Your app is already a standard web app. You're mostly done — just verify your stack and register on Base.dev.
+Your app is already a standard web app. You're mostly done — just verify your stack and register in Base Dashboard.
 
 <Steps>
 <Step title="Confirm your app is web- and wallet-ready">
@@ -188,8 +188,8 @@ Your app is already a standard web app. You're mostly done — just verify your
   - Uses [SIWE](https://viem.sh/docs/siwe/utilities/createSiweMessage) for authentication where needed
 </Step>
 
-<Step title="Register on Base.dev">
-  If you haven't registered yet, create a project at [Base.dev](https://www.base.dev) and complete your app metadata: name, icon, tagline, description, screenshots, category, primary URL, and [builder code](/apps/builder-codes/builder-codes). Already registered apps do not need to re-register or update metadata.
+<Step title="Register in Base Dashboard">
+  If you haven't registered yet, create a project in [Base Dashboard](https://dashboard.base.org) and complete your app metadata: name, icon, tagline, description, screenshots, category, primary URL, and [builder code](/apps/builder-codes/builder-codes). Already registered apps do not need to re-register or update metadata.
 </Step>
 
 <Step title="Integrate notifications (optional)">
@@ -238,11 +238,11 @@ Before considering your app migrated, verify the following:
   Wallet connection and contract interactions use wagmi + viem. Authentication uses [SIWE](https://viem.sh/docs/siwe/utilities/createSiweMessage) where needed.
 </Step>
 
-<Step title="Register and complete Base.dev metadata">
-  Project is registered on [Base.dev](https://www.base.dev) with primary URL set. Name, icon, tagline, screenshots, category, description, and [builder code](/apps/builder-codes/builder-codes) are all filled in.
+<Step title="Register and complete Base Dashboard metadata">
+  Project is registered in [Base Dashboard](https://dashboard.base.org) with primary URL set. Name, icon, tagline, screenshots, category, description, and [builder code](/apps/builder-codes/builder-codes) are all filled in.
 </Step>
 
-<Step title="Notifications use Base.dev API (if applicable)">
+<Step title="Notifications use Base Dashboard API (if applicable)">
   Notifications are sent by wallet address using the [Notifications guide](/apps/technical-guides/base-notifications), not through Neynar, FIDs, or tokens.
 </Step>