New Base Builder Code Tracker Reveals On-Chain Activity for Web3 Games

The plumbing of attribution

The site, built by Matt Wong on top of the Coinbase Developer Platform SQL API, converts a developer's code into a readable dashboard of transactions, active days, and streaks. Champz became the first studio to publish concrete figures through it, reporting roughly 40,000 on-chain transactions across its two Base applications over the last six months.

How the code works

The mechanism behind the dashboard is ERC-8021. A byte suffix is appended to a transaction's calldata, identifying the app that initiated it. Indexers parse the suffix in reverse: a 16-byte marker, then schema ID, then schema-specific payload. Because the contracts the transaction targets ignore bytes appended past the arguments they expect, the suffix passes through execution untouched. Overhead is fixed at 16 gas per non-zero byte. Codes are issued as an ERC-721 collection, with an on-chain payout address for any future rewards and off-chain metadata carrying the app name and site. Developers register on base.dev, where the code appears under Settings, then Builder Code, and a single suffix can hold multiple comma-separated codes for transactions facilitated by both a frontend and a backend relay. Builder Codes went live for all apps on Base in early March 2026 and were extended to x402 payments in June under schema 2, so settlement transactions can also carry attribution.

Reading Champz's split

The numbers break down cleanly. Legends of Champz accounts for 21,900 transactions across 154 active days, with a current activity streak of 142 days. The Champz miniapp contributes 17,900 transactions across 185 active days on a 185-day streak, meaning it has not missed a single day in the measured window. The CDP SQL API the tracker queries returns results with latency under 500ms and freshness under 250ms from the chain tip, according to CDP documentation. That latency budget is what makes a real-time dashboard viable for an indexer of this scope.

Scalability verdict

The protocol layer is sound. Attribution is technically clean, cheap, and live across both consumer apps and payment rails like x402. The bottleneck is opt-in: any transaction routed through a relay, bot, or backend job that fails to attach the suffix is invisible to the tracker. Hyperliquid and Polymarket have already shipped their own scoped versions for swaps and prediction markets. Signal quality is bounded by the share of developers who register, not by the capacity of the chain. Until that share grows, the dashboard measures an honest subset rather than the full on-chain truth.