Starting A Scan
Learn how to initiate security scans on your smart contracts. The fastest way to scan: 1. Click New Scan on the dashboard 2. Upload or select a contract 3....
Starting a Scan
Learn how to initiate security scans on your smart contracts.
Quick Start
The fastest way to scan:
- Click New Scan on the dashboard
- Upload or select a contract
- Choose a scan profile (Quick/Standard/Deep)
- Click Start Scan
Scan Workflow
Step 1: Select Contract
You can either:
- Upload new - Drag a file or click to browse
- Choose existing - Select from your contracts list
Step 2: Choose Scanners
Select a preset or customize:
| Preset | Scanners | Time | Best For |
|---|---|---|---|
| Quick | 3-4 | ~1 min | Development feedback |
| Standard | 7-8 | ~3 min | Regular checks |
| Deep | All 17+ | ~10 min | Pre-audit analysis |
Or click Custom to select individual scanners.
Step 3: Configure Options (Optional)
Additional settings:
- Project context - Include related files
- Scan name - Custom name for reference
- Priority - Normal or high (paid plans)
Step 4: Start
Click Start Scan to begin.
Scan Presets
Quick Scan
Best for: Fast feedback during development
Scanners included:
- Slither (static analysis)
- Aderyn (fast analyzer)
- Solhint (linting)
Time: ~30 seconds - 2 minutes
Standard Scan
Best for: Regular security checks
Scanners included:
- All Quick scanners, plus:
- Semgrep (pattern matching)
- Wake (framework-aware)
- Mythril (symbolic execution)
Time: ~2-5 minutes
Deep Scan
Best for: Comprehensive pre-audit analysis
Scanners included:
- All Standard scanners, plus:
- SolidityDefend (204+ detectors)
- Echidna (fuzzing, projects only)
- Medusa (fuzzing, projects only)
- Halmos (symbolic testing)
Time: ~5-15 minutes
Custom Scanner Selection
Available Scanners
Click Custom to see all scanners:
Static Analysis:
- Slither - Industry standard, 93 detectors
- Aderyn - Rust-based, 88 detectors
- SolidityDefend - 204+ detectors
- Semgrep - Pattern matching
- Solhint - Linting
- Wake - Framework-aware
- Mythril - Symbolic execution
Fuzzing (projects only):
- Echidna - Property-based
- Medusa - Fast fuzzing
- Halmos - Symbolic testing
Scanner Availability
Some scanners require specific conditions:
| Scanner | Single File | Project |
|---|---|---|
| Slither | ✓ | ✓ |
| Echidna | - | ✓ |
| Medusa | - | ✓ |
| Halmos | - | ✓ |
During the Scan
Progress View
While scanning, you see:
- Overall progress bar
- Individual scanner status
- Estimated time remaining
- Real-time findings count
Scanner States
| State | Meaning |
|---|---|
| ⏳ Queued | Waiting to start |
| 🔄 Running | Currently analyzing |
| ✅ Complete | Finished successfully |
| ❌ Failed | Error occurred |
Background Scanning
You can navigate away while scanning:
- Scan continues in background
- Notification when complete
- Results available in Scans list
Scan Completion
Success
When complete:
- Results page opens automatically
- Findings listed by severity
- Summary statistics shown
Partial Completion
If some scanners fail:
- Successful results are available
- Failed scanners show error message
- You can retry failed scanners
Full Failure
If all scanners fail:
- Error message displayed
- Check contract for syntax errors
- Try with fewer scanners
Scan Options
Scan Name
Give your scan a memorable name:
- "Pre-audit check v2.1"
- "Post-fix verification"
- Defaults to contract name + date
Notifications
Get notified when complete:
- Browser - Desktop notification
- Email - Email notification (enable in settings)
- Webhook - For CI/CD integration
Re-Scanning
When to Re-Scan
Re-scan after:
- Fixing vulnerabilities
- Updating code
- Adding new features
- Before deployment
Quick Re-Scan
- Go to a previous scan
- Click Re-Scan
- Same scanners run again
- Compare to previous results
Scan Limits
By Plan
| Plan | Scans/Month |
|---|---|
| Free | 10 |
| Developer | 100 |
| Startup | 500 |
| Professional | Unlimited |
What Counts
Each scan uses 1 credit/quota:
- New scans
- Re-scans
- Project scans (regardless of file count)
Troubleshooting
Scan stuck at "Queued"
- High system load, wait a moment
- Check scan queue status
- Contact support if >10 minutes
Scanner keeps failing
- Check contract for syntax errors
- Try a different scanner
- Review error message for clues
"Timeout" error
- Contract may be too complex
- Try with fewer scanners
- Try Quick preset first
Next Steps
- Scanner Selection - Choose optimal scanners
- Scanner Catalog - All scanner details
- Scan Status - Monitor progress