-
- );
-}
-```
-
-### Step 2: Backend Verification
-
-Install the Quick Auth client:
-
-```bash
-npm install @farcaster/quick-auth
-```
-
-**Quick Auth Client** is the SDK that initiates the authentication flow in your application.
-
-**Quick Auth Server** is Farcaster's service that handles signature verification and issues JWTs.
-
-When a user authenticates, the Quick Auth Server verifies their signature and issues a JWT. Your backend verifies this JWT using the `@farcaster/quick-auth` package.
-
-```jsx route.tsx
-// app/api/auth/route.ts
-import { createClient, Errors } from '@farcaster/quick-auth';
-import { NextRequest, NextResponse } from 'next/server';
-
-const domain = 'your-domain.com'; // Must match your mini app's deployment domain
-const client = createClient();
-
-// This endpoint returns the authenticated user's FID
-export async function GET(request: NextRequest) {
- const authorization = request.headers.get('Authorization');
- if (!authorization?.startsWith('Bearer ')) {
- return NextResponse.json({ error: 'Unauthorized' }, { status: 401 });
- }
-
- const token = authorization.split(' ')[1];
-
- try {
- const payload = await client.verifyJwt({ token, domain });
-
- return NextResponse.json({
- fid: payload.sub,
- });
- } catch (e) {
- if (e instanceof Errors.InvalidTokenError) {
- return NextResponse.json({ error: 'Invalid token' }, { status: 401 });
- }
- throw e;
- }
-}
-```
-
-## Schema
-
-### JWT Payload
-
-
-```json
-{
- "iat": 1747764819,
- "iss": "https://auth.farcaster.xyz",
- "exp": 1747768419,
- "sub": 6841,
- "aud": "your-domain.com"
-}
-```
-Payload fields:
-
-Authenticated as FID: {userData?.fid}
- -
-
- );
- }
-
- // Show user information
- if (user) {
- return (
- Please open this app in a Farcaster or Base client to see your profile.
-
- 
- )}
-
- );
- }
-
- return Welcome, {user.displayName || user.username}!
-FID: {user.fid}
-Username: @{user.username}
- {user.pfpUrl && ( -Loading user profile...
;
-}
-```
-
-## Schema
-
-
-### User Object
-
-Contains the user's profile information. This data shouldn't be used for authentication or sensitive actions because its passed by the application.
-
-
-
-
-
- {result &&
- );
- }
- ```
-
- {result}
} -
-
-* A side menu can also be an intuitive place to put settings and user profile information.
- 
-
-* Always include **labels under icons** so users understand each tab.
-* Test on multiple device sizes to ensure buttons are not cut off.
-
-
-### Colors
-
-Use color to communicate clearly, express your brand, and create cohesive mini app experiences.
-
-### **Color Palette**
-
-* **Primary:** Brand color for CTAs and key interactions.
-* **Secondary:** Complements primary; use for accents or secondary actions.
-* **Neutral:** For text, backgrounds, and structure with strong contrast.
-
-### **Themes**
-
-* Support **light and dark modes**:
-* Maintain contrast and brand consistency.
-* Respect system preference but allow manual toggle.
-* Use smooth transitions between themes.
-* **💡Tip:** Use **semantic color tokens** (e.g., `--color-primary`, `--color-background`) with **light/dark theme overrides** for maintainability and flexibility.
-
-
-### Typography
-
-* Ensure the fonts you use are easy to read. Our team recommends **Inter.**
-* **Ensure sufficient contrast between text and background colors** to make reading easy under various lighting conditions.
-* **Stick to regular, bold, and italic as needed.** Decorative or script fonts should be reserved for accents, not body text.
-
-### Spacing
-
-* Groups related elements together.
-* Consistent spacing: Creates visual rhythm and predictability with consistent spacing.
-* Give content room to breathe with white space.
-* Avoid cramped layouts.
-* Base Unit: Start with a base spacing unit (typically **4px** or **8px**) and maintain consistency throughout:
- * 4px base: More granular control, better for mobile.
- * 8px base: Easier mental math, good for desktop.
-
-
-### Touch Interactions
-
-* Ensure all touch targets are at least **44px**.
-* Support common gestures (tap, swipe, pinch) where appropriate.
-* Don’t rely on **hover states** — they don’t exist on touch screens.
-
diff --git a/docs/apps/featured-guidelines/notification-guidelines.mdx b/docs/apps/featured-guidelines/notification-guidelines.mdx
deleted file mode 100644
index ea7f9a57b..000000000
--- a/docs/apps/featured-guidelines/notification-guidelines.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-hidden: true
-title: "Notification Guidelines"
-description: "Well designed notifications re-engage users, driving retention, and highlight key moments"
----
-
-Notifications will allow you to re-engage users who have saved your Mini App, driving retention and bringing users back at key moments like new content releases, achievements, or time-sensitive events.
-
-Focus on sending updates that are relevant, well-timed, and valuable. It’s important to balance how many notifications you send — too many can cause users to turn them off entirely.
-
-# Anatomy
-
-* Title
- * Short, clear statement of feature or what’s happening
- * Max length 32 characters
-* Body
- * Supporting detail or call-to-action
- * Max length 128 characters
-* targetURL
- * URL to open when the user clicks the notification
- * Max length 1024 characters.Must be on the same domain as the Mini App.
-
-
-# Best practices
-
-1. **Keep notifications short and clear**
- Each notification should be easy to scan. Use the title to state the key details, and keep the body text brief and focused on value. Users should know at a glance what is happening and why it matters.
-
-2. **Control frequency**
- Send notifications sparingly. Stay well below the enforced limit (1 every 30 seconds, maximum 100 per day) to avoid users from turning off notifications from your mini app. Focus on moments that truly benefit the user, and avoid sending multiple alerts close together.
-
-3. **Deliver at the right time**
- Timing shapes how notifications feel. Send them when they’re most relevant, such as after an event or during active hours. Avoid off-hours or interrupting while users are already in your mini app. Well-timed notifications feel helpful, not disruptive.
-
-4. **Measure and refine**
- Analytics reveal whether your notifications are working. High click-through rates show value, rising disabled rates mean you’re overwhelming users. Use these signals to adjust content, timing, or cadence so notifications remain useful.
-
-# Types of notifications
-
-Different mini apps use notifications in different ways. Choose the type that best fits your app’s purpose, and always keep the message relevant.
-
-* **Reminders** encourage users to return regularly
- * “Your crops are ready to harvest\!
-* **Events driven updates** highlight something new or time sensitive.
- * “BTC is up 5% today\! Check your portfolio”
-* **Feature announcements** showcase new functionality or opportunities
- * Example: “New quest unlocked\! More Coins are waiting for you\!”
-* **Alerts/warnings** share urgent or critical information
- * Example: “Your balance is low. Top up to keep trading”
-
-
-Not every message deserves to be a notification, here are some to avoid:
-
-* **Avoid overly generic nudges**. Messages with no clear value feel spammy, always explain why it matter to the user
- * Example: “Open the app today\!”
-* **Avoid unnecessary confirmations**. Notifications should only confirm meaningful or irreversible events like payments or shipments
- * Example: “You liked a post”
\ No newline at end of file
diff --git a/docs/apps/featured-guidelines/overview.mdx b/docs/apps/featured-guidelines/overview.mdx
deleted file mode 100644
index d80bc7610..000000000
--- a/docs/apps/featured-guidelines/overview.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-hidden: true
-title: "Featured Checklist"
-description: "Build high quality mini apps to get more distribution."
----
-
-Your app must meet all product, design, and technical guidelines outlined below. Meeting these guidelines is a prerequisite for featured placement, but __does not guarantee placement__. Base holds a very high bar for featured placement.
-
-
-
- 
-
-
-
-## User Information & Privacy
-
-* Only ask for personal information when absolutely necessary. Give users context and explain the value of using the app **before** asking for private information.
-* Always explain why the information is needed. Respect user privacy and data minimization principles.
-
-## User Profile
-
-* Show the user’s profile somewhere on the screen, and include their avatar and username used on the Base app
-* **Avoid showing 0x addresses in your mini app.**
-
-## App Description
-
-* Your mini app should have a clear, simple value proposition that makes sense to anyone.
-* Describe what your app does and why it matters in one sentence.
-* **Keep your messaging human, concise, and benefit-focused.**
-
-***Examples**:* “Earn and borrow on your terms”, “Create and share art that lives onchain”
-
-## App Cover Photo
-
-**Do’s ✅**
-
-* Your app’s visuals should make users want to click in and explore.
-* Include a high-quality cover image that feels trustworthy and engaging.
-* Ensure no typos or visual clutter in the image.
-
-**Don’ts ❌**
-
-* Include the Base logo in your cover photo.
-* Include photos of your team
-
-
-
-
- 
-
-
-
-## App Icon
-
-* **Design clear, recognizable icons:** Use bold, simple shapes and high contrast; avoid fine details so icons remain clear at **16×16px**.
-* **Follow icon specs**
- * Size: **1024×1024px**
- * Format: **PNG (no alpha transparency)**
- * Defined via `iconUrl` in `farcaster.json`
-
diff --git a/docs/apps/featured-guidelines/technical-guidelines.mdx b/docs/apps/featured-guidelines/technical-guidelines.mdx
deleted file mode 100644
index 80cbf94ef..000000000
--- a/docs/apps/featured-guidelines/technical-guidelines.mdx
+++ /dev/null
@@ -1,79 +0,0 @@
----
-hidden: true
-title: "Technical Guidelines"
-description: "Ensure your mini app is built for the Base app"
----
-
-## Complete Metadata
-
-Metadata includes your manifest and embed metadata. Complete, valid metadata is required for indexing, category placement, and high‑quality embeds.
-
-**Acceptance Criteria**
-- Manifest is publicly accessible at `/.well-known/farcaster.json`
-- Required fields are present and valid (`accountAssociation`, `frame`, `primaryCategory`, `tags`)
-- Images meet size/format constraints; text fields respect length limits
-
-**How to Implement**
-- Follow the [Manifest guide](/mini-apps/core-concepts/manifest)
-- Implement [embed metadata](/mini-apps/core-concepts/embeds-and-previews#implementation)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-As more people interact with these apps, they create valuable user activity and market opportunities that attract talented builders to Base, who see the engaged audience and build even better, more innovative experiences to capture that demand.This self-reinforcing cycle means every successful app strengthens the entire network, creating exponential growth that benefits every builder on Base.
-
-
-
-## What You Can Build
-
-The most successful Mini Apps solve everyday problems with built-in social mechanics:
-
-
-
- 4. Click on the "Verify" button that appears and follow the instructions to generate the `accountAssociation` fields.
- 5. Copy the `accountAssociation` object
-
-
-
-
-
-
-**Intent (coinbase.com/intent:1.0)**
-
-Purpose: User expresses choice from Quick Actions
-
-Structure:
-
-```typescript IntentContent
-type IntentContent = {
- id: string;
- actionId: string;
- metadata?: Record
-
-
-
-## Transaction trays
-
-If you would like to display agent information such as favicon and branded title, utilize the metadata property of wallet send calls data.
-
-**Example: Display agent information**
-
-```ts Wallet send calls data
-// example of wallet send calls data shape
-{
- version: "1.0",
- from: request.from as `0x${string}`,
- chainId: this.networkConfig.chainId,
- calls: [
- {
- ...
- metadata: {
- description: "Transfer token",
- ...other fields,
- hostname: "tba.chat",
- faviconUrl: "https://tba.chat/favicon",
- title: "Your favorite Agent"
- }
- }
- ]
-}
-```
-
-
- 
-
-
-You can send "GM" to **tbachat.base.eth** to get more details about message content types we support and get the firsthand experience on by interacting with our agent
-
-
-
-
-
- );
-}
-```
-
-
-
-
- 
- {/* Your component */}
;
-}
-```
-
-## Supported Chains
-
-- Base
-- Mainnet
-- Optimism
-- Arbitrum
-- Polygon
-- Zora
-- BNB
-- Avalanche C‑Chain
-
-
-We are actively expanding compatibility and will update this page as support increases.
-
-
-
diff --git a/docs/apps/troubleshooting/common-issues.mdx b/docs/apps/troubleshooting/common-issues.mdx
deleted file mode 100644
index 826fc341d..000000000
--- a/docs/apps/troubleshooting/common-issues.mdx
+++ /dev/null
@@ -1,243 +0,0 @@
----
-hidden: true
-title: Common Issues & Debugging
-description: Frequent issues encountered during Mini App development and their solutions
----
-
-## Prerequisites & Setup Verification
-
-Ensure your Mini App has the foundational requirements in place.
-
-### Required Files and Structure
-
-```text
-your-domain.com/
-├── .well-known/
-│ └── farcaster.json # Required manifest file
-├── your-app/
-│ ├── index.html # Your app entry point
-│ └── ... # Your app files
-```
-
-### Environment Setup Checklist
-
-- Domain is accessible via HTTPS
-- Manifest file exists at `/.well-known/farcaster.json`
-- All image URLs are publicly accessible
-
-# Debugging
-Use Base Build's built-in Preview Tool for foundational debugging.
-
-
- {walletConnected && (
-
- );
-}
-```
-
-
-
-### 5. Gesture Conflicts and App Dismissal Issues
-
-Disable native gestures when calling ready if you use swipe/drag interactions:
-
-```ts App.tsx
-await sdk.actions.ready({ disableNativeGestures: true });
-```
-
-### 6. Mobile Testing & Debugging
-
-**Eruda Mobile Console Setup:**
-
-Add Eruda for mobile console debugging during development:
-
-```tsx App.tsx
-import { useEffect } from 'react';
-
-export default function App() {
- useEffect(() => {
- // Only load Eruda in development and not on localhost
- if (typeof window !== 'undefined' &&
- process.env.NODE_ENV === 'development' &&
- !window.location.hostname.includes('localhost')) {
- import('eruda').then((eruda) => eruda.default.init());
- }
- }, []);
-
- return (
- Wallet: {userAddress}
- )} - {/* Use wallet data for secure operations */} -
- {/* Your app content */}
-
- );
-}
-```
-
-**Mobile Testing Workflow:**
-
-1. Deploy to production or use ngrok for local testing
-2. Share the mini app in a Farcaster DM to yourself
-3. Open in mobile client (Base App, Farcaster)
-4. Use Eruda console for debugging on mobile
-5. Test across multiple clients for compatibility
-
-**Testing Checklist:**
-
-- [ ] App loads correctly on mobile devices
-- [ ] Touch interactions work properly
-- [ ] Viewport is correctly sized
-- [ ] Images load and display correctly
-- [ ] Console shows no critical errors
-
-### 7. Your app is being flagged as unsafe?
-
-Base Account relies on the [Blockaid](https://blockaid.io/) platform to flag apps as unsafe.
-If your app is being flagged as unsafe or if you are concerned about your app being flagged as unsafe, you can follow the steps below to resolve the issue:
-
-1. Navigate to [Blockaid Reporting Portal](https://report.blockaid.io/).
-2. Submit a "mistake" or "developer" report.
-3. Follow the instructions provided by Blockaid to resolve the issue.
-4. If you are unable to resolve the issue, you can contact the Base core team on [Discord](https://discord.com/invite/buildonbase) for support.
-
-
-## Advanced Troubleshooting
-
-**CBW Validator Tool:**
-
-Use the Coinbase Wallet validator for Base App compatibility analysis. This AI-powered tool can identify unsupported patterns and suggest improvements.
-
-**Complete Manifest Example:**
-
-```json farcaster.json
-{
- "accountAssociation": {
- "header": "your-farcaster-header",
- "payload": "your-farcaster-payload",
- "signature": "your-farcaster-signature"
- },
- "frame": {
- "name": "Your Mini App",
- "iconUrl": "https://yourapp.com/icon.png",
- "homeUrl": "https://yourapp.com",
- "imageUrl": "https://yourapp.com/og.png",
- "buttonTitle": "Launch App",
- "description": "Your app description under 130 characters",
- "primaryCategory": "social",
- "tags": ["tag1", "tag2"]
- }
-}
-```
-
-## Success Verification
-
-Basic functionality and discovery/sharing checklists: confirm load, images, wallet, manifest endpoint, embed rendering, and search presence.
-
-## Getting Additional Help
-
-- [Base Build Preview Tool](https://base.dev/preview)
-- JSONLint
-- [Eruda](https://github.com/liriliri/eruda)
-- Base Discord — #minikit channel
-
-
-
diff --git a/docs/apps/troubleshooting/error-handling.mdx b/docs/apps/troubleshooting/error-handling.mdx
deleted file mode 100644
index 78a37725a..000000000
--- a/docs/apps/troubleshooting/error-handling.mdx
+++ /dev/null
@@ -1,9 +0,0 @@
----
-hidden: true
-title: Error Handling
-description: Patterns for surfacing and resolving common runtime errors in Mini Apps
----
-
-TODO: Provide guidance on handling errors from hooks, network issues, and manifest/metadata failures.
-
-
diff --git a/docs/apps/troubleshooting/how-search-works.mdx b/docs/apps/troubleshooting/how-search-works.mdx
deleted file mode 100644
index 9078a4cc1..000000000
--- a/docs/apps/troubleshooting/how-search-works.mdx
+++ /dev/null
@@ -1,81 +0,0 @@
----
-hidden: true
-title: How Search works
-description: If your Mini App isn't appearing in the Base app, this guide explains how indexing and search work so you can identify and fix the issue.
----
-Indexing is how The Base app adds your Mini App to its catalog, making it discoverable through search and browsing.
-Unlike traditional app stores with manual submission, you control when indexing happens. Share your Mini App URL to the social feed, and indexing starts automatically—no review process required.
-
-## How indexing works
-
-Understanding the indexing process helps you diagnose why your Mini App may not be appearing.
-
-
-
-
-
-
-
-
-
-
-### Direct messages
-
-When users share your Mini App URL in a direct message, it displays as an interactive embed. Recipients can preview and open your app directly from the conversation, with `context.location` set to `messaging` so you can customize the experience for shared discovery.
-
-## Related
-
-