Distribution and Commitments
ALX Blocks are created and verified locally. Content distribution, commitment evidence, and application discovery are optional layers around that deterministic core.
Choose infrastructure by the operational capability the application requires. Every layer preserves contentHash, blockHash, and declared parentHashes.
Choose a Path
- Application storage fits when one application controls Block persistence and retrieval.
- IPFS fits when content-addressed distribution by CID is useful. Keep the CID-to-
blockHashmapping in your application and arrange pinning when availability matters. Validate each retrieved Block and compare itsblockHashwith the expected identity. - Blockchain Commitments fit when an independently verifiable record of a
blockHashor Merkle root hash is useful. The commitment records a value, not the Block content, ownership, correctness, or availability. - XNDR Network fits when an application needs discovery and indexing of observed Blocks across sources. XNDR Network is an application layer built around ALX, not a requirement of the protocol.
Architecture at a Glance
Each layer adds a separate capability. Applications can combine the layers required by a workflow while preserving the same ALX Block identity.
| Concern | ALX Protocol | IPFS | Blockchain Commitments | XNDR Network |
|---|---|---|---|---|
| Primary role | Defines Block structure, identity, lineage, and verification | Distributes bytes by CID | Records a Block-derived commitment | Discovers and indexes observed Blocks |
| Identifier | contentHash and blockHash | CID | blockHash or Merkle root hash | Source-scoped indexed references |
| Content handling | Validates supplied Block content | Retrieves serialized content | Keeps Block content offchain | Presents application-governed indexed content |
| Application choice | Required protocol layer | Optional distribution layer | Optional evidence layer | Optional application and discovery layer |
Keep the Boundaries Clear
A CID identifies stored bytes, not an ALX Block. A blockchain commitment is not Block storage or lineage. An index observation is not proof that a Block exists globally or that it was created at the observed time.
Start with the protocol data and local validation. Add only the distribution, commitment, or application infrastructure that the workflow needs.