flare-general

Document Flare network RPCs, chain IDs, and developer toolchains.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/mashharuki/flare-sample --skill flare-general
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flare-general
Source: https://github.com/mashharuki/flare-sample/tree/main/.claude/skills/flare-general
Command: npx skills add https://github.com/mashharuki/flare-sample --skill flare-general

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a single, authoritative reference that helps developers and integrators quickly understand Flare network fundamentals, avoid common integration mistakes, and configure toolchains and RPC endpoints without hunting through fragmented documentation.

Core Features & Use Cases

  • Network & RPC Configuration: Chain IDs, HTTPS/WSS RPC endpoints, explorers, and testnet faucets for Flare, Coston2, Songbird, and Coston.
  • Core Protocol Summaries: Clear explanations of FTSO, FDC, FAssets, Smart Accounts, and FCC/TEE and how they interact with contracts and offchain components.
  • Developer Tooling Guidance: Best practices for Hardhat, Foundry, wagmi/viem, Flare TX SDK, ContractRegistry usage, Wrapped Native (WNat) handling, secure random numbers, and indexer/wallet integrations.
  • Safety & Integration Notes: Read-only guidance emphasizing safe handling of external data, private keys, and runtime contract address resolution.

Quick Start

Use flare-general to summarize Flare core protocols and return the chain IDs, RPC URLs, explorers, and recommended developer tools for starting a new dApp on Coston2 or Flare mainnet.

Frequently Asked Questions about flare-general

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the Flare Time Series Oracle (FTSO) and how does it provide external data?

You can use Hardhat, Foundry, and wagmi/viem for dApp development on Flare. This reference provides best practices for configuring these toolchains, using the Flare TX SDK, and handling Wrapped Native (WNat) tokens.

How does ContractRegistry usage work for resolving contract addresses on Flare?

ContractRegistry usage on Flare involves querying the registry at runtime to dynamically resolve contract addresses. This ensures your dApp interacts with the correct protocol contracts and avoids hardcoding addresses across different network deployments.

What are FAssets and FDC protocols on the Flare network?

FAssets allow wrapping non-smart-contract assets on Flare, while the Flare Data Connector (FDC) enables the verification of external data. Both protocols interact with smart contracts and offchain components to expand network utility.

How do I safely handle private keys and external data when integrating with Flare?

To safely handle external data and private keys on Flare, follow read-only guidance and ensure runtime contract address resolution. This prevents key exposure and mitigates risks associated with processing untrusted external inputs.