← Back to dashboard
README.txtBASE / ERC-8021

About the Base WTU Dashboard

A read-only, self-hosted view of ERC-8021 attribution on Base mainnet.

How WTU is calculated

WTU (weekly transacting users) is the number of distinct users with at least one successful attributed operation in the trailing 7 days. The same method is also available for 1-day and 30-day windows.

Other columns

Tx counts attributed operations, including failed ones. Fees ETH is the confirmed gas fee; an operation with multiple codes contributes its fee to each code.

Why failed operations are included

Failed operations are still real onchain attempts and usually consume gas, so they remain part of the transaction count. They do not increase WTU, which stays focused on users whose attributed operation completed.

Wallet connects and other off-chain activity are not included. The source of truth is Base mainnet calldata, receipts, and EntryPoint logs. “Indexed through” shows the newest confirmed block; during an initial backfill, the selected window can be marked partial.

App identity disclaimer

App names, websites, and social links are added manually. Basic checks are performed, but mistakes are always possible. DYOR before interacting with any app, website, wallet, or contract.

Index coverage

Loading the current tracking start…

A 7-day or 30-day selection is a trailing window only after the index contains that much history. Until then, the dashboard shows every indexed transaction it has and marks the result as partial.

Build with the dashboard

Every builder page includes a Copy embed code action. It creates a live iframe card that refreshes once a minute:

<iframe src="https://builder-circle.xyz/widget/bc_yourcode?window=7d" width="460" height="360" loading="lazy" style="border:0;max-width:100%"></iframe>

Use variant=compact for a small sidebar card or variant=wide for a larger dashboard card. For a custom design, request /api/widget/bc_yourcode?window=7d. Cross-origin GET requests are allowed. Always show the partial-window warning when window_complete is false.

Use the API & widgets · Open a live widget example