Security

ALX verification establishes deterministic Block identity and the consistency of declared parent relationships. Optional signatures, Merkle proofs, and blockchain commitments establish separate properties. Each mechanism establishes one specific property, and applications decide how the results support their security requirements.

Explore

Before integrating ALX into a security-sensitive workflow:

1. Trust Model: identify the actors, evidence, and assumptions that apply to the application.
2. Known Limitations: record the protocol, implementation, package, deployment, and verification constraints.
3. Trust Boundary: match each verification result to the claim the result supports before making security decisions.
4. EVM Security: review the contract and deployment properties when the application uses blockchain commitments.

Deployment Status

ALXAnchor is deployed on Base mainnet (chain ID 8453) at 0xF6E12e7052F15c44AE926E50A0a68FAB5E35ea46, with source and ABI verified on BaseScan. The independent audit is complete; the audit report is not yet published. ALX on Base publishes the deployment evidence.