Security Model
ALX security begins with deterministic Block identity and verification of declared relationships. Applications can evaluate optional cryptographic evidence and external commitments when additional assurances are required.
Each mechanism establishes a specific property. Security depends on verifying the correct data, relationships, evidence, and external context for the application’s requirements.
Security Properties
Core ALX verification establishes deterministic Block identity and structural properties of available declared relationships. Optional signatures, Merkle proofs, and blockchain commitments add mechanism-specific evidence.
Security Boundary
Each verification mechanism establishes only the property evaluated by that mechanism. Block and graph verification do not establish factual truth, authorship, ownership, authorization, safety, legal validity, or application trust. Applications interpret additional evidence and define acceptance policy.
Security Review
Before integrating ALX into a security-sensitive workflow:
- Trust Model: identify the actors, evidence, and assumptions relevant to the application.
- Known Limitations: the protocol, implementation, package, deployment, and verification constraints.
- Protocol Trust Boundary: read it before translating verification results into application-level claims or security decisions.
- EVM Security: if using blockchain commitments, alongside the security properties of the specific contract and deployment in use.
No independent smart-contract audit or supported public deployment is currently recorded.