flare-security

Apply security-first patterns to Flare-family contract design and audits.

1|1|Updated May 6, 2026
One-click install
npx skills add https://github.com/Thanasimos/Thanas-flare-builders-toolkit --skill flare-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flare-security
Source: https://github.com/Thanasimos/Thanas-flare-builders-toolkit/tree/main/flare-security
Command: npx skills add https://github.com/Thanasimos/Thanas-flare-builders-toolkit --skill flare-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flare-security provides a comprehensive security-first framework for Flare-family contract design, deployment, and audits, reducing common security pitfalls before mainnet.

Core Features & Use Cases

  • Foundational secure-coding patterns (Ownership with Ownable2Step, ReentrancyGuardTransient, SafeERC20 usage, CEI, custom errors, immutable/constant values) as baseline for all contracts.
  • Flare-specific overlays (Permit2 chain availability, FoT handling, blacklistable stablecoin surface, FTSO redistributor proxy upgradeability, basefee floors on testnets, protected RPC log access, Multicall3 awareness) to handle chain-specific constraints.
  • Audit-ready governance: supports both generic audits and Flare overlays to ensure safe deployments and robust post-audit operations.

Quick Start

Review the Part 1 and Part 2 guidance and incorporate the recommended patterns into your contract design and review process.

Frequently Asked Questions about flare-security

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

FAQPage Schema
What security-first patterns should I apply when auditing Flare smart contracts?

To audit Flare contracts securely, apply foundational patterns like Ownable2Step, ReentrancyGuardTransient, SafeERC20 usage, and Checks-Effects-Interactions ordering, alongside Flare-specific overlays including Permit2 availability and Multicall3 awareness to mitigate known vulnerabilities.

How do I handle Fee-on-Transfer (FoT) and blacklistable tokens during a Flare contract audit?

During Flare contract audits, explicitly handle Fee-on-Transfer (FoT) tokens and blacklistable stablecoin surfaces by enforcing SafeERC20 patterns, ensuring safe token transfers and preventing unexpected revert conditions in post-audit operations.

Does Flare support Permit2 and Multicall3 for secure contract deployments?

Yes, Flare deployments can leverage Permit2 chain availability and Multicall3 awareness as security overlays, allowing developers to integrate these protocols into contract design and audit workflows to ensure safe mainnet operations.

Why should I use Ownable2Step and custom errors in Flare smart contract design?

Using Ownable2Step prevents accidental ownership loss by requiring two-step transfer acceptance, while custom errors reduce gas costs; both are enforced baseline patterns for secure Flare contract design and robust audit compliance.

What are the limitations when auditing FTSO redistributor proxy upgrades on Flare?

When auditing Flare contracts, explicitly verify FTSO redistributor proxy upgradeability and basefee floor constraints on testnets, as these chain-specific validations require dedicated attention outside standard foundational security patterns.