Skip to main content

Deployment Manifest

A deployment manifest connects a contract address to the source, compiler settings, bytecode, transaction, and review evidence used for that deployment. The record gives integrators the inputs needed to reproduce and inspect a release.

Why Deployment Evidence Matters​

An address alone cannot show which source or compiler produced the deployed bytecode. The manifest keeps those values together and records whether explorer verification and activation checks succeeded.

How Publication Works​

A complete record includes the protocol version, contract version, network, chain ID, address, transaction hash, deployer, compiler settings, source commit, ABI hash, bytecode hash, explorer result, audit reference, and activation status.

When a deployment is published, the finalized JSON record is reserved under /deployments/{network}/, for example /deployments/base/alx-anchor.json. No public instance is published until a supported deployment exists.

When to Use a Manifest​

Use a completed manifest before configuring an integration for a network deployment. No supported public ALX contract deployment is currently recorded.

The schema records protocol and contract versions, network, contract, source, compiler, artifact hashes, explorer evidence, audit reference, and status.

A deployment record must validate against /schemas/alx-deployment-manifest.schema.json.

Required evidence includes protocol version, contract version, network name, chain ID, contract name and address, deployment transaction, deployer, source commit, compiler version and settings, source hash, ABI hash, deployed bytecode hash, explorer verification, audit reference, and activation status.

The public schema describes complete evidence only. Incomplete drafts are not representable; keep them private until explorer verification and audit references are ready.