Skip to main content
Use attribution when you need to identify which builder generated onchain activity or determine whether a user satisfies a verified eligibility requirement. Builder Codes and Base Verify solve different parts of that problem.

​
Attribute Onchain Activity

Builder Codes append an ERC-8021 attribution suffix to transaction calldata. Offchain indexers use the suffix to associate activity with the app, wallet, or agent that generated it.

Builder Codes Overview

Understand Builder Codes, attribution benefits, supported account types, and verification options.

For App Developers

Add automatic transaction attribution with Wagmi, Viem, CDP Wallets, or Privy.

For Wallet Developers

Implement the dataSuffix capability for EOAs and ERC-4337 user operations.

For Agent Developers

Register an agent and attribute its autonomous onchain transactions.

​
Verify User Attributes

Base Verify lets a user prove control of a supported account and lets your application evaluate approved traits. Choose the backend flow for application-controlled experiences or the onchain flow when a smart contract must enforce the policy.

Base Verify API

Compare the backend and onchain verification flows.

Verify Social Accounts

Check verified account ownership and traits from your application backend.

Verify Users Onchain

Enforce policy gating and one-person-once participation in a smart contract.
Builder Codes attribute transaction origin; they do not verify a user’s identity or eligibility. Base Verify evaluates verified user attributes; it does not attribute transactions to the builder that generated them.