Deployment Requirements
A supported blockchain deployment connects one network address to reviewed source, reproducible build artifacts, chain evidence, and recorded security-review status.
The ALX on Base page publishes the current status and evidence for the Base implementation. No supported public ALX contract address is currently published.
Required Evidence
| Category | Required values |
|---|---|
| Identity | Protocol version, contract version, network, chain ID, contract name, and address |
| Provenance | Deployment transaction, deployment block, deployer, and deployment time |
| Source | Source revision, source hash, and verified source location |
| Build | Compiler version, compiler settings, ABI hash, and deployed bytecode hash |
| Review | Test results, security-review status, audit reference, and activation status |
| Publication | Completed deployment manifest and explorer verification |
Publication Requirements
Publish a supported address after the deployment record establishes:
- reviewed source and a recorded source revision;
- reproducible compiler settings and matching artifacts;
- matching ABI and deployed bytecode hashes;
- transaction evidence on the declared network;
- explorer verification;
- completed tests and recorded security-review status; and
- an active deployment manifest.
Integration Requirement
Configure a public integration from the deployment record published for the selected network. Record the contract address, chain ID, deployment manifest, and application finality policy with the integration configuration.
Block creation and local Block verification do not require a blockchain deployment.
When to Use Deployment Requirements
Use the Deployment Requirements before publishing, configuring, or endorsing a blockchain deployment. Evaluate the deployment record again after a contract, network, source revision, build configuration, or security-review status changes.