Flare Network

Flare Network — Deployment Registry

Authoritative addresses + endpoints for the Flare-family chains. For protocol architecture (FTSO, FDC, FAssets, Smart Accounts), see the flare-general skill. This skill answers "WHERE is X" questions — concrete addresses, RPC URLs, explorer endpoints, and verification commands.

If you're unsure whether something is in scope: this skill is for deployed contracts and network endpoints. Anything about how a protocol works lives in the protocol-specific skills (flare-ftso, flare-fassets, etc.).

Chain matrix

RPC endpoints

Public RPCs (rate-limited, 30-block eth_getLogs cap)

flare:    https://flare-api.flare.network/ext/C/rpc
songbird: https://songbird-api.flare.network/ext/C/rpc
coston2:  https://coston2-api.flare.network/ext/C/rpc
coston:   https://coston-api.flare.network/ext/C/rpc

Faster / paid alternatives

Origin lock note — a browser-locked Ankr key returns Origin not allowed (-32079) to curl / forge-script. Use the public RPC for deploys; reserve Ankr for browser code.

Block explorers

Flare

Songbird

Coston2

Verification command (Foundry)

Both explorer families work via forge verify-contract:

# Blockscout (no API key needed)
forge verify-contract \
  --rpc-url flare \
  --verifier blockscout \
  --verifier-url "https://flare-explorer.flare.network/api/" \
  --num-of-optimizations 200 --compiler-version 0.8.24 \
  --constructor-args $ENCODED_ARGS \
  $ADDRESS \
  src/MyContract.sol:MyContract

# Routescan / Etherscan-style (use literal "verifyContract" as the key)
forge verify-contract \
  --verifier etherscan \
  --verifier-url "https://api.routescan.io/v2/network/mainnet/evm/14/etherscan" \
  --etherscan-api-key "verifyContract" \
  --num-of-optimizations 200 --compiler-version 0.8.24 \
  --constructor-args $ENCODED_ARGS \
  $ADDRESS \
  src/MyContract.sol:MyContract

Constructor args go in via --constructor-args 0x.... Get them from the broadcast log: broadcast/Deploy.s.sol/<chainId>/run-latest.json → transactions[i].arguments, then cast abi-encode "constructor(...)" <args...> to encode.

Cross-chain infrastructure

Permit2 (Uniswap canonical)

0x000000000022D473030F116dDEE9F6B43aC78BA3 — deployed on Flare ONLY (chain 14). NOT deployed on Songbird, NOT deployed on Coston2. Verify via:

cast code 0x000000000022D473030F116dDEE9F6B43aC78BA3 --rpc-url <chain>
# Returns full bytecode on Flare; returns 0x on Songbird/Coston2

Implication: Permit2-dependent contracts (batch sweeps, signed-permit flows) cannot be canary-tested on Songbird. Either deploy your own Permit2 fork there (~3000 LOC), use mocks, or skip Songbird and validate via Flare fork tests only.

Multicall3

0xcA11bde05977b3631167028862bE2a173976CA11 on all Flare-family chains (Flare, Songbird, Coston2). Standard Multicall3 ABI. Useful for batched RPC reads.

When defining a custom chain in viem, you must explicitly register contracts.multicall3 or publicClient.multicall(...) will throw silently:

defineChain({
  id: 14,
  name: 'Flare',
  // ...
  contracts: {
    multicall3: {
      address: '0xcA11bde05977b3631167028862bE2a173976CA11',
      blockCreated: 3002461,
    },
  },
})

Tokens

Addresses are case-insensitive on the EVM but stored canonical-checksummed below.

Flare (chain 14)

Songbird (chain 19)

Coston2 (chain 114, testnet)

Token lists are not exhaustive — for the long tail (airdrops, dust), discover via the explorer's account.tokenlist API. For Flare:

curl -s "https://flare-explorer.flare.network/api?module=account&action=tokenlist&address=$WALLET"

Concentrated-liquidity DEXes

Three CLMM families on Flare today. Picking the right one depends on whether you need V3-shape (getPool(t0,t1,fee)) or Algebra-shape (poolByPair(t0,t1)) ABI.

Enosys V3 (Uniswap V3-compatible) — Flare

FTSO redistributor naming gotcha (Flare): the active NFT redistributor was rotated 2026-04 from FlaresRewardsRedistributorForNft (0x4410B821…) to FtsoRewardRedistributorForNft (0x5a0BfF8F…). Same ABI shape; only the address changed. Rewards accrued under the legacy contract are still claimable via direct calls — see enosys-dex-v3 for the address-allowlist recovery pattern.

Enosys V3 — Songbird

SparkDEX V3.1 (Uniswap V3-compatible, no FTSO redistributor) — Flare

LP fees still accrue; FTSO delegation rewards do not (no redistributor deployed for this fork). Position NFT lifecycle is otherwise identical to Enosys V3.

SparkDEX V4 (Algebra V1.9+ with plugins, dynamic fees) — Flare

Algebra differs from V3 in three places that matter when integrating:

1. Pool resolution — factory.poolByPair(token0, token1) (no fee tier).
2. Pool state — globalState() returns 6 fields (V3's slot0() returns 7), but tick is at index 1 in both.
3. MintParams has address deployer where V3 has uint24 fee. Pass address(0) to use the factory's default deployer (current SparkDEX V4 pattern). For non-default-deployer pools, you must pass the actual deployer address; verify by computing factory.computePoolAddress(t0, t1) matches the pool you're targeting.

V2 routers (Uniswap V2-compatible)

Flare

BlazeSwap quirk — its swapExactTokensForTokens checks amountOutMin against the actual recipient balance change, not the getAmountsOut quote. For fee-on-transfer tokens this means a quote-derived minOut will trip BlazeSwapRouter: INSUFFICIENT_OUTPUT_AMOUNT. See flare-security for the double-FoT-aware integration pattern.

Aggregators

OpenOcean

Function selector for swap: 0x90411a32 (signature swap(address,(SwapDescription),(uint256,uint256,uint256,bytes)[])). Do NOT guess this from the human-readable signature — verify against the actual returned calldata from the OO API:

curl -s '<OO API endpoint>' | jq -r '.data.data[2:10]'

OO API endpoint: https://open-api.openocean.finance/v3/{chainId}/swap_quote. Free, unauthenticated, ~$0.01 minimum-USD-value gate per quote (legs below that get rejected — fall back to V2 routers for dust).

Cross-chain bridges

LayerZero

LayerZero V2 endpoints are deployed on Flare and Songbird. For up-to-date contract addresses, see https://docs.layerzero.network/v2/deployments.

Stargate

Stargate v2 has Flare deployments for USDC and USDT0 routes. See https://stargateprotocol.gitbook.io/stargate.

Faucets (testnet only)

Common command snippets

Read deployed bytecode (verify a contract exists at an address)

cast code $ADDRESS --rpc-url flare
# returns 0x if no contract; full bytecode if deployed

Find deployed function selectors in a contract's dispatch table

cast code $ADDRESS --rpc-url flare | grep -oE '63[0-9a-f]{8}1461' | head
# 63XXXXXXXX14 = PUSH4 selector + EQ — that's the dispatcher's selector check

Decode a 4-byte selector into a function signature

cast 4byte 0x90411a32
# returns swap(address,(address,address,address,address,uint256,uint256,uint256,bytes),(uint256,uint256,uint256,bytes)[])

Pull constructor args from a Foundry broadcast log

node -e "console.log(JSON.stringify(require('./broadcast/Deploy.s.sol/14/run-latest.json').transactions.find(t => t.contractName === 'MyContract').arguments))"

Encode constructor args for verification

cast abi-encode "constructor(address,address)" 0xabc... 0xdef...

Foundry config (recommended for Flare-family work)

# foundry.toml
[profile.default]
src = "src"
out = "out"
libs = ["lib"]
optimizer = true
optimizer_runs = 200
solc_version = "0.8.24"
via_ir = true                  # required for stack-too-deep on complex contracts
fs_permissions = [{ access = "read", path = "config/" }]

[rpc_endpoints]
flare      = "https://flare-api.flare.network/ext/C/rpc"
songbird   = "https://songbird-api.flare.network/ext/C/rpc"
coston2    = "https://coston2-api.flare.network/ext/C/rpc"

When to use other skills

• Protocol architecture (FTSO, FDC, FAssets, Smart Accounts, FCC/TEE) — flare-general, then the protocol-specific skill.
• FTSO price feeds, anchor feeds, volatility incentives — flare-ftso.
• Flare Data Connector (cross-chain proofs) — flare-fdc.
• FAssets / FXRP minting + redemption — flare-fassets.
• ERC-4337 smart accounts on Flare — flare-smart-accounts.
• Enosys-specific contracts (DEX V3 reward managers, Loans/CDP, governance) — enosys-contracts, enosys-dex-v3.
• Cross-project gotchas (RPC log range, EIP-3855, MetaMask SDK hangs, claim-OOG) — flare-dapp-pitfalls.
• Flare-specific security review of a deployment — flare-security.
• Generic Solidity standards — solidity (Cyfrin).
• Auditing workflow — audit (checklist) and audit-contract (adversarial multi-agent).