Skip to content

Canonical state and freshness

Torq integrations consume shared state through:

Chain -> Indexer -> Projector -> Postgres -> API

Do not reconstruct shared protocol state from RPC. The API returns freshness evidence including status, lag, block, projection time, snapshot time, and a reason when state is stale or missing.

Workflow lifecycle

Typed intents were built against a named canonical snapshot.
prepared
Your signer submitted and registered the transaction.
submitted
The transaction is in a block; product state is not yet complete.
mined
The relevant chain events were consumed.
indexed
Canonical Postgres reads show the expected state.
Unknown
Every declared postcondition passed.
final success
Execution, indexing, reorg handling, or canonical readback failed.
failed

Every prepared workflow includes a snapshot hash, expiry, simulation requirement, blocked reasons, and expected postconditions. Re-prepare after expiry or stale-state rejection.