Smart Contract Pause System for Anomaly Detection

After high-profile DeFi protocol exploits, it became clear: manual reaction to anomalies is too slow. Automatic smart contract pausing is the only way to stop a leak within seconds. But it must not block legitimate operations. Our engineers, with 5+ years of DeFi experience and 15+ delivered projects, offer a system that combines on-chain detectors and off-chain monitoring with over 99.9% accuracy. The average saving from preventing a single exploit exceeds $1 million — that's recent statistics.

How the smart contract pause system works on anomalies

The goal is to build a system that pauses the contract on real anomalies with minimal false positives, and does not itself become an attack vector. We use a combination of on-chain detectors and off-chain monitoring via OpenZeppelin Defender and Forta Network, ensuring reliability and transparency. The cost of error is high: exploit damage can reach $100 million.

How to set up automatic smart contract pausing

OpenZeppelin Pausable is the standard starting point. The source code is in OpenZeppelin Contracts.

import "@openzeppelin/contracts/security/Pausable.sol";
import "@openzeppelin/contracts/access/AccessControl.sol";

contract ProtectedVault is Pausable, AccessControl {
    bytes32 public constant PAUSER_ROLE = keccak256("PAUSER_ROLE");
    bytes32 public constant GUARDIAN_ROLE = keccak256("GUARDIAN_ROLE");

    function pause() external onlyRole(GUARDIAN_ROLE) {
        _pause();
    }

    function unpause() external onlyRole(DEFAULT_ADMIN_ROLE) {
        _unpause();
    }

    function deposit(uint256 amount) external whenNotPaused {
        // ...
    }

    function withdraw(uint256 amount) external whenNotPaused {
        // ...
    }
}

Key point: different roles for pause and unpause. An automated guardian could be compromised or err, but only humans via multisig/governance can unpause. That asymmetry is intentional.

What anomalies we detect

TVL anomaly and large transactions — developing the pause system

If more than X% of TVL leaves the contract within N blocks — that's a signal. We also monitor individual transactions exceeding 5% of TVL. Instead of automatic pause on these, we emit events for off-chain analysis.

contract AnomalyDetector {
    uint256 public constant MAX_TVL_DROP_BPS = 1000; // 10% per period
    uint256 public constant MONITORING_WINDOW = 100; // blocks

    function checkTVLAnomaly(uint256 currentTVL) internal {
        // ...
    }

    modifier checkWithdrawAnomaly(uint256 amount) {
        uint256 tvl = totalAssets();
        if (tvl > 0 && (amount * 10000 / tvl) > 500) { // 5% TVL
            emit LargeWithdrawal(msg.sender, amount, tvl);
        }
        _;
    }
}

Reentrancy detection on-chain

Complementing the standard nonReentrant — when a reentrancy attempt is detected, the contract pauses, not just reverts.

uint256 private _callDepth;

modifier noDeepCalls() {
    _callDepth++;
    if (_callDepth > 1) {
        _triggerPause("Reentrancy detected");
        revert("Reentrancy");
    }
    _;
    _callDepth--;
}

Why off-chain monitoring is more efficient

On-chain detectors are limited: they only see what happens in the current transaction. A more powerful pattern is off-chain monitoring + privileged pause transaction. We use OpenZeppelin Defender and Forta Network — this reduces reaction time by 5x compared to on-chain only.

OpenZeppelin Defender

OZ Defender Sentinel + Autotask is the standard stack:

const { DefenderRelayProvider, DefenderRelaySigner } = require('@openzeppelin/defender-relay-client/lib/ethers');

exports.handler = async function(credentials) {
    const provider = new DefenderRelayProvider(credentials);
    const signer = new DefenderRelaySigner(provider, credentials, { speed: 'fast' });
    const contract = new ethers.Contract(VAULT_ADDRESS, VAULT_ABI, signer);
    const tvl = await contract.totalAssets();
    const threshold = await contract.pauseThreshold();
    if (tvl < threshold) {
        const tx = await contract.pause();
        await tx.wait();
    }
};

Forta Network

Forta is a decentralized detection bot network. Alerts are integrated into Defender via webhook. For a precise assessment of your scenario, get a consultation from our engineers.

How circuit breaker works

A more flexible pattern: not a full pause, but a circuit breaker — temporary operation limits when an anomaly occurs. The concept is borrowed from Circuit breaker design pattern.

contract CircuitBreaker {
    enum Status { Normal, Restricted, Paused }
    Status public status;
    uint256 public dailyWithdrawLimit;
    uint256 public dailyWithdrawn;
    uint256 public lastResetDay;

    function withdraw(uint256 amount) external {
        require(status != Status.Paused, "Paused");
        if (status == Status.Restricted) {
            require(amount <= restrictedWithdrawLimit, "Exceeds restricted limit");
        }
        // ...
    }
}

Advantage: when the daily limit is exceeded, the protocol does not pause — it simply rejects transactions that exceed the limit. Users can continue operating within normal volume. MakerDAO, Compound, Aave use similar mechanisms.

Step-by-step implementation guide

1. Import Pausable and AccessControl into your contract, set up guardian and admin roles.
2. Add on-chain detectors: TVL drop, large transactions, reentrancy detection.
3. Connect off-chain monitoring: configure Defender Sentinel on LargeWithdrawal and TVL drop events, create an Autotask for automatic pause.
4. Integrate Forta Network: set up detection bots and webhook to call pause on anomalies.
5. Test scenarios: normal operation, false positives, attacks. Use formal verification and fuzzing.

What's included in the work

Development timelines: basic system (Pausable + Defender monitoring) — 2-3 weeks. Full system with circuit breaker, Forta, and governance — 5-7 weeks. We guarantee transparency at every stage.

To protect your DeFi protocol, get a consultation — we'll evaluate your project for free. Contact us. Order development of a pause system for your contract.

How Do We Find What the Compiler Misses?

When a protocol loses $197M through a flash loan attack on a function that auditors reviewed live — it's not an accident. It's a systemic gap in methodology. Our experience shows: vulnerabilities live in a contract for over a year, while the compiler remains silent. We restructured the audit process to catch such cases before deployment.

What Static Analysis Won't Find?

Slither is the standard first tool. It finds reentrancy, integer overflow (in older Solidity versions), improper use of tx.origin, variable shadowing, uninitialized storage. On a real project, Slither produces dozens of warnings, of which critical ones are 0‑2. The rest is informational noise.

Slither won't find logical vulnerabilities. If withdraw correctly checks balance and correctly updates state, but business logic allows double deduction through two different code paths — Slither stays silent.

Mythril uses symbolic execution: builds a graph of all possible execution paths and searches for reachable states violating properties. Works well on isolated contracts. On a protocol of 20 contracts with cross‑contract calls — path explosion, analysis hangs or returns false positives.

Both tools are mandatory as a first pass. But they don't replace manual analysis.

Fuzzing: Where Echidna and Foundry Find Real Bugs

Echidna is a property‑based fuzzer from Trail of Bits. The idea: formulate contract invariants as Solidity functions (echidna_invariant), Echidna generates random call sequences and tries to break the invariant.

Example invariant for a lending protocol:

function echidna_total_assets_ge_liabilities() public view returns (bool) {
    return totalAssets() >= totalLiabilities();
}

Echidna will find a sequence deposit → borrow → liquidate → repay that violates this invariant. You can't build such a case manually — too many combinations.

Foundry fuzzing (forge test --fuzz-runs 100000) is easier to integrate if the team is already on Foundry. Supports stateful fuzzing via invariant tests. In a real project: auditing a vault contract, Foundry fuzzed for 40 minutes and found an edge case where maxWithdraw returned a value larger than actual balance at a specific shares/assets ratio after several donations. Hardhat unit tests missed it — they didn't have that combination of parameters.

Medusa (from Trail of Bits, newer than Echidna) supports corpus‑guided fuzzing and runs faster on large contracts. If the codebase exceeds 5000 lines of Solidity — we look at Medusa.

How Invariants Help Identify Critical Vulnerabilities

Formal verification proves that the contract satisfies specifications for all possible inputs — not for N random ones, but mathematically for all. Tools: Certora Prover, K Framework, Halmos.

Certora works with CVL (Certora Verification Language): write rules and invariants, the Prover translates them into SMT formulas and checks via Z3/CVC5. MakerDAO, Aave, Uniswap use Certora in CI/CD pipeline — every PR is automatically verified.

Limitations: doesn't work with unbounded loops, struggles with hash functions and signature verification. For contracts with simple math (AMM, lending) — excellent. For contracts with arbitrary external calls — difficult to write sufficiently complete specifications.

Formal verification makes sense for contracts that: manage over $50M, are rarely updated, have clearly formalizable invariants. For fast‑iterating products — the cost‑benefit ratio doesn't favor verification.

What Attack Vectors Do Junior Auditors Miss?

Storage collision in proxy pattern. Transparent proxy and UUPS use specific slots for implementation address (EIP‑1967). If an implementation accidentally declares a variable in slot 0 that overlaps with proxy storage — we get silent override. Slither won't catch this if proxy and implementation are in different files.

Read‑only reentrancy. Classic reentrancy guard protects against state changes during recursive calls. But if an external contract reads state via a view function mid‑transaction — guard doesn't help. Years ago, Curve pools became an attack vector precisely through this: an external protocol read get_virtual_price during a reentrancy‑vulnerable state of Curve.

Oracle manipulation via TWAP. Spot price is a standard target for flash loan attack. TWAP is harder to manipulate, but not impossible: on low‑liquidity Uniswap v2 pairs, TWAP can be shifted over several blocks with enough capital. Proper protection: use Chainlink as primary oracle with TWAP as fallback, with deviation threshold check.

Gas griefing on unbounded loop. A function iterates over an array of users. Attacker adds thousands of addresses with zero balances — the function's gas cost rises to the gas limit, making it inaccessible. Protection: pull pattern instead of push, limit array lengths, batch processing with position tracking.

Front‑running on MEV. Transaction is visible in mempool before inclusion in block. MEV bot sees addLiquidity for a significant amount, inserts its own swap before it (sandwich attack). For AMM this is part of the model. For protocols with price functions — require minAmountOut / deadline parameter and its mandatory verification.

Structure of a Full Audit

1. Scope definition and automated analysis (1‑2 days). Fix commit hash, compiler version, list of out‑of‑scope items. Run Slither, Mythril, Aderyn. Triage: separate real critical bugs from false positives. Build contract dependency map.

2. Manual analysis (5‑15 days). Each contract line by line. Special attention: all external and public functions, all transfer/call/delegatecall, all places where state changes before a check or after an external call, all math operations with user inputs. On average, 95% of found vulnerabilities are logical, not technical.

3. Fuzzing and testing (2‑5 days). Echidna or Foundry invariant tests for critical invariants. Fork mainnet tests — verify behavior in real environment with real oracles. For example, in 4 days fuzzing finds on average 3 edge cases not covered by unit tests.

4. Report and mitigation. Report with severity (Critical/High/Medium/Low/Informational), attack vector description, PoC code for Critical/High. Developers fix, auditors perform re‑audit of fixes.

Audit in CI/CD

Common practice for mature protocols: Slither and Aderyn run in GitHub Actions on every PR. Certora Prover — on merge to main. This doesn't replace a full audit before deployment, but catches regressions.

# .github/workflows/audit.yml
- name: Run Slither
  uses: crytic/[email protected]
  with:
    target: 'src/'
    slither-args: '--filter-paths "test|mock|script"'

Audit Tools Comparison

Deliverables

• Full report in PDF with CVSS scores for each vulnerability
• PoC code for all Critical and High (reproducible in test environment)
• Remediation recommendations with code examples
• Re‑audit after fixes (up to two iterations)
• Brief guide for developers on ongoing operation
• Post‑deployment support for 30 days (consultations and incident analysis)

Timeline

Audit of a simple token or NFT contract — 3‑5 business days. DeFi protocol with lending/AMM — 2‑4 weeks. Full stack with multiple protocols, cross‑chain, proxy upgrades — 4‑8 weeks. Re‑audit of fixes — 3‑7 days separately.

Our team has 7+ years of experience in smart contract security, having audited over 100 projects. We guarantee we won't miss any known attack vectors — we use licensed versions of Slither and best fuzzer configurations. Assess your project — we will analyze your code for free and provide a commercial offer within 2 days. Order an audit with quality guarantee and get a discount on re‑audit for repeat customers.