Security & Audit

Static analysis results, test coverage, reentrancy protections, access control matrix, trust model, and known limitations.

1. Slither Security Audit

The initial contract set was analyzed with Slither v0.11.5 and completed its scoped remediation with zero high or critical findings at that time. The current recursive gate covers all 21 production Solidity sources and reports zero unreviewed High signals and zero Critical signals under the pinned toolchain against a reviewed six-entry High baseline.

• Tool: Slither v0.11.5
• Initial findings: 51
• Fixed: 15
• Accepted (informational / false positives): 36
• Current CI policy: every Critical signal and every new, changed or stale High fingerprint fails closed
• Current reviewed baseline: six signals, including one future V2 hardening item for the unchecked ERC-20 return in BuybackController.withdrawIFR()

Complementary Mythril Analysis

A separate bounded CI gate uses a hash-locked Python dependency set with Mythril v0.24.8 and setuptools 80.10.2 plus a repository-pinned SHA-256 for the Linux amd64 solc 0.8.28 artifact. It performs bounded symbolic execution of all 17 concrete production contracts. Four complete local runs on 4 September 2026 reported zero signals at any severity and completed in roughly six to seven minutes. The gate was integrated through PR #77 after exact-head and Main CI passed.

Fixes Applied

2. Full Internal Contract Security Audit

The contract set in this recorded review was examined line-by-line across 10 internal check categories: reentrancy, access control, integer overflow, front-running, DoS, centralization, fee edge cases, timelock bypass, feeExempt manipulation, and owner privileges.

Top Findings (Medium)

3. Test Coverage

The repository maintains contract, vault, application, wallet, browser and integration checks. Current exact results are recorded by CI and release preflights. The detailed counts below are a March 2026 internal snapshot, not a current deduplicated repository total.

Run the full test suite:

npx hardhat test

Solidity Coverage (solidity-coverage)

Historical coverage was measured with solidity-coverage for the contract subset recorded in March 2026: 99% statements, 91% branches, 98% functions, 99% lines. This is not a current full-repository coverage claim.

Full coverage report: COVERAGE_REPORT.md

4. Reentrancy Protection

Every contract that performs external calls is protected against reentrancy attacks through one of two mechanisms: OpenZeppelin's ReentrancyGuard modifier or the Checks-Effects-Interactions (CEI) pattern.

5. Access Control Matrix

The following matrix shows which roles can call which functions on each contract. Owner refers to the contract owner (Governance after ownership transfer), Guardian is the emergency role, Anyone means any external address, and Self means the contract calling itself via a governance proposal.

6. Trust Model

Inferno is designed so that no admin can make instant changes — all actions require a 48-hour public timelock delay and can be cancelled by the Guardian. Multiple safeguards are layered to protect token holders and ensure transparent governance.

• InfernoToken owned by Governance — all parameter changes (fee rates, exemptions) require a proposal with a 48-hour timelock before execution.
• Team tokens vested — 12-month cliff followed by 36-month linear release. No early access possible.
• Liquidity reserve staged — the 6-month initial lock ended 01.09.2026; all 200M IFR remains held and the contract limits withdrawals to 50M IFR per 90-day period.
• BuybackVault activation delayed — 60-day activation delay before the first buyback can be executed.
• Guardian is emergency-only — the Guardian role can pause contracts and cancel governance proposals, but cannot withdraw funds, execute proposals, or change parameters.
• Builder Vault (40M IFR) governance-locked — cannot be withdrawn directly. Released only through user adoption: when a user locks IFR for a Builder product, a % is automatically paid as reward (vested 6–12 months). If nobody locks, all 40M stay locked permanently.

7. Known Limitations

While the Inferno contracts have been thoroughly tested and analyzed, the following limitations should be understood by users, integrators, and auditors.

FeeRouter & Points Backend — Threat Model

FeeRouter Threats

Points Backend Threats

On-Chain Audit

All values are verifiable on-chain via Etherscan. Contracts are deployed and verified on Ethereum Mainnet.

Contract Ownership

Token Supply Distribution

Vesting (Team)

• Balance: 150,000,000 IFR (15%)
• Cliff: 365 days (~March 2027)
• Duration: 1,460 days total (12-month cliff + 36-month linear release)
• Released: 0 IFR

Deflation (Live)

Since deployment, — IFR have been permanently burned (— of total supply). Deflation is provable on-chain.

• Connecting…