Small creatures, close inspection

Bugs are good at one thing: going everywhere, slowly, and noticing what everyone else walks past. BugCrawl applies that to smart contracts. It crawls what's deployed, asks each network's explorer what is actually known about the code, and leaves a trail of evidence you can follow back.

We started on Robinhood Chain, an EVM network where tokenized assets and new projects arrive quickly and names are cheap to copy. A familiar name on a contract tells you nothing. Published, matching source code tells you a little more. A named reviewer's report tells you more again. BugCrawl keeps those three things separate and shows you exactly which one you're looking at.

What BugCrawl does

• Keeps a searchable directory of contracts, with where each entry came from.
• Relays source-verification submissions to the network's explorer and records what the explorer says.
• Runs its own logic in 47 small, separately verifiable Solidity files, with roles, a pause switch and a timelock.
• Shows recent transactions and counterparties of any address on the trail map.

What BugCrawl does not do

• It does not certify that any contract is safe. Source verification is not an audit.
• It does not hold funds, mint tokens or charge fees in its contracts.
• It never asks for a seed phrase or private key, and never signs anything on your behalf.

The code, the contracts and the deployment manifests are all part of the same repository, so you can check every claim on this site. Start with the documentation or the ecosystem map.