Keep your activity attributable.

A transaction can succeed without your Builder Code. Bao Toolkit checks for the missing credit.

Builder Codebc_vwmzy653

Published evidence

Before release: check the code

Not connected

—

No published source audit
Connect a Doctor report to inspect source coverage

Protected paths —Gaps or unresolved —

Source coverage and onchain evidence are separate checks. A successful transaction does not prove every source path is protected.

Missing attribution—

Wrong Builder Code—

Needs manual resolution—

Run these checks on your app

Inspect every supported path

Publish a source audit to see framework-level coverage.

Catch regressions in a PR

Run Doctor in strict CI. Missing or unresolved attribution produces a failing check before changes ship.

Get the GitHub Action

Check what reached the chain

Decode the actual transaction or supported smart-wallet UserOperation and match your Builder Code.

Open the real evidence

After sending: verify the onchain evidence

100% verified attribution across this selected sample. 1 of 1 published transactions; not a full activity feed.

Published transactions: 1
Unique transaction hashes
RPC-verified evidence: 1
Verified when the snapshot was made
Builder Code found: 1
Decoded from transaction data
Needs review: 0
Missing attribution or verification

Where attribution holds

Published transaction paths

Published transaction

1 / 1 verified & attributed

Before the next release

Release check

Recheck attribution when you add a mint, wallet flow, or payment path. Publish a new source audit and onchain evidence for the paths you enable.

This published transaction sample is separate from release checks. It does not establish current deployment readiness.

The evidence behind the numbers

Open a transaction to check it on the block explorer.

Export full sample

Needs review only1 of 1 transactions

Transaction / path	Network	Block	Attribution	Evidence
0x657334…fe4926Published transaction	Base mainnet	48,068,189	Code found`bc_vwmzy653`	RPC verified

How to read these numbers

Transactions are deduplicated by network and hash. Coverage counts transactions that are both RPC verified and decoded with the expected Builder Code, divided by every transaction in the selected published sample. Empty samples have no coverage percentage.

Verification describes attribution evidence at snapshot time. It does not certify contract security, current deployment readiness, successful game actions, or the source of a player’s visit. Missing, invalid, unavailable, differently attributed, and unverified records remain in the denominator.

Snapshots update when a new proof set is published. This dashboard does not poll the blockchain. Season counts, unique players, revenue, and daily activity are not inferred from the sample.

Explore all published proof sets

Use Bao Toolkit alongside Base analytics

Base App automatically adds a registered app’s Builder Code. Outside Base App, builders integrate attribution themselves. A direct SDK setup can be enough for a simple app. Read the Base integration guide.

Bao Toolkit becomes useful when you want repeatable source checks, failing CI checks for attribution regressions, and reusable onchain evidence across supported transaction paths. It does not guarantee rewards, recover past unattributed transactions, or measure referrals from X.