Smart Contract Monitoring: Forta & OpenZeppelin Defender

You've deployed smart contracts, passed audits, but you realize: zero-day vulnerabilities appear every day. Reentrancy, flash loan attacks, oracle manipulations — monthly losses in DeFi exceed $100M, according to analytics. Audits check known bugs but don't protect against new attacks after deployment. The solution is active real-time smart contract monitoring that detects threats and blocks them before liquidity is stolen. The most effective combination is Forta Network and OpenZeppelin Defender.

We set up smart contract monitoring on Forta and Defender. Forta is a decentralized anomaly detection network: it analyzes every transaction and finds suspicious patterns using ML models and rules. Defender is a management platform that executes actions: pauses contracts, revokes permissions, sends alerts to Telegram/Slack/email. Together they form an automatic security circuit that works without human intervention.

Which attacks do we track?

• Reentrancy. Forta catches multiple calls to the same contract in one transaction. Defender immediately calls pause() via Autotask. Typical case: attacks on protocols with old code after EIP-150.
• Oracle manipulation. An abnormal change in Chainlink price (jump >20% in one block) triggers an alert and temporary blocking of dependent operations. For example, we set up protection for an AMM pool with $5M TVL where such a bot prevented a potential drain of $1.2M. For another protocol with $10M TVL, we prevented a reentrancy attack that could have taken $2M.
• MEV and flash loans. Custom bots recognize patterns of sandwich attacks and liquidity draining by analyzing call sequences. We also monitor mass approves — if there are more than 10 in a block, it's a sign of an attack.

How Forta and Defender work together

Forta detects faster (1-2 seconds) but cannot automatically respond. Defender is slower (up to a minute with polling) but can execute actions: pause, revoke, transfer. We connect them: Forta sends an alert to Defender via webhook, and Defender launches an Autotask that blocks the attack. Response time is no more than 10 seconds, which is critical for protecting liquidity.

Turnkey setup process

Setup goes through five stages:

1. Contract analysis: We study the code, identify critical functions (withdraw, mint, transferOwnership). We create an attack map.
2. Forta bot configuration: Deploy ready-made bots (reentrancy-counter) and write custom ones for your protocol.
3. Defender integration: Connect contracts, configure Admin and Relay, write Autotasks in JS for pausing or revoking permissions.
4. Testing: Simulate attacks on testnet using Foundry. Ensure detection and response work without false positives.
5. Launch and training: Move configuration to mainnet, hand over access, hold two training sessions for your team.

Response scenario comparison

Example custom Forta bot

const { ethers } = require('ethers');
const THRESHOLD = 10;

async function handleTransaction(txEvent) {
  const approves = txEvent.filterLog('Approval(address,address,uint256)');
  if (approves.length > THRESHOLD) {
    return [{ alertId: 'MASS-APPROVE', severity: 'High', metadata: { count: approves.length.toString() } }];
  }
  return [];
}

What's included in the service

• Documentation of all bots, triggers, and actions.
• Dashboards in Forta Explorer and Defender Admin.
• RBAC access for your team.
• 2 weeks of post-launch support.
• 95% detection guarantee for attacks with response under 10 seconds.
• Gas fee monitoring — alert on abnormal transaction costs.

Timeline and pricing

Standard setup for one contract (up to 10 functions, one network) takes 5 to 10 business days. For complex projects with cross-chain monitoring, we calculate the timeline individually. The cost is fixed after analyzing your contracts. If false positives or missed attacks occur in the first month, we adjust the bots for free.

Contact us for a detailed estimate — we will assess your project in one day. We can show configuration examples for protocols with TVL over $10M. Our team has 10+ years in blockchain security, and each engineer has personally written Forta bots and configured Defender in production. Order monitoring setup now.

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.