Learn how to build custom Wake printers for smart contract analysis, uncover vulnerabilities, and speed up Solidity security reviews.
Glossary definition
Tool-based analysis
Automated smart contract analysis uses static or dynamic tools to surface suspicious code, violated properties, execution behavior, and coverage gaps.
Tool-based analysis is the analysis of computer programs using various tools. In smart contract security, many tools can help find common and known vulnerabilities.
We distinguish between static and dynamic code analysis. Static analysis is performed without executing the contract, whereas dynamic analysis identifies defects while running the contracts.
Tools we use when auditing EVM smart contracts written in Solidity include:
- Slither, a static-analysis framework written in Python that automatically detects common vulnerabilities
- Wake, a Python development and testing framework with static-analysis, fuzzing, and debugging capabilities
Wake is the actively developed successor to the framework originally named Woke.
Used in context
Articles using this term.
This guide provides a comprehensive analysis of reentrancy vulnerabilities with examples. Learn how reentrancy works and how to identify it in real protocols.
Safe Smart Accounts are the most audited and battle-tested smart contracts on Ethereum securing over $100 billion in assets. The Safe Social Recovery Module is a…
Ackee is finalizing an ERC-4337 detector to identify the use of forbidden opcodes and storage access, turning a very labor-intensive manual review into an automated…
So you want to write and deploy a smart contract, huh? Let’s set up this environment for a sample project from scratch
How to prepare for a smart contract audit The pre-audit part is essential for a smooth audit, and we will now guide you through it.
Building projects on top of cross-chain solutions may lead to security issues in the code. Open-source tools can automatically detect many issues or help test the…