Before: code missing
- Expected code
bc_example- Direct attribution
- 0/1 (0%)
- Token evidence
- Initialized B20 Asset · modeled factory query
- Execution
- Successful synthetic receipt
- Application readiness
- Not tested
A B20 transfer can succeed without your Builder Code. Compare the same transfer before and after an attribution fix, then inspect the evidence.
The token, recipient, raw amount, and modeled execution stay the same. The corrected request uses withAttributionSuffix from Bao Toolkit’s viem adapter.
bc_examplebc_exampleThese receipts demonstrate the analyzer. This before/after transfer has not been tested on a native B20 runtime.
5 synthetic examples · 2 recorded network reports. Synthetic examples remain separate from the attribution Observatory’s totals.
A successful transfer omits the expected Builder Code.
The existing Bao Toolkit viem helper preserves the expected code.
Canonical factory evidence and a direct transfer in the supplied set.
End-of-block token state cannot establish initialization before a reverted call.
Receipt evidence does not establish attribution for the nested application.
Six public transactions, including a receipt-matched approval. Expected Builder Code is not configured.
Two factory events inside wrapper calls. Nested application attribution remains unresolved.
Download a report’s capture, then run the candidate CLI. Offline validation checks internal consistency; a network recheck requires an explicit RPC endpoint.
bao b20 replay --input b20-direct-broken.capture.json --chain-id 84532 --expect bc_example --offline
bao b20 replay --input b20-direct-fixed.capture.json --chain-id 84532 --expect bc_example --offlineStart with the CLI guide or technical pilot kit. The B20 package is an unreleased candidate.