flare-general

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

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

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, core protocols (FTSO, FDC, FAssets, Smart Accounts, FCC), and tooling setup without searching scattered documentation. ## Core Features & Use Cases - Network Configuration Reference: Chain IDs, RPC endpoints, block explorers, faucets, and native tokens for Flare Mainnet, Coston2, Songbird, and Coston. - Protocol Explanations: Covers FTSO price feeds, FDC attestations, FAssets wrapped tokens, Smart Accounts, Flare Systems Protocol, Snowman++ consensus, governance, and Flare Confidential Compute. - Developer Onboarding Guides: Language-specific guides for JavaScript, Python, Rust, Go, and React, plus Hardhat/Foundry starter kits, the ContractRegistry pattern, WNat wrapping, and secure random numbers. - Use Case: A developer asks how to connect Hardhat to Coston2 testnet and read an FTSO price feed; the skill supplies the RPC URL, chain ID 114, cancun EVM setting, and ContractRegistry-based resolution code. ## Quick Start Ask the assistant to explain how to set up a Hardhat project on Flare's Coston2 testnet and resolve the FtsoV2 contract address 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 Hardhat to the Flare Coston2 testnet?

Add a network entry with url https://coston2-api.flare.network/ext/C/rpc and chainId 114 in hardhat.config, and set evmVersion to cancun in Solidity settings. Get test C2FLR from the Coston2 faucet at faucet.flare.network/coston2.

How do I get Flare contract addresses without hardcoding them?

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

What are the chain IDs and RPC endpoints for Flare networks?

Flare Mainnet is chain ID 14, Coston2 testnet is 114, Songbird is 19, and Coston is 16. Each network has HTTPS and WSS endpoints following the pattern https://<network>-api.flare.network/ext/C/rpc.

Does Flare support standard Ethereum tooling like Foundry and web3.py?

Yes, Flare is EVM-compatible with Cancun hard fork support, so Foundry, Hardhat, web3.py, web3.js, viem, wagmi, go-ethereum, and alloy-rs all work. Set the EVM version to cancun and inject ExtraDataToPOAMiddleware when using web3.py on testnets.

What is the difference between FTSO, FDC, and FAssets on Flare?

FTSO provides decentralized price feeds updated every ~1.8 seconds, FDC validates external data from other chains and Web2 APIs via attestation consensus, and FAssets are trustless wrapped tokens like FXRP, FBTC, and FDOGE for use in Flare DeFi.

Can this skill execute transactions or manage wallet keys?

No, this skill is documentation and reference only. It does not sign transactions, access private keys, or call contracts; all signing and on-chain execution must occur in user-controlled developer environments.