Practical overview
When it fits
Consult it during DeFi application and smart-contract planning or before deployment to organize review topics. Use it as a prompt list alongside the testing, tools and review work your project requires.
Who it is for
- DeFi teams preparing an application or smart contracts for deployment.
- Developers and reviewers organizing a security review around documented checklist topics.
- Contributors proposing additions or updates to the repository.
Documented uses
- Structure a pre-deployment review across testing, architecture, contract practices and security.
- Identify topics for team discussion, including access control, oracle choices, upgradeability and pausing.
- Suggest checklist changes through a pull request.
Requirements & limits
- The repository covers both engineering practices, such as testing and documentation, and design topics such as threat modeling, access control and tokenomics.
- It mentions automated anomaly-detection tools, formal verification and audits as review considerations; the repository itself is not shown to perform these tasks.
- The checklist names Solidity and Rust in its compiler-version guidance and discusses smart-contract practices across several languages.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Review a DeFi project against the pre-deployment checklist
Use the checklist’s documented topics to review smart-contract security before deployment.
Before you start
- A DeFi project preparing for deployment.
- Project code and design materials to review.
Steps
Review the project’s architecture, design, and threat model, considering possible threats and security assumptions.
Check that the project uses the latest released Solidity or Rust version and that the code has no reported issues with the latest compiler version.
Review unit-test coverage, programming practices, code documentation, modularity, and logging of crucial operations.
Assess the checklist’s remaining security topics, including libraries, oracle sources, upgradeability, pausing, common vulnerabilities, access control, tokenomics, anomaly detection, formal verification, and audits.
Expected outcome
A review organized around the checklist’s pre-deployment security topics, with items available for the project team to assess.
Guide limitations
- The checklist is guidance; it does not establish that automated audits or executable security tools are provided.
- The listed topics do not provide detailed procedures or acceptance criteria for each review.
Suggest an update to the checklist repository
Contribute a missing checklist item or update an existing resource through a pull request.
Before you start
- A proposed missing item or update to an existing resource.
- Access to the repository’s contribution workflow.
Steps
Identify a missing checklist item or an existing resource that needs updating.
Create a pull request proposing the contribution.
Expected outcome
A proposed checklist contribution submitted to the project for consideration.
Guide limitations
- The repository description does not specify contribution formatting, review steps, or acceptance criteria.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 18 October 2026
- Original website title
- Quillhash/DeFi-anti-hack-checklist · Official homepage title · retained in its source language