Overview
Auditing Hedera contracts combines standard Ethereum tooling with network-specific invariants (HTS precompile behavior, decimal quirks, hook-enabled ERC-20 flows).
When to use this skill
- Preparing bug bounty submissions (Bug bounty scope).
- Running static analysis in CI for Solidity repos targeting Hedera relays.
Prerequisites
- Python 3.10+ for Slither/Mythril.
- Compiled artifacts (
artifacts/+ source maps).
Workflow
Static analysis — run
./scripts/run-audit.shafter customizing compiler version inside repo.Manual review — walk checklist in references/audit-checklist.md.
Hedera-specific classes — investigate hook-enabled allowances per HIP-1195 & HTS interactions (references/hedera-vuln-taxonomy.md).
Reporting — populate scripts/audit-template.md.
Scoring — apply CVSS but annotate network-layer exploitability assumptions.
Examples
Example 1
“Slither on Hedera fork.”
Point Slither at flattened contracts + relay RPC if differential testing needed.
Example 2
“Does reentrancy matter on HTS?”
Yes — treat HTS calls as external interactions possibly invoking hooks.
Example 3
“Need bounty-ready write-up.”
Include reproducible testnet PoC + impacted contracts list.
Troubleshooting
| Issue | Tip |
|---|---|
| Mythril timeouts | Narrow bytecode scope |
References
- Local: references/hedera-vuln-taxonomy.md, references/audit-checklist.md, references/2023-hts-exploit.md, references/bug-bounty-scope.md