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.
No ABI is currently associated with a supported public ALX on Base deployment. The ALX on Base deployment record will publish the supported ABI with the matching address, bytecode, source revision, and deployment manifest.
Interface Purpose
Applications use an ABI to:
- encode contract function calls;
- decode function return values;
- decode emitted events and contract errors; and
- integrate with wallets, SDKs, and Ethereum development tools.
Release Artifacts
A reviewed contract release pairs the ABI with:
- a deployment manifest;
- the source revision;
- the compiler version and settings;
- the deployed bytecode;
- the contract address; and
- the network.
Use the ABI to interact with the contract interface. Use the deployment manifest to connect the interface to a reviewed build and deployment.
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 deployment record identifies the matching source, build, bytecode, address, network, and deployment manifest.