--- name: convert-farcaster-miniapp-to-app-1144b2e00fb5 description: Converts Farcaster miniapp SDK projects into regular Base/web apps. Starts with an interactive quiz to choose between the default regular-app conversion and a narrowly isolated Farcaster surface when something truly needs to remain separate. Handles wagmi connectors, providers, auth, SDK actions, manifest routes, meta tags, dependencies, and read-only preservation. --- # Convert Farcaster Miniapp to Base App Convert a Farcaster miniapp into a normal app on Base. The default outcome is a regular web app that works in the Base app browser and on the open web, with Farcaster Mini App host coupling removed. If some Farcaster functionality truly needs to survive, keep it separate from the main app surface. Prefer read-only data first. Only preserve Mini App-specific behavior when the user explicitly insists, and isolate it behind a dedicated route or page rather than carrying it through the whole app. ## Core Principle Always separate these decisions: 1. Remove Mini App host/runtime coupling. 2. Decide whether any Farcaster-facing functionality should remain. 3. If something remains, keep it isolated from the main app and avoid introducing new vendor dependencies by default. Do **not** automatically turn "keep some Farcaster functionality" into "migrate to Neynar." If a project already uses Neynar and the user wants to keep an isolated Farcaster-only area, you may preserve that existing integration. Do not introduce new Neynar adoption as the default recommendation. ## Quick Start Follow these five phases sequentially: 0. **Discovery** — Quick scan + quiz to choose a path 1. **Analysis** — Detailed read-only analysis scoped to the chosen path 2. **Conversion** — Remove Mini App SDK patterns and isolate any intentionally preserved Farcaster surface 3. **Cleanup** — Remove dead code, env vars, and dependencies 4. **Verification** — Type check, build, and summarize ## Conversion Paths The quiz should route the user into one of two paths: | Path | Name | Who it's for | What happens | |------|------|-------------|-------------| | **A** | Regular App Default | Most projects | Strip Farcaster Mini App coupling and become a normal Base/web app | | **B** | Isolated Farcaster Surface | The app still needs a small Farcaster-specific area | Convert the main app into a normal app, then keep only a separate Farcaster route/page for the remaining functionality | `Path B` is still biased toward removing complexity: - Prefer **read-only** Farcaster data. - Avoid preserving Mini App host/runtime behavior unless the user explicitly asks for it. - Keep any preserved Farcaster logic out of the main app shell, shared providers, and primary auth flow. --- ## Phase 0: Discovery ### 0A. Quick Scan (automated, no user interaction) Run a lightweight scan before asking questions. Produce an internal tally: 1. **Detect framework** from `package.json` (`next`, `vite`, `react-scripts`, `@remix-run/*`) 2. **Count Farcaster packages** in `dependencies` and `devDependencies` 3. **Grep source files** (`.ts`, `.tsx`, `.js`, `.jsx`) for: - `sdk.actions.*` calls (count total) - `sdk.quickAuth` usage (yes/no) - `sdk.context` usage (yes/no) - `.well-known/farcaster.json` (yes/no) - `farcasterMiniApp` / `miniAppConnector` connector (yes/no) - Total files with any `@farcaster/` import - `@neynar/` imports or `api.neynar.com` fetch calls (yes/no) 4. **Identify the blast radius**: - Are Farcaster references spread across the main app shell? - Are they already mostly confined to a route like `app/farcaster/`, `pages/farcaster/`, or a small set of components? - Are there obvious host-only features such as haptics, notifications, `openMiniApp`, or `sdk.context.client`? Use this tally to inform quiz suggestions. Do **not** dump raw scan output to the user before asking the quiz. ### 0B. Interactive Quiz Ask these questions one at a time. Use the quick scan results to suggest the most likely answer. **Q1** (always ask): > Based on my scan, your project has [X] files using the Farcaster SDK with [summary of what is used]. > > Which outcome do you want? > - **(a) Regular app everywhere** — remove Farcaster-specific behavior and just keep a normal Base/web app > - **(b) Regular app first, plus a separate Farcaster area** — keep the main app clean, but preserve a small isolated route/page if really needed **Q2** (always ask): > How deeply is the Mini App SDK used today? > - **(a) Minimal** — mostly `sdk.actions.ready()` and a few helpers > - **(b) Moderate** — some `context`, `openUrl`, profile links, or conditional `isInMiniApp` logic > - **(c) Heavy** — auth, wallet connector, notifications, compose flows, or host-specific behavior **Q3** (ask if Q1 = b): > What is the smallest Farcaster feature set you actually need to preserve? > - **(a) Read-only only** — profile or cast display, links out to Farcaster profiles, maybe a small social page > - **(b) Some Farcaster-specific interactions** — there is a separate page/path that still needs more than read-only behavior > - **(c) Not sure** — analyze what is isolated already and recommend the smallest keep-surface possible **Q4** (ask if Q1 = b and there is existing isolated Farcaster code or existing Neynar usage): > Does the project already have an isolated Farcaster-only route/page or integration that you want to keep as-is if possible? > - **(a) Yes** — preserve only that isolated surface > - **(b) No** — prefer removing it unless there is a very strong reason to keep it **Q5** (ask if quick auth or other Mini App auth is present): > After conversion, what should the main app use for authentication? > - **(a) SIWE** — wallet-based auth for the regular app > - **(b) Existing non-Farcaster auth** — keep whatever normal web auth already exists > - **(c) No auth** — remove auth entirely ### 0C. Path Selection Map answers to a path: | Desired outcome | Typical result | |-----------------|----------------| | `Q1 = regular app everywhere` | **Path A** — Regular App Default | | `Q1 = regular app first, plus separate Farcaster area` | **Path B** — Isolated Farcaster Surface | Then tighten the recommendation: - If the user chose `Path B`, prefer **read-only preservation** unless they explicitly require something else. - If the scan shows heavy host/runtime coupling but the user wants `Path A`, warn them that some features will be deleted rather than recreated. - If the project already uses Neynar, only keep it if it remains inside the isolated Farcaster surface. Do not expand it into the main app. Announce the chosen path: > Based on your answers, I'll use **Path [X]: [Name]**. This will [one-sentence description]. I'll now do a detailed analysis of your project. Record the quiz answers internally. They guide whether the agent should: - fully remove Farcaster features - preserve only a read-only isolated surface - quarantine any unavoidable Farcaster-specific logic to a dedicated route/page **Proceed to Phase 1.** --- ## Phase 1: Analysis (Read-Only) ### 1A. Detect Framework Read `package.json`: - `next` → Next.js - `vite` → Vite - `react-scripts` → Create React App - `@remix-run/*` → Remix ### 1B. Scan for Farcaster Dependencies List all packages matching: - `@farcaster/miniapp-sdk`, `@farcaster/miniapp-core`, `@farcaster/miniapp-wagmi-connector` - `@farcaster/frame-sdk`, `@farcaster/frame-wagmi-connector` - `@farcaster/quick-auth`, `@farcaster/auth-kit` - `@neynar/*` (compatibility only; do not assume it stays) ### 1C. Grep for Farcaster Code Search source files (`.ts`, `.tsx`, `.js`, `.jsx`) for: **SDK imports:** ``` @farcaster/miniapp-sdk @farcaster/miniapp-core @farcaster/miniapp-wagmi-connector @farcaster/frame-sdk @farcaster/frame-wagmi-connector @farcaster/quick-auth @farcaster/auth-kit @neynar/ ``` **SDK calls:** ``` sdk.actions.ready sdk.actions.openUrl sdk.actions.close sdk.actions.composeCast sdk.actions.addMiniApp sdk.actions.requestWalletAddress sdk.actions.viewProfile sdk.actions.viewToken sdk.actions.sendToken sdk.actions.swapToken sdk.actions.signIn sdk.actions.setPrimaryButton sdk.actions.openMiniApp sdk.quickAuth sdk.context sdk.isInMiniApp sdk.getCapabilities sdk.haptics sdk.back sdk.wallet ``` **Connectors & providers:** ``` farcasterMiniApp() miniAppConnector() farcasterFrame() MiniAppProvider MiniAppContext useMiniApp useMiniAppContext ``` **Manifest & meta:** ``` .well-known/farcaster.json fc:miniapp fc:frame ``` **Environment variables:** ``` NEYNAR_API_KEY NEXT_PUBLIC_NEYNAR_CLIENT_ID FARCASTER_ FC_ ``` ### 1D. Check Existing Web3 Setup Look for: - `coinbaseWallet` connector in wagmi config - SIWE / `siwe` package usage - `connectkit`, `rainbowkit`, or `@coinbase/onchainkit` - Existing wallet connection UI ### 1E. Check Separation Boundaries Map where Farcaster logic currently lives: - Root providers or app shell - Shared hooks or auth middleware - One-off components - Dedicated routes/pages like `app/farcaster/*` - Server routes used only by Farcaster functionality Mark each location with one action: - **remove** - **stub** - **move behind isolated route/page** - **keep only as read-only** ### 1F. Report Findings Create a path-scoped summary. **All paths include:** ``` ## Conversion Analysis — Path [X]: [Name] **Framework:** [detected] **Farcaster packages:** [list] **Files with Farcaster code:** [count] ### Wagmi Connector - File: [path] - Current connector: [farcasterMiniApp / miniAppConnector / farcasterFrame / none] - Other connectors: [list] - Action: [replace with coinbaseWallet / leave existing wallet setup / remove only] ### MiniApp Provider - File: [path] - Pattern: [simple / complex] - Consumers: [files importing from this] - Action: [stub / remove / isolate] ### SDK Action Calls [list each: file, what it does, action] ### Manifest & Meta - Manifest route: [path or N/A] - Meta tags: [file or N/A] ``` **Path A additionally includes:** ``` ### Main App Outcome - Action: remove Farcaster-specific UI and flows from the main app entirely ### Authentication - Quick Auth used: [yes/no, file] - Action: replace with SIWE / keep existing non-Farcaster auth / remove ### Existing Neynar Usage - Package or files: [list or N/A] - Action: remove entirely unless the user later re-scopes to Path B ### Environment Variables [list all FC/Neynar vars that will be removed] ``` **Path B additionally includes:** ``` ### Main App Outcome - Action: convert the main app into a normal web app first ### Isolated Farcaster Surface - Route/page to keep: [path or proposed path] - Scope: [read-only / mixed / host-specific] - Recommended target scope: [prefer read-only / quarantine existing behavior / remove] ### Authentication - Quick Auth used: [yes/no, file] - Main app action: replace with SIWE / keep existing non-Farcaster auth / remove - Isolated Farcaster surface action: [remove auth coupling / preserve existing isolated flow only if explicitly requested] ### Existing Neynar Usage - Package or files: [list or N/A] - Action: [remove / keep only inside isolated surface] ### Environment Variables - Remove from main app: [FC_*, FARCASTER_*, etc.] - Keep only if isolated surface truly still needs them: [NEYNAR_API_KEY, etc. or N/A] ``` **All paths end with:** ``` ### Potential Issues - [ ] FID used as database primary key - [ ] Farcaster colors in tailwind config - [ ] `isInMiniApp` branches with unique else logic - [ ] Components only meaningful inside Farcaster - [ ] Farcaster code mixed into shared providers or root layout ``` Ask: > Does this analysis look correct? Ready to proceed with conversion? **STOP and wait for user confirmation before Phase 2.** --- ## Phase 2: Conversion Steps are organized by feature area. Each step notes which paths it applies to and what to do differently for `Path B`. ### 2A. Wagmi Connector (All Paths) Find the wagmi config file (`lib/wagmi.ts`, `config/wagmi.ts`, `providers/wagmi-provider.tsx`, etc.): 1. Remove import of `farcasterMiniApp` or `miniAppConnector` from `@farcaster/miniapp-wagmi-connector` 2. Remove the `farcasterMiniApp()` / `miniAppConnector()` call from the `connectors` array 3. If no wallet connector remains, add: ```typescript import { coinbaseWallet } from "wagmi/connectors"; coinbaseWallet({ appName: "" }) ``` 4. If `coinbaseWallet` already exists, leave it as-is 5. Clean up empty lines and stale imports Skip this step if wagmi is not in the project. ### 2B. MiniApp Provider / Context (All Paths) If the app has a shared Mini App provider, remove host/runtime assumptions from the main app. **Pattern A: simple provider** Replace with a safe stub: ```tsx 'use client' import React, { createContext, useContext, useMemo } from "react"; interface MiniAppContextType { context: undefined; ready: boolean; isInMiniApp: boolean; } const MiniAppContext = createContext(undefined); export function useMiniAppContext() { const context = useContext(MiniAppContext); if (context === undefined) { throw new Error("useMiniAppContext must be used within a MiniAppProvider"); } return context; } export default function MiniAppProvider({ children }: { children: React.ReactNode }) { const value = useMemo( () => ({ context: undefined, ready: true, isInMiniApp: false, }), [] ); return {children}; } ``` Preserve export style and hook names so consumers do not break. **Pattern B: complex provider** - If many consumers depend on it, stub it first. - If only a few files use it, remove it and update those imports directly. - In `Path B`, do not let the isolated Farcaster surface keep this provider wired through the root app shell. If needed, make it local to the isolated route only. ### 2C. Authentication The main app should use normal web auth, not Mini App auth. **Default rule for both paths:** - If `sdk.quickAuth.getToken()` is used, replace it with SIWE or remove it. - If a normal non-Farcaster auth system already exists, prefer that over adding new auth. - Do not introduce new Farcaster or Neynar auth as the default conversion target. #### SIWE Replacement Pattern **Client-side** (e.g. `useSignIn.ts`): - Remove `import sdk from "@farcaster/miniapp-sdk"` - Remove `sdk.quickAuth.getToken()` - Replace with: 1. Get wallet address from `useAccount()` (wagmi) 2. Create a SIWE message with `siwe` 3. Sign with `useSignMessage()` (wagmi) 4. Send signature + message to the backend for verification **Server-side** (e.g. `app/api/auth/sign-in/route.ts`): - Remove `@farcaster/quick-auth` verification - Replace with SIWE verification: 1. Parse the SIWE message 2. Verify the signature with `siwe` or `viem` 3. Use recovered wallet address as the normal app identity **If FID is used as a database primary key:** - Do not auto-change schema - Add a TODO comment for later migration - Warn in Phase 4 summary **Path B note:** - If the isolated Farcaster surface already has its own auth or integration flow and the user explicitly wants to keep it, quarantine it there only. - Do not let that flow remain the default app-wide auth system. ### 2D. SDK Action Calls #### 2D-1. Main replacements for both paths | Original | Replacement | |----------|-------------| | `sdk.actions.ready()` | Remove entirely | | `sdk.actions.openUrl(url)` | `window.open(url, "_blank")` | | `sdk.actions.close()` | `window.close()` or remove | | `sdk.actions.composeCast(...)` | Remove from the main app | | `sdk.actions.addMiniApp()` | Remove call and UI | | `sdk.actions.requestWalletAddress()` | Remove; wagmi handles wallet access | | `sdk.actions.viewProfile(fid)` | `window.open(\`https://warpcast.com/~/profiles/${fid}\`, "_blank")` | | `sdk.actions.viewToken(opts)` | `window.open(\`https://basescan.org/token/${opts.token}\`, "_blank")` | | `sdk.actions.sendToken(opts)` | Replace with wagmi flow if the feature matters, otherwise remove | | `sdk.actions.swapToken(opts)` | Remove call and UI unless there is a real app-specific swap feature outside Farcaster | | `sdk.actions.signIn(...)` | Remove; auth handled by normal web auth | | `sdk.actions.setPrimaryButton(...)` | Remove entirely | | `sdk.actions.openMiniApp(...)` | Remove from the main app | | `sdk.isInMiniApp()` | Remove conditional and keep the non-Farcaster branch | | `sdk.context` | Remove from the main app | | `sdk.getCapabilities()` | Remove or replace with `async () => []` | | `sdk.haptics.*` | Remove entirely | | `sdk.back.*` | Remove entirely | | `sdk.wallet.*` | Remove; wagmi handles wallet access | For conditional `isInMiniApp` branches: ```tsx // BEFORE if (isInMiniApp) { sdk.actions.openUrl(url); } else { window.open(url, "_blank"); } // AFTER window.open(url, "_blank"); ``` Always keep the normal web branch. #### 2D-2. Path B overrides `Path B` does **not** mean "recreate everything." It means "keep the main app clean and preserve the smallest separate Farcaster surface possible." - `sdk.context` - Remove from the main app - For the isolated surface, prefer replacing it with read-only fetched data or explicit route params - Remove `context.location`, `context.client`, safe area, and other host-derived assumptions unless the user explicitly insists on preserving a host-specific page - `sdk.actions.composeCast(...)` - Remove from the main app - If the user only needs read-only, delete it entirely - If they insist on preserving it, keep it isolated behind a dedicated page/path and flag it as a manual follow-up rather than rebuilding it by default - `sdk.actions.openMiniApp(...)` - Remove from the main app - Only keep it in an isolated route if the user explicitly wants a Farcaster-only surface - notifications / haptics / host buttons - Remove from the main app - Preserve only if the isolated route truly depends on them and the user has explicitly opted into that complexity ### 2E. Optional Read-Only Farcaster Data (Path B only) If the user wants an isolated Farcaster surface, prefer **read-only** data first. **Create `lib/farcaster-readonly.ts`** (or equivalent) only if the app needs it: ```typescript const HUB_URL = "https://hub.farcaster.xyz"; export async function getUserData(fid: number) { const res = await fetch(`${HUB_URL}/v1/userDataByFid?fid=${fid}`); if (!res.ok) throw new Error(`Hub user data fetch failed: ${res.status}`); return res.json(); } export async function getCastsByFid(fid: number, pageSize = 25) { const res = await fetch(`${HUB_URL}/v1/castsByFid?fid=${fid}&pageSize=${pageSize}`); if (!res.ok) throw new Error(`Hub casts fetch failed: ${res.status}`); return res.json(); } ``` Then: - Keep these calls inside the isolated route/page only - Do not thread Farcaster data requirements through the main app shell - If the project already has a small isolated Neynar-based read-only integration, you may keep it only if removing it would create more churn than it saves - Do not add new Neynar packages for this by default ### 2F. Manifest Route (All Paths) Delete `.well-known/farcaster.json` route: - `app/.well-known/farcaster.json/route.ts` - `public/.well-known/farcaster.json` - `api/farcaster-manifest.ts` or similar helpers If the `.well-known` directory becomes empty, delete it. ### 2G. Meta Tags (All Paths) In root layout or metadata files, remove: - `` tags with `property="fc:miniapp*"` or `property="fc:frame*"` - `Metadata.other` entries that only exist for Farcaster tags - `generateMetadata` logic that only produces Mini App metadata ### 2H. Dependencies **All paths — remove:** - `@farcaster/miniapp-sdk`, `@farcaster/miniapp-wagmi-connector`, `@farcaster/miniapp-core` - `@farcaster/frame-sdk`, `@farcaster/frame-wagmi-connector` - `@farcaster/quick-auth`, `@farcaster/auth-kit` **Path A — also remove:** - `@neynar/nodejs-sdk`, `@neynar/react` - any other Neynar packages or helpers **Path B — remove by default:** - `@neynar/nodejs-sdk`, `@neynar/react`, and Neynar helpers unless they remain inside the intentionally isolated Farcaster surface **All paths — add only if truly needed:** - `siwe` if SIWE auth is introduced and not already present Do not add new Neynar packages as part of the default conversion. ### 2I. Farcaster-Specific Routes & Components **Path A:** - Delete `app/farcaster/`, `pages/farcaster/`, and Farcaster-only components entirely - Delete Farcaster-only API routes such as `/api/farcaster/*` and `/api/neynar/*` - Remove any navigation links that point to deleted routes **Path B:** - Keep the main app route tree clean - Move preserved Farcaster UI behind one dedicated route/page if it is not already isolated - Prefer names like `app/farcaster/` or `app/social/` over spreading Farcaster logic throughout generic shared pages - Remove any component that has no purpose outside that isolated surface - Keep any remaining Neynar usage, if any, confined to that isolated route/page and its server helpers only --- ## Phase 3: Cleanup ### 3A. Update `package.json` **All paths — remove Mini App packages:** - `@farcaster/miniapp-sdk`, `@farcaster/miniapp-wagmi-connector`, `@farcaster/miniapp-core` - `@farcaster/frame-sdk`, `@farcaster/frame-wagmi-connector` - `@farcaster/quick-auth`, `@farcaster/auth-kit` **Path A — also remove:** - all `@neynar/*` packages **Path B — remove unless still isolated and intentionally preserved:** - `@neynar/*` **All paths — add if introduced:** - `siwe` ### 3B. Environment Variables **Path A — remove from all `.env*` files:** - `NEYNAR_API_KEY` - `NEXT_PUBLIC_NEYNAR_CLIENT_ID` - `FARCASTER_*` - `FC_*` - `NEXT_PUBLIC_FC_*` - `NEXT_PUBLIC_FARCASTER_*` **Path B — remove from the main app by default:** - `FARCASTER_*` - `FC_*` - `NEXT_PUBLIC_FC_*` - `NEXT_PUBLIC_FARCASTER_*` Only keep `NEYNAR_*` vars if the isolated surface explicitly still depends on existing Neynar integration. Also update env validation schemas (`env.ts`, `env.mjs`, zod schemas, etc.). ### 3C. Dead Code Cleanup - Remove unused imports from modified files - Remove unused Farcaster types and helper functions - Remove empty import statements - Remove dead hooks or API wrappers that only existed for the Mini App SDK ### 3D. Tailwind Colors If `tailwind.config.ts` or `tailwind.config.js` includes Farcaster brand colors such as `farcaster: "#8B5CF6"`, remove them unless that branding is intentionally kept inside an isolated Farcaster-only surface. ### 3E. Install Dependencies Tell the user: ```bash npm install ``` --- ## Phase 4: Verification ### 4A. Search for Remaining References **All paths — search for:** ``` @farcaster farcasterMiniApp miniAppConnector sdk.actions sdk.quickAuth sdk.context fc:miniapp fc:frame ``` **Path A — also search for:** ``` @neynar NEYNAR_API_KEY NEXT_PUBLIC_NEYNAR_CLIENT_ID api.neynar.com ``` **Path B — if Neynar was intentionally preserved:** - verify that remaining `@neynar` imports and env vars exist only inside the isolated Farcaster surface and its server helpers Report any source matches, ignoring `node_modules`, lock files, and git history. ### 4B. Type Check ```bash npx tsc --noEmit ``` Report and fix type errors. ### 4C. Build Check ```bash npm run build ``` Report and fix build errors. ### 4D. Conversion Summary ``` ## Conversion Complete — Path [X]: [Name] **Files modified:** [count] **Files deleted:** [count] **Files created:** [count, if any] **Packages removed:** [list] **Packages added:** [list, if any] ### What was done - [x] Removed Farcaster Mini App wagmi connector - [x] Stubbed or removed Mini App provider/context - [x] Replaced Mini App auth with normal web auth or removed it - [x] Removed or replaced SDK action calls - [x] Deleted manifest route - [x] Removed Farcaster meta tags - [x] Cleaned up dependencies and env vars ``` **Path B summary additionally includes:** ``` - [x] Kept the main app as a normal web app - [x] Confined remaining Farcaster functionality to a dedicated route/page - [x] Preferred read-only Farcaster data where possible - [x] Removed Farcaster host/runtime coupling from shared app infrastructure ``` **All paths end with:** ``` ### Manual steps - [ ] Run `npm install` - [ ] Test wallet connection flow - [ ] If FID migration is needed, migrate from FID-based identity to wallet address - [ ] If Path B preserves a Farcaster-only area, verify it stays isolated from the main app shell ### Verification - TypeScript: [pass/fail] - Build: [pass/fail] - Remaining Farcaster references: [none / list] ``` --- ## Edge Cases ### No wagmi Skip Phase 2A. Do not introduce wagmi unless the app actually needs wallet connectivity. ### No auth system Skip Phase 2C. Do not add SIWE unnecessarily. ### `@farcaster/frame-sdk` (older) Treat identically to `@farcaster/miniapp-sdk`. ### Monorepo Ask which workspace(s) to convert. Only modify those. ### FID as database primary key Do not change schema automatically. Flag it and warn in Phase 4. ### Conditional `isInMiniApp` branches Always keep the normal web branch and remove the Mini App branch. ### Components with no non-Farcaster purpose Delete them entirely in `Path A`. In `Path B`, keep them only if they live inside the isolated Farcaster route/page. ### Existing Neynar usage If the project already uses Neynar: - remove it in `Path A` - keep it only if it remains inside the isolated `Path B` surface - do not add more Neynar usage than already exists unless the user explicitly requests it ### Read-only is usually enough If the user says they want to "keep Farcaster stuff," bias toward: - profile links - read-only profile or cast display - a dedicated social page Do not assume they want write access, notifications, or host/runtime behavior. ### Quiz ambiguity If the scan and quiz conflict, point it out and ask the user to confirm the smaller keep-surface first. --- ## Security - **Validate wallet setup** — ensure `coinbaseWallet` or the chosen wallet connector is configured correctly - **FID-based identity** — requires manual database migration if used as a primary key - **SIWE verification** — verify signatures server-side before trusting them - **Preserved isolated surface** — do not let a Farcaster-only route/page leak host/runtime assumptions into the main app shell - **Existing Neynar usage** — keep API keys server-side only, and only if that isolated surface still depends on them --- Source attribution: jiayaoqijia Original project: https://github.com/jiayaoqijia/cryptoskill/blob/bcc0d208deaa4f1f80aa0df7ca26c4bed6318918/skills/chains/base-official-convert-farcaster-miniapp-to-app/SKILL.md License: AGPL-3.0-only License information: https://www.gnu.org/licenses/agpl-3.0.html Original upstream instructions; downloaded from Dave AI. ## Upstream license notice GNU AFFERO GENERAL PUBLIC LICENSE Version 3, 19 November 2007 Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software. A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate. Many developers of free software are heartened and encouraged by the resulting cooperation. However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public. The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version. An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals. This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU Affero General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Remote Network Interaction; Use with the GNU General Public License. Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program. If not, see . Also add information on how to contact you by electronic and paper mail. If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source. For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code. There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements. You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see . # Dave AI resource metadata Creator / publisher: jiayaoqijia Original project: https://github.com/jiayaoqijia/cryptoskill/blob/bcc0d208deaa4f1f80aa0df7ca26c4bed6318918/skills/chains/base-official-convert-farcaster-miniapp-to-app/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Product Management Roles: Backend Developer, Frontend Developer, Product Manager Specialties: Backend, Frontend Tools: Farcaster Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: b4b7e9fe6badc6c9671c69da97e26bc50883e07db78619ad3ae110c3781054bf