flare-dapp-pitfalls

What problem does it solve?

Hard-won, cross-project lessons from building, deploying, and operating Flare-family (Flare / Songbird / Coston2) dApps. Use this skill whenever the user is: deploying or interacting with a Flare/Songbird/Coston2 contract, building a frontend with RainbowKit + Wagmi for Flare chains, writing Foundry fork tests against Flare-family state, claiming or rotating FTSO reward redistributors, debugging a stuck or silently-failing transaction, choosing RPC endpoints for browser vs server use, or troubleshooting MetaMask / wallet connection on Flare. Trigger on any mention of: Flare RPC, Songbird canary, Coston2 testnet, FTSO reward claim, WNAT vote-power, FlareDrops, FtsoRewardRedistributor, FlaresRewardsRedistributorForNft, Enosys redistributor, RainbowKit MetaMask hang, Ankr origin locked, Multicall3 on Flare, EIP-150 63/64 gas, eth_getLogs 30-block cap, "why is my Flare contract test failing in CI", "why did my claim transaction return zero", "Wrap SGB to WSGB", or any question about gotchas specific to Flare-family chains.

Core Features & Use Cases

• Wallet integration and RainbowKit/Wagmi pitfalls
• RPC endpoint guidance for browser vs server usage
• Foundry fork-test patterns and CI gating
• Redistributor rotation cautions and ABI compatibility
• Frontend UX guidance for WNAT wrapping and 1:1 wrappers
• Deployment determinism and Ledger handoff patterns
• Frontend CI pitfalls and tests gating info

Quick Start

Review your Flare dApp workflow against this pitfall checklist and implement the recommended mitigations before deployment.