Best Practices for Using QuillShield

Pre-Audit Preparation

  • Ensure all dependencies are properly configured

  • Use consistent Solidity compiler versions across your project

  • Organize your codebase with clear folder structures

  • Document any custom business logic for better analysis

Interpreting Results

  • Prioritize High and Medium severity findings

  • Review Low severity issues for code quality improvements

  • Validate findings against your specific use case requirements

  • Consider the provided POCs for understanding attack vectors

Last updated