BUILD ON BASE.KNOW WHATSHIPPED.

BAO Toolkit: open-source tools for ERC-8021 attribution, source audits, and B20 evidence.

One toolkit for attribution,
code audits, and native
token evidence.

Reproduce transaction checks.
Keep your policy from source
code to onchain evidence.

Open source. Runs in your app, locally, and in CI.

From your app.
To the evidence.

BAO Toolkit is an independent, open-source developer toolkit for ERC-8021 Builder Code attribution, source audits, B20 token evidence, and transaction proofs on Base.

Add Builder Code attribution to your client. Catch gaps in source code. Inspect native token evidence. Keep a report you can reproduce.

  1. IntegrateAdd the code where your app builds a transaction.
  2. Audit and enforceKeep the same attribution policy in your app and CI.
  3. Verify and retainCheck submitted hashes and save the evidence.
Meet your new toolkit

Attribution that
travels with your app.

Builder Code attribution can disappear in a refactor without breaking the transaction. BAO Toolkit gives your team a repeatable control over that path.

Use typed helpers with viem, wagmi, or ethers. For smart wallets, negotiate capabilities before sending a batch and apply attribution to the final UserOperation calldata.

Choose your integration
Illustrative viem request
await walletClient.sendTransaction({
  account,
  to,
  value,
  data: "0x",
});
Builder Code suffix missing

A valid transaction request can omit attribution. The transaction alone does not protect your code.

Try the source audit
Illustrative Doctor output · local source analysis
$ bao doctor

Frameworks: smart-wallet, wagmi, x402
Coverage: 2/3 paths protected (67%)

+ wagmi   app/mint.tsx:18  protected
+ x402    src/pay.ts:9    protected
! wallet  src/batch.ts:22 missing BAO005

  Negotiate wallet_getCapabilities
  before wallet_sendCalls.
Find the path. Read the finding. Fix the request.

Catch the gap.
Before the merge.

Attribution Doctor connects supported TypeScript call sites to Builder Code evidence. Read findings in your terminal, inspect JSON, or send SARIF into Code Scanning.

Keep a project policy in bao.config.json and run it in CI. Static analysis reports unresolved configuration explicitly; it does not execute your app.

Native tokens.
Evidence attached.

B20 · Evidence tools

A successful token call can still omit your Builder Code.

BAO Toolkit inspects B20 initialization, canonical creation events, direct calldata attribution, and receipt comparisons as separate evidence. A router event does not establish attribution for the nested app.

See the transfer before and after

The transfer example uses synthetic receipts. Native runtime qualification and application readiness remain untested.

Before · synthetic transferCode missingInspect the missing-code report
After · corrected requestCode foundInspect the corrected report

Same token, recipient, and raw amount. One attribution fix.

Proof you can
open and reproduce.

Follow a selected transaction sample from calldata to a replay report and a Proof Set. Check the hashes, networks, acquisition context, and limits yourself.

Explore the Observatory

Inside the BAO Toolkit snapshot

Published transaction evidence · Base mainnet. This snapshot is separate from the illustrative source examples above.

Decoded Builder Code
bc_vwmzy653
What was checked
Calldata acquired over RPC; expected code decoded.
What you can retain
The replay input and the published manifest. Neither proves complete project coverage.
Open and reproduce this snapshot

Published attribution Proof Sets

2 registered snapshots · 3 verified transaction entries. These are the published sample’s totals, not network-wide analytics.

Base Attribution OSbc_vwmzy653
Base mainnet
Stack the Bagbc_4pe6m33m
Base Sepolia

Recorded B20 observations

2 public network snapshots. Recorded observations stay separate from synthetic examples and attribution Observatory totals.

Base mainnet: creation and a direct approvalSix public transactions, including a receipt-matched approval. Expected Builder Code is not configured.
Base Sepolia: Asset and Stablecoin creationTwo factory events inside wrapper calls. Nested application attribution remains unresolved.

Questions about BAO Toolkit

What is BAO Toolkit?

BAO Toolkit is an independent, open-source TypeScript toolkit for developers building on Base. It combines ERC-8021 Builder Code attribution, source audits, CI policy checks, B20 token evidence, app activity tools, and reproducible transaction Proof Sets. It is MIT licensed and is not affiliated with Base or Coinbase.

Explore the documentation

How do I add a Builder Code to my Base app?

Register your project's Builder Code on Base Dashboard, then use a BAO Toolkit adapter for viem, wagmi, or ethers to append ERC-8021 attribution to transaction calldata. Smart wallet integrations also cover capability-aware EIP-5792 batches and ERC-4337 UserOperations. Keep the same code in your app and bao.config.json policy.

Follow the installation and integration steps

What does Attribution Doctor check?

The bao doctor CLI scans supported TypeScript transaction paths for Builder Code attribution gaps. Use the same policy in local checks and GitHub Actions to catch regressions. The browser Doctor demonstrates example snippets; a full-project scan runs locally or in CI. A source audit checks code paths, while transaction replay checks supplied onchain evidence.

Read the source-audit scope and commands

What can I inspect with the B20 tools?

BAO Toolkit's B20 tools inspect token initialization evidence, replay supplied transaction samples, and check Builder Code attribution. The site separates synthetic examples from recorded network observations and publishes report inputs and limitations. These checks do not establish token safety or application readiness; follow the B20 guide for the current installation and reproduction workflow.

Read the B20 inspection and replay guide

Does a Proof Set cover every transaction from an app?

No. A published Proof Set covers only the supplied transaction sample. BAO Toolkit decodes ERC-8021 calldata, checks the expected Builder Code, and retains reproducible reports. Complete activity analysis needs an indexed dataset with a stated time range. A passing snapshot does not establish complete project coverage or future attribution correctness.

See how to reproduce transaction evidence

Do Builder Codes identify which tweet brought a user?

No. Builder Codes identify projects in transaction calldata. They do not identify a referring tweet, ad, or visitor session. BAO Toolkit helps preserve and verify that project-level attribution; campaign attribution requires separate referral or analytics data.

Understand Builder Code attribution

Your code.
Your next step.

Install the attribution adapters and CLI from npm. Follow the B20 guide to inspect tokens and reproduce transaction evidence.

pnpm add @base-attribution-os/viem
pnpm add -D @base-attribution-os/cli
Start building