Fuzz test
Related service Blockchain
DEFINITION
Running millions of pseudo-random inputs through a function to find a combination that breaks it. Echidna or Foundry fuzz campaigns.
- Smart contract→
Code running on a blockchain (Solidity, Rust) that auto-executes an agreement. A single bug can cost nine figures · why we audit, fuzz, and threat-model before deploy.
- Solidity→
The primary language for EVM-compatible blockchains (Ethereum, Arbitrum, Base). Pascal-like syntax, low-level memory handling, TS-compatible toolchain (Foundry, Hardhat).
- EVM (Ethereum Virtual Machine)→
The shared execution environment across Ethereum and compatible chains (Arbitrum, Base, Polygon, Optimism). Writing a contract here means it runs on all of them.
- L2 (Layer 2)→
A secondary network (Arbitrum, Base, Optimism, zkSync) settling on Ethereum (L1) but much faster and cheaper. Rollups bring 10–100× lower gas.
- Invariant test→
A test that verifies a universal rule ('sum of user balances always equals total supply'). Feeds the contract random transaction sequences; the rule must hold in every state.
- Foundry→
A Rust-based Solidity toolchain (`forge`, `cast`, `anvil`). Faster with better invariant-test support than Hardhat. We run it on every DField audit project.
- 0126 Apr 2026OWASP LLM Top 10 v2 · what changed and what to ship→
- 0226 Apr 2026The CSP we ship · with notes on why each directive is there→
- 0322 Apr 2026Signed-firmware OTA pipeline · the 2026 default we ship→
- 0422 Apr 2026Agentic AI · the safe tool-use pattern we ship by default→
- 0522 Apr 2026Solana smart contract gotchas · what bites every Anchor dev in 2026→
- 0622 Apr 2026Multi-tenant SaaS on Postgres · the RLS-first playbook→
- 0722 Apr 2026EIP-712 meta-transactions · gasless UX without compromising security→
- 0820 Apr 2026NIS2 for SaaS: minimum checklist for 2026→