Skip to content
bugcrawl

Every contract has a trail.

Explore contracts on Robinhood Chain, check whether their published source matches the bytecode, and follow the evidence behind every result.

Explore contractsor verify a contract
  1. 0contracts tracked
  2. 0source-verified by an explorer
  3. 2public networks
  4. 0verification checks this week

No contracts tracked yet. Look one up in the Verification Center to start the trail.

A colony of small contracts, each with one job

BugCrawl runs on 47 Solidity source files: 28 deployable modules, 12 interfaces, 5 libraries and 2 shared base and type files. Source files and deployed instances are tracked separately, and only modules a deployment needs are deployed.

BugCrawl's contracts are not deployed on any network enabled here yet. Follow the deployment guide to put them on Robinhood Chain.
See the architectureRead the module guide

Where the work happens

Four modules carry most of the load. Each is a separately deployed, separately verifiable contract.

No BugCrawl deployment on these networks yet

Once the contracts are deployed, the directory, coordinator, attestation registry and lens appear here with their live source status.

Recently verified

Contracts whose source an explorer confirmed most recently. Mock-provider results never appear here.

All verified contracts

Nothing verified yet

When a contract's source is confirmed by its network's explorer, it shows up here with the time it was checked.
Verify a contract

How a contract gets verified

Verification needs more than an address. It needs the exact source and compiler settings that produced the bytecode.

  1. 1

    Point at a contract

    Pick a network and paste an address. BugCrawl confirms there is bytecode there before anything else.

  2. 2

    Ask the explorer

    The network's explorer is asked whether it already holds matching source. If it does, you're done.

  3. 3

    Send the exact build

    Otherwise, submit the source plus the exact compiler version, optimizer runs, EVM version and constructor arguments.

  4. 4

    Explorer recompiles

    The explorer compiles your input and compares it byte-for-byte with what's deployed. BugCrawl polls the job.

  5. 5

    Evidence is recorded

    The final status is re-read from the explorer, stored with a digest of what was submitted, and shown on the contract page.

Start a verificationWhat the explorer checks

Three different claims, never blended

BugCrawl keeps each kind of evidence in its own field, on its own contract, so one can never be mistaken for another.

ClaimWhat it meansWhat it does not mean
Source verifiedAn explorer recompiled the published source and got the same bytecode.Not a statement that the code is safe, audited, or does what its name suggests.
Security attestationA named, curator-approved reviewer published a report hash for this contract on-chain.Not issued by BugCrawl, and only as good as the reviewer and the report itself.
Listed in the directorySomeone catalogued the contract so it can be found and tracked.Not verification and not an endorsement. Anyone can be listed.

Supported networks

Coming soon

$BUGS

The BugCrawl token is on its way. Its contract will be source-verified through BugCrawl before launch, and the address will be published on this site first.

Read about $BUGS

For developers