Solidity Lab
  • 🧪Guardian - Solidity Lab
  • 📚Encyclopedia of Solidity Attack Vectors
    • 🔁Reentrancy
    • ✋Contract Cannot Accept Ether DoS
    • ⛽Gas Griefing
    • 👿isContract Manipulation
    • 🏃‍♂️🏃♂ 🏃♂ Front/Back-Running
    • ⏪External Call Reverts DoS
    • 🕐block.timestamp Manipulation
    • 🎣tx.origin Phishing Attack
    • 📩Directly Sending Funds
    • ✍️Signature Malleability
  • 📚Encyclopedia of Common Solidity Bugs
    • ➗Division Precision Loss
    • ‼️Unexpected Panic Revert
    • 👬Matching to/from Addresses
    • ⏸️Forget to Update Parallel Data Structures
    • 🚫Lack of Success Checks
    • 🤷‍♂️🤷♂ 🤷♂ Lack of Access Control
    • 📝Inaccurate Allowance
    • 🔼Overflow/Underflow
    • 💲Unsafe ERC20 Operations
    • 🦺Lack of Exception Handling
    • ✖️Duplicate Values
    • ⚖️Asymmetrical Code
    • 🛑Constant Protocol Parameters
    • ⬆️Storage Not Updated
    • 🕵️Delete Item, Unupdated Index
    • 🎁Native vs Wrapped Handling
    • 1️⃣1⃣ 1⃣ 1⃣ Off By 1
  • 📙The Auditors Handbook
    • 📝The Auditing Process
      • 0️⃣0⃣ Audit Setup/Preparation
      • 1️⃣1⃣ Beginning The Audit
      • 2️⃣2⃣ The Meat of The Audit
      • 3️⃣3⃣ Writing Tests & PoCs
      • 4️⃣4⃣ Wrapping Up The Audit
      • 5️⃣5⃣ After The Audit
      • 6️⃣6⃣ Addendum
Powered by GitBook
On this page
Edit on GitHub
  1. The Auditors Handbook
  2. The Auditing Process

5⃣ After The Audit

It's not over!

Continued Review

After delivering the report, make yourself available for any clarifications/advice on resolutions.

Be sure to review the amendments made to each finding and validate that they fully resolve the original issue and do not create new ones.

If the amendments are significant they may constitute a new audit. Contracts may need to go through several stages of audits until they are ready for deployment.

Previous4⃣ Wrapping Up The AuditNext6⃣ Addendum

Last updated 2 years ago

📙
📝
5️⃣