flare-general

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

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

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 core protocols (FTSO, FDC, FAssets, Smart Accounts, FCC/TEE), network configurations, RPC endpoints, chain IDs, and tooling without hunting through scattered documentation. ## Core Features & Use Cases - Network Reference: Chain IDs, RPC endpoints, block explorers, faucets, and native tokens for Flare Mainnet, Coston2, Songbird, and Coston. - Protocol Knowledge: Explanations of FTSO price feeds, FDC attestations, FAssets wrapped tokens, Smart Accounts, Flare Systems Protocol, Snowman++ consensus, and governance. - Developer Onboarding: Hardhat and Foundry starter kit setup, ContractRegistry address resolution, WNat wrapping, secure random numbers, and language-specific guides for JavaScript, React, Python, Rust, and Go. - Use Case: A developer asks how to read FTSO price feeds on Coston2 testnet; the skill supplies the correct RPC endpoint, the ContractRegistry pattern for resolving FtsoV2, and a working Solidity or TypeScript example. ## Quick Start Ask the assistant to explain how to connect to the Coston2 testnet and resolve the FtsoV2 contract address using the Flare 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 tokens from the Coston2 faucet at faucet.flare.network/coston2, and configure your Hardhat or Foundry project with evmVersion set to cancun.

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 is the difference between FTSO and FDC on Flare?

FTSO is a decentralized price feed oracle delivering block-latency data every ~1.8 seconds from around 100 providers. FDC validates external data such as cross-chain transactions and Web2 API responses through attestation consensus and Merkle proofs.

Does Flare support standard Ethereum development tools?

Yes, Flare is EVM-compatible with Cancun hard fork support, so Hardhat, Foundry, web3.js, ethers, viem, wagmi, web3.py, go-ethereum, and alloy-rs all work. Set evmVersion to cancun when compiling contracts that use Flare periphery contracts.

What are the limitations of this Flare reference skill?

The skill is documentation and reference only; it does not execute transactions, sign messages, access private keys, or call contracts directly. All signing and on-chain execution must occur in user-controlled developer environments.

How do I get a secure random number on Flare?

Call getRandomNumber() on the RandomNumberV2 contract, which updates every 90 seconds via the Scaling protocol's commit-reveal process. Always verify the isSecure flag is true before using the value, and resolve the address via ContractRegistry.getRandomNumberV2().