flare-general

Provides reference documentation for Flare network protocols, networks, and developer tooling.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/Zireaelst/Flare-Hackaton --skill flare-general-zireaelst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flare-general
Source: https://github.com/Zireaelst/Flare-Hackaton/tree/main/.agents/skills/flare-general
Command: npx skills add https://github.com/Zireaelst/Flare-Hackaton --skill flare-general-zireaelst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developers building on Flare need accurate, consolidated knowledge of the network's architecture, chain IDs, RPC endpoints, contract registry patterns, and core protocols (FTSO, FDC, FAssets, Smart Accounts) without hunting through scattered documentation. ## Core Features & Use Cases - Network Reference: Chain IDs, RPC endpoints, block explorers, and faucets for Flare Mainnet, Coston2, Songbird, and Coston. - Protocol Explanations: How FTSO, FDC, FAssets, Smart Accounts, FSP, consensus (Snowman++), governance, and FCC/TEE work. - Developer Guides: Language-specific integration guides for JavaScript, TypeScript/React, Python, Rust, and Go, plus Hardhat/Foundry starter kits, the ContractRegistry pattern, WNat wrapping, and secure random numbers. - Use Case: A developer setting up a Hardhat project on Coston2 asks for the correct RPC URL, chain ID, EVM version setting, and how to resolve the FtsoV2 contract address at runtime. ## Quick Start Ask the assistant to explain how to connect to the Coston2 testnet and resolve Flare contract addresses using the ContractRegistry.

Frequently Asked Questions about flare-general

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

FAQPage Schema
How do I connect to the Flare Coston2 testnet?

Use the RPC endpoint https://coston2-api.flare.network/ext/C/rpc with chain ID 114. Get testnet C2FLR, FXRP, and USDT0 from the Coston2 faucet at faucet.flare.network/coston2 before deploying or testing contracts.

How do I get Flare contract addresses without hardcoding them?

Use the FlareContractRegistry deployed at 0xaD67FE66660Fb8dFE9d6b1b4240d8650e30F6019, the same address on all Flare networks. Call getContractAddressByName or use the ContractRegistry Solidity library shorthand methods like getFtsoV2() to resolve addresses at runtime.

What is the difference between Flare Mainnet, Coston2, Songbird, and Coston?

Flare Mainnet (chain ID 14) is production, Coston2 (114) is the dApp testnet, Songbird (19) is the canary network for protocol experiments, and Coston (16) is the protocol testnet. dApp development follows Coston2 to Mainnet; protocol development follows Coston, Songbird, Coston2, then Mainnet.

Does Flare support standard Ethereum development tools like Hardhat and Foundry?

Yes, Flare is EVM-compatible and works with Hardhat, Foundry, web3.js, web3.py, go-ethereum, and alloy-rs. You must set the EVM version to cancun in compiler settings when using Flare periphery contracts.

Why must I check isSecure when using Flare random numbers?

The RandomNumberV2 contract sets isSecure to false if any data provider manipulated the commit-reveal round. Using a value when isSecure is false risks a biased random number, so consumers should wait for the next 90-second voting round.

Can this skill execute transactions or manage wallet keys?

No, this skill is documentation and reference only. It does not sign, broadcast, or initiate any transactions and never accesses private keys; all signing must occur in user-controlled wallets or developer-managed environments.