Sabitlenmiş Tweet
Base is moving away from Farcaster Mini Apps → toward standard web apps.
This is one of the biggest developer experience updates happening in the @base ecosystem right now.
Here’s a breakdown of what’s changing, why it matters, and how builders should migrate their apps.
🧵
For a long time, apps inside the @base App relied on the Farcaster mini-app spec.
This meant builders had to use:
• Farcaster manifests
• Neynar notifications
• Farcaster SDK methods
• FID-based identity
While powerful, this introduced additional complexity in the developer stack.
Now the team behind Base is simplifying everything.
The new direction:
Standard web apps + wallet connectivity, No custom mini-app spec required.
Instead of building around Farcaster infrastructure, apps will now run as regular web applications inside the @baseapp in-app browser.
What’s Changing
The Base App is transitioning to a unified web native architecture.
Previously:
• App metadata came from Farcaster manifest files
• Notifications used Neynar webhooks and FIDs
• Identity was tied to Farcaster accounts
• Developers relied on Farcaster SDK methods
Now:
• Metadata is managed directly through Base.dev
• Notifications are sent via a Base.dev Notifications API
• Identity comes from wallet addresses
• Authentication uses Sign-In with Ethereum (SIWE)
• Wallet connectivity is handled using wagmi + viem
In short:
Base Apps are becoming standard Web3 applications.
Why Base is Making This Change
The goal is simple: reduce complexity for builders.
Maintaining multiple frameworks (Farcaster specs, SDKs, manifests, etc.) created unnecessary overhead.
By standardizing on web native tooling, developers can now build using the same stack they already use for Web3 apps.
That means:
• fewer custom specs
• easier onboarding for developers
• faster iteration cycles
• simpler infrastructure
Key Migration Deadline
April 9
After this date:
• Farcaster mini-app specs will no longer function inside the Base App
• Neynar-powered notifications will stop working
• Apps relying on Farcaster SDK methods must migrate
The Base App will treat all applications as standard web apps regardless of Farcaster manifests.
What Builders Need To Do
If you already have a web app, migration is minimal.
Here’s the core checklist:
1. Remove Farcaster SDK dependencies
2. Replace Farcaster auth with SIWE
3. Use wagmi + viem for wallet connectivity
4. Register your project on Base.dev
5. Move metadata (icon, screenshots, description) to the Base.dev dashboard
6. Migrate notifications to the Base.dev Notifications API
The Base docs also provide a migration skill for AI coding agents to automate this process.
Developers can run:
npx skills add base/skills
This installs a migration tool that maps deprecated Farcaster methods to modern web3 equivalents.
Identity Model Is Changing
Previously:
User identity → Farcaster FID
Now:
User identity → Wallet Address
Developers can retrieve the connected wallet address using wagmi hooks like:
useAccount()
This wallet native approach simplifies authentication and aligns with Web3 standards.
Also the new Notifications changes introduces a Base.dev Notifications API, this Notifications will now be delivered directly to wallet addresses for users who opt in, This centralizes metadata, notifications, and distribution inside the Base developer platform.
Wants to get more information about this Changes ??
Read >> x.com/i/status/20321…
Docs ; docs.base.org/mini-apps/quic…
Happy Building On Base
English
