Skip to main content

Protocol Specification

The ALX Protocol specification defines Block structure, canonicalization, deterministic identity, declared parent relationships, and verification. Independent implementations reproduce protocol-defined results without relying on specific applications, storage systems, transport mechanisms, or blockchain infrastructure. For a runnable introduction, see Quick Start.

Specifications​

  1. Canonicalization — Deterministic serialization of supported ALX values.
  2. Block — Block structure and required protocol fields.
  3. Block Identity — Derivation of contentHash and blockHash.
  4. Parent Relationships — Parent declarations and normalization rules.
  5. Lineage Graphs — Graph structure, validation, and completeness.
  6. Lineage and Attribution — Attribution Traces and structural lineage.
  7. Verification — Block validation, Graph verification, and optional evidence.
  8. Trust Boundary — Scope and limitations of verification claims.
  9. Signing — Optional cryptographic attestations and signed requests.
  10. Protocol Non-Goals — Responsibilities excluded from the core protocol.
  11. Conformance — Requirements for interoperable implementations.
  12. JSON Schemas — Published protocol and extension schemas.

Normative Sources​

Four sources govern ALX protocol behavior together: protocol/spec.md in the ALX Protocol repository, the JSON Schemas, the Conformance Vectors, and the error code registry. The pages above explain these sources. When a page and a source differ, the source governs. The required-suite manifest lists the conformance suites every implementation must pass.