Blockchain Implementation
A blockchain implementation records commitments derived from ALX Blocks. The implementation can record an individual blockHash or a Merkle root hash representing multiple Block hashes.
Blockchain infrastructure remains optional. Block creation, deterministic identity, declared lineage, and local verification operate independently of a blockchain implementation.
Implementation Model
| Element | Responsibility |
|---|---|
| Commitment input | Accept a deterministic blockHash or Merkle root hash. |
| Record context | Identify the network, contract or program, transaction, and chain position. |
| Record lookup | Expose enough data to determine whether the supplied commitment was recorded. |
| Local verification | Recompute Block identity and verify Merkle inclusion outside the blockchain implementation. |
| Application policy | Define authorization, fees, retention, finality requirements, and accepted evidence. |
Implementation Responsibilities
- Record
- Verify
- Operate
Define the commitment value format and the operation that records the value. Preserve the transaction identifier, chain position, submitting account, and chain timestamp when the selected network provides the corresponding properties.
The blockchain implementation can accept individual Block hashes, Merkle root hashes, or both. The interface should identify the submitted commitment form.
Bind each verification result to the selected network, contract or program identifier, transaction, and chain position. Apply the finality requirements selected by the application.
Verify complete ALX Blocks with protocol rules. Verify Merkle inclusion with the Merkle construction rules used to produce the supplied root hash.
Document submission permissions, administrative controls, upgrade behavior, fee requirements, key management, network finality, reorganization handling, and monitoring. Publish deployment evidence that connects the deployed code to reviewed source, build artifacts, and the selected network address.
Verification Boundary
A blockchain record establishes that the supplied commitment was recorded within the evaluated chain context. Additional evidence and application policy determine Block validity, content meaning, authorship, ownership, approval, authorization, and availability. Implementations can use different networks, contract interfaces, programs, and operational controls while preserving ALX Block identity.
When to Use a Blockchain Implementation
Use a blockchain implementation when an application requires verifiable onchain commitments tied to a specific network and block position. ALX Block data and protocol verification remain independent of the blockchain, while applications define their requirements for commitment verification, network trust, and transaction finality.