Deployment Requirements
A supported blockchain deployment connects one network address to explorer-verified source, chain evidence, and a recorded security-review status.
The ALX on Base page publishes the current status and evidence for the Base implementation. ALXAnchor is deployed on Base mainnet at 0xF6E12e7052F15c44AE926E50A0a68FAB5E35ea46.
ALXAnchor Source Design
The deployed ALXAnchor's runtime bytecode matches the contracts/src/ALXAnchor.sol source at revision b2c63ac. The table lists the characteristics of that source. Verify the deployed address, bytecode, source, and review record before relying on these properties for an integration.
| Property | Current source behavior |
|---|---|
| Commitment input | A bytes32 value. The contract stores no hash type; the application records whether each value is a blockHash or a Merkle root hash. |
| Submission | Permissionless. |
| Administration and upgrades | No administrator or built-in upgrade mechanism. Deployment through a separate proxy would require its own verification. |
| Recorded evidence | The first chain timestamp and submitting address for each value. |
| Duplicate handling | anchor rejects an already-recorded value; anchorBatch skips previously recorded values. |
| Batch size | anchorBatch accepts 2 to 256 values and reverts with BatchTooSmall or BatchTooLarge otherwise. |
Required Evidence
A supported Base deployment requires the evidence in the table. A deployment manifest adds the deployer, source commit and hash, compiler settings, ABI and bytecode hashes, explorer verification, and audit reference in one machine-readable record. A manifest is recommended evidence, not a requirement for a supported address.
| Category | Required values |
|---|---|
| Identity | Network, chain ID, contract name, and address |
| Provenance | Deployment transaction |
| Source | Source and ABI verified on the network's block explorer |
| Review | Security-review status and the date of the last review |
| Publication | An active status and the values above on the ALX on Base page |
Publication Requirements
Reproducible compiler settings, matching ABI and bytecode hashes, and a published deployment manifest strengthen a deployment record and are recommended. Publish a supported address after the deployment record establishes:
- transaction evidence on the declared network;
- source and ABI verified on the network's block explorer;
- a recorded security-review status; and
- an active status on the ALX on Base page.
Deployment Manifest
A deployment manifest is a JSON record that connects a contract address to the source, compiler settings, bytecode, transaction, and review evidence used for the deployment. A manifest validates against /schemas/alx-deployment-manifest.schema.json. The schema requires the manifest version, protocol version, contract version, network, chain ID, contract name and address, deployment transaction, deployer, compiler, source commit, source hash, ABI hash, deployed bytecode hash, explorer verification, audit reference, and activation status. The schema describes complete evidence only; keep drafts private until explorer verification and audit references are ready.
A finalized manifest is published under /deployments/{network}/, for example /deployments/base/alx-anchor.json, when the activation status is active. No manifest is published yet for the Base deployment.
Integration Requirement
Configure a public integration from the deployment record published for the selected network. Record the contract address, chain ID, and application finality policy with the integration configuration, and the deployment manifest when one is published. 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.