Skip to main content

ABI

The ALX on Base ABI defines the public functions, events, errors, inputs, and outputs exposed by the Base contract. Applications and Ethereum tooling use the ABI to encode calls and decode contract data.

The ABI for the supported Base deployment (chain ID 8453) is published with the verified contract source on BaseScan. The ALX on Base page links the ABI, the contract address, and the deployment transaction.

Interface Purpose​

Applications use the ABI to encode function calls, decode return values, decode emitted events and contract errors, and integrate with wallets, SDKs, and Ethereum development tools.

EntryBehavior
anchor(bytes32 blockHash)Records one value. Reverts with AlreadyAnchored(bytes32) when the value is already recorded.
anchorBatch(bytes32 batchId, bytes32[] blockHashes)Records 2 to 256 values and skips values already recorded. Reverts with BatchTooSmall(uint256,uint256) or BatchTooLarge(uint256,uint256).
isAnchored(bytes32 blockHash)View. Returns true when the value is recorded.
anchoredAt(bytes32 blockHash)View. Returns the block timestamp of the first record, or 0 when the value is not recorded.
anchoredBy(bytes32 blockHash)View. Returns the address that submitted the first record, or the zero address when the value is not recorded.
MAX_BATCH_SIZE()View. Returns 256.
Anchored(bytes32 indexed blockHash, address indexed by, uint256 at)Event emitted for each newly recorded value.
BatchAnchored(bytes32 indexed batchId, address indexed by, uint256 at, uint256 count)Event emitted once per anchorBatch call; count is the number of newly recorded values.

Release Artifacts​

A reviewed release pairs the ABI with the deployment evidence listed in Deployment Requirements. Use the ABI to interact with the contract interface. Use the verified source on the network's block explorer, or a deployment manifest when one is published, to connect the interface to the deployed build.

Deployment Boundary​

An ABI defines a contract interface. An ABI alone does not identify a deployment, verify deployed bytecode, establish review status, or identify a supported network address.

When to Use an ABI​

Use an ABI for a public ALX on Base integration only when the ALX on Base deployment record identifies the matching verified source, address, and network.