Indexing Model
XNDR Network builds searchable views of ALX Blocks from configured sources. Results report the selected scope, availability, relationships, and completeness.
Scope
A scope is a named, versioned set of configured sources, such as chains, registries, or archives. The scope parameter selects that set; each query result identifies the scope that answered the query.
ALX Protocol defines canonical Block identity and declared parents. XNDR Network records observations separately for each scope, so one canonical Block can have different observation histories across scopes.
XNDR Network Data Flow
XNDR Network retrieves Blocks from configured sources, checks Block structure and identity against ALX Protocol rules, and records source observations. For queries, XNDR Network combines each Block's declared parents with children observed in the selected scope. The Block Explorer and REST API return indexed records with that scope context.
Canonical Facts and Index Observations
Responses separate protocol-defined Block information from index observations and query context.
| Information | Meaning |
|---|---|
| Canonical Block Facts | Protocol-defined identity, content, version, and declared parentHashes. |
| Index Observations | Source, first-observed time, availability, reverse relationships, and resolution status recorded within a scope. |
| Query Context | Scope, revision, pagination, and completeness information for one response. |
firstObservedAt records when the selected scope first observed a Block, not when the Block was created.
Relationship Resolution
Declared parents are protocol-defined relationships in a Block’s parentHashes. XNDR Network resolves declared parents against the selected scope and reports each parent record’s availability.
Indexed children are reverse relationships observed within the selected scope. available: false means the scope has not indexed a declared parent; an absent child means only that the scope has not observed one. Interfaces and integrations can present those two conditions accurately.
Completeness and Pagination
Graph and list responses include scope and pagination information so clients can interpret result boundaries.
A bounded neighborhood reports the graph portion retrieved within the selected scope, traversal limits, node budgets, and pagination state.
The response reports one of four completeness values:
complete-within-scope: Every configured source is caught up to the source’s advertised boundary, and the query stayed within the query budget.partial: At least one source has a successful observation, but not every configured source is caught up.unknown: XNDR Network has not established completeness for the scope.truncated: A query budget or pagination boundary cut the result short; check the response's page and traversal metadata.
Even complete-within-scope does not claim coverage of every ALX Block. See Response Envelope for the fields that describe the result boundary.