Clone Finder answers a simple question with expensive consequences: what else on-chain looks like this contract? You pick a source contract and run a similarity search, and it surfaces the contracts that share its code — forks, redeploys, and near-identical copies — ranked by how close the match is.
Why it exists
Vulnerabilities travel by copy-paste. A bug found in one contract usually exists in every fork of it, and attackers scan for those forks first. Because Clone Finder works from bytecode — structural hashes, function selectors, and opcode profiles — it finds those relatives even when they were deployed from unverified source or with cosmetic changes that would fool a source-text diff.
Who uses it
- Auditor — checks whether a finding in one contract reproduces across its known forks before signing off.
- Researcher — maps the family of contracts descended from a common implementation to scope a class of bugs.
How to open it
- Sidebar → Analysis → Clone Finder.
- Direct URL —
/clone-finder.
Running a search
- Choose a source contract from the workspace and its network.
- Set a minimum similarity threshold and a match type to control how strict the comparison is.
- Run similarity search.
Each result shows why it matched: its structural hash, the function selectors and shared functions it has in common, its top opcodes, and its code size, so a high score is something you can inspect rather than take on faith.
Limits
- Similarity is a lead, not a verdict — two contracts sharing structure still need their differences reviewed before you assume a bug carries over.
- Matching is by compiled shape; a functionally similar contract written differently may score lower than an exact fork.
Related pages
- EVM Contract Overview — open any match to analyse it in full.
- Dependency Map — see how a matched contract connects to others.