Skip to main content
After April 9, 2026, the Base App treats all apps as standard web apps regardless of Farcaster manifests. Use the migration paths below to get your app working correctly in the Base App.
Using an AI coding agent? Install the Migration Skill to let your agent handle this migration automatically. Run npx skills add base/skills and ask your agent to migrate your Farcaster app to a standard web app.

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.

Choose your migration path

Let your agent handle this. Install the Migration Skill with npx skills add base/skills and ask your agent to migrate your Farcaster app to a standard web app. The skill maps deprecated SDK methods, replaces auth and wallet logic, and wires up the Base App path automatically.
Your app uses the Farcaster SDK. The migration replaces Farcaster-specific auth, identity, and actions with standard web equivalents.
1

Add the standard web stack

Install wagmi, viem, and React Query if you don’t have them already:
Terminal
Create a wagmi config for Base and wrap your app with WagmiProvider and QueryClientProvider:
config.ts
App.tsx
This replaces the Farcaster frame connector with standard wagmi providers that work in the Base app’s in-app browser.
2

Replace auth and identity

Farcaster sign-in and FID-based identity are not available in the Base App. Replace them with SIWE for authentication and the connected wallet address for user identity.Build, sign, and verify the SIWE message:
SignIn.tsx
This example verifies the signature client-side. If your app needs server-side sessions or replay protection, see the Authenticate users guide for the full pattern with server-issued nonces, backend verification.
Use useAccount from wagmi to read the connected wallet address as the user’s identity and guard SIWE execution until the wallet and chain are available.
3

Review SDK method compatibility

See the compatibility table for what will and won’t work in the Base app, along with standard web alternatives.
4

Migrate notifications to Base.dev

Farcaster-based notifications (via Neynar, FIDs, or tokens) will not reach Base App users. Follow the Notifications guide to fetch opted-in wallet addresses and send notifications through the Base Dashboard API.
5

Register on Base.dev

If you haven’t registered yet, create a project at Base.dev and complete your app metadata: name, icon, tagline, description, screenshots, category, primary URL, and builder code. Already registered apps do not need to re-register or update metadata.

Deprecated Farcaster SDK methods in the Base App

The following Farcaster mini-app SDK methods are not invoked by the Base App after April 9, 2026. Migrate to the alternatives listed.

Pre-flight checklist

Before considering your app migrated, verify the following:
1

Wallet and auth use wagmi + viem

Wallet connection and contract interactions use wagmi + viem. Authentication uses SIWE where needed.
2

Register and complete Base.dev metadata

Project is registered on Base.dev with primary URL set. Name, icon, tagline, screenshots, category, description, and builder code are all filled in.
3

Notifications use Base.dev API (if applicable)

Notifications are sent by wallet address using the Notifications guide, not through Neynar, FIDs, or tokens.
If all steps above are complete, your app is ready for the Base App as a standard web app.