Projects and existing evidence

As an integrator, move from a Lockness role to the existing project, documentation and evidence behind it. Lockness defines the cross-project contracts; these repositories own implementations.

CSMT-UTXO: the existing engine

Cardano UTxO CSMT already follows the chain, maintains a compact sparse Merkle tree over the live UTxO set, computes roots and serves inclusion proofs. Its current-tip commitment machinery is a reuse candidate for anchors. The ledger-provider role is a substantially larger indexing and storage service that can reuse that machinery, rather than an HTTP extension alone.

At revision f513705, the documented API serves inclusion proofs, historical roots and address lookup; the storage schema stores UTxOs, tree nodes and rollback operations, not a transaction-history archive.

Role	Existing machinery to assess	Additional Lockness contract and work
Anchor	Chain following, current UTxO commitment and rollback	Signed publication format, key policy and per-block stream; independently validated chain source
Ledger provider	Follower, tree and proof machinery	Asset indexes, transaction/reference archive, retained chainpoint views, leases and explicit refusals

Whether this is delivered by extending the existing service or composing its libraries in a new indexer remains an implementation decision. Historical roots alone do not provide historical query views.

Use its architecture, database schema, getting started guide and API reference to explore what exists.

Its benchmark code covers CSMT insertion, storage and deserialization paths. Start cost assessment there and at its runtime metrics. Benchmark definitions are not a measured Lockness deployment budget: distinguish full commitment maintenance from KV-only baselines, include the node's cost, and measure the additional archive, retained-view and serving workload separately. See the measurement roadmap.

The existing internal-index epic and HTTP epic need reconciliation with Lockness contracts. They describe the earlier architecture. Reconciliation is a tracked assignment prerequisite; the CSMT lane remains paused, and this documentation review does not change those tickets.

Application consumers

Project	Explore	Connection to Lockness
MPFS	Repository and documentation · existing facts verifier	Prior implementation checks reconstructed facts against the application root in an anchored state output.
Singular	Repository and documentation	Application consumer whose state interpretation and proof construction stay outside the generic ledger service.

Follow the asset and NFT concepts into the proof-composition sequence. MPFS’s linked verifier consumes backend facts; replay from transaction CBOR still needs a deterministic application interpreter and complete reconstruction inputs. The proposed history-retrieval integration still needs the complete journey; these links do not claim it is delivered.

Assess the evidence

The decision record distinguishes existing MPFS verification and CSMT work from unresolved Lockness guarantees. The roadmap describes the next evidence needed. The trust and availability model explains which commitments applications would purchase.