Protocol Architecture
ALX separates deterministic Block processing from the infrastructure applications use to store, exchange, discover, and govern Blocks.
Block creation, identity, lineage, and verification are defined by protocol rules and operate independently of storage, networking, authentication, indexing, governance, and blockchain infrastructure.
Architecture Model
ALX defines a deterministic protocol layer for creating and verifying Blocks.
Applications and external infrastructure determine how Blocks are stored, transported, indexed, discovered, accessed, and presented. The protocol boundary allows the same Block identities and declared relationships to move across different systems while remaining independently verifiable.
Protocol Layer
Block structure, canonicalization, identity derivation, parent normalization, declared lineage, and verification.
Application & Infrastructure Layer
Storage, transport, APIs, authentication, permissions, indexing, governance, user experience, and optional external commitments.
Applications and infrastructure operate around protocol-defined Blocks. They do not become required foundations for Block creation, identity, lineage, or verification.
Protocol Boundary
ALX standardizes the data and deterministic rules required for interoperable Blocks.
Applications determine the meaning of Block content and the policies governing content use. Infrastructure can change without changing the protocol-defined identity of an existing Block.
The protocol boundary allows independent applications, agents, organizations, and infrastructure providers to work with the same Block model without depending on a shared application stack.
Protocol Data Model
The sole protocol primitive is the Block. A v1 Block contains five fields:
| Field | Role |
|---|---|
content | JSON-serializable application payload |
parentHashes | Normalized set of declared parent Block identities |
contentHash | Deterministic identity of the canonicalized content |
blockHash | Deterministic identity of the content with its normalized parent set |
protocolVersion | Version marker for the Block algorithms; the v1 value is "1" |
contentHash identifies content independently of lineage. blockHash binds that content to its declared parents. protocolVersion is required on the Block and is excluded from v1 hash derivation.
Connected Blocks form a derivation graph by following declared parentHashes. Reverse children, descendants, and other index views are derived application concerns; they are not stored on the Block.
For field-level detail, see The Block, Block Identity, and Lineage Graphs.
Blockchain Commitments
Blockchain infrastructure can record commitments derived from ALX Blocks without becoming part of Block creation or identity.
Blockchain Commitments define a chain-neutral path from Block hashes to Merkle root hash commitments and inclusion proofs. Blockchain Implementation defines the responsibilities of an optional application-selected blockchain implementation.
Blockchain commitments are optional. Creating, identifying, and verifying an ALX Block does not require a blockchain.