Crate exoware_qmdb 

Store-backed bridge for Commonware authenticated storage proofs.

The crate currently supports multiple Commonware authenticated backends:

• ordered QMDB (qmdb::any and qmdb::current::ordered)
• unordered QMDB (qmdb::any::unordered and current hit proofs when callers upload current-boundary rows)
• immutable (qmdb::immutable)
• keyless (qmdb::keyless)

Writers upload exact Commonware operations into the Exoware store, then publish an externally authoritative watermark once the uploaded prefix is complete.

Uploads may still happen concurrently and out of order. Current batch-boundary state may also be uploaded ahead of publication. Only watermark publication is monotonic: publishing watermark W means the whole contiguous prefix [0, W] is available and may now be trusted by readers.

Readers fence historical queries against that low watermark. Historical proofs use the global ops Merkle nodes stored by Position.

Current QMDB proofs use versioned current-state deltas:

• bitmap chunk rows
• grafted-node rows

Those rows are versioned by uploaded batch boundary Location, not by the final published watermark. That is what preserves lower-boundary current proofs below a later published low watermark.

Re-exports

pub use error::ProofKind;

pub use error::QmdbError;

pub use proof::CurrentOperationRangeProofResult;

pub use proof::OperationRangeCheckpoint;

pub use proof::RawKeyValueProof;

pub use proof::RawMultiProof;

pub use proof::VariantRoot;

pub use proof::VerifiedCurrentRange;

pub use proof::VerifiedKeyLookup;

pub use proof::VerifiedKeyRange;

pub use proof::VerifiedKeyValue;

pub use proof::VerifiedMultiOperations;

pub use proof::VerifiedOperationRange;

pub use proof::VerifiedUnorderedKeyValue;

pub use proof::VerifiedVariantRange;

Modules

error

proof

proto

prune

Structs

BuiltImmutableUpload

BuiltKeylessUpload

Deterministic output of a keyless row-build.

BuiltOrderedUpload

BuiltUnorderedUpload

Deterministic output of an unordered row-build.

CurrentBoundaryState

Current-state rows for one uploaded current batch boundary.

CurrentOperationClient

Client for qmdb.v1.CurrentOperationService, parameterized on the Merkle family and current-state operation type.

CurrentOperationRangeProof

CurrentSyncResolver

Store-backed resolver for Commonware current::sync over Exoware QMDB’s operation-log API.

ImmutableClient

ImmutableWriter

Sole-writer immutable QMDB helper. Pipelining, flushing, failure, and sole-writer contract are identical to KeylessWriter — see its docs for details.

KeylessClient

KeylessWriter

Sole-writer keyless QMDB helper.

OperationLogClient

Client for qmdb.v1.OperationLogService, parameterized on the Merkle family and backend operation type.

OperationLogRangeProof

OperationLogSubscribeProof

OperationLogSubscription

OperationLogSyncResolver

Store-backed resolver for Commonware QMDB sync over Exoware QMDB’s operation-log API.

OrderedClient

OrderedConnect

OrderedConnectClient

OrderedWriter

Sole-writer ordered QMDB helper. Pipelining, flushing, failure, and sole-writer contract are identical to KeylessWriter — see its docs for details. prepare_upload additionally requires the caller-supplied CurrentBoundaryState for the batch.

PreparedUpload

A QMDB upload that has reserved writer state and encoded its Store rows, but has not yet been persisted.

PreparedWatermark

A prepared QMDB watermark row that should be staged into the same Store batch as the uploads it publishes.

PublishedCheckpoint

Writer publication point that is known to be durable in Store.

UnorderedClient

UnorderedConnect

UnorderedConnectClient

UnorderedWriter

Sole-writer unordered QMDB helper. Pipelining, flushing, failure, and sole-writer contract are identical to KeylessWriter — see its docs for details.

UploadReceipt

Metadata returned after uploading one batch of QMDB operations.

VersionedValue

Historical value resolved for one logical key.

WriterState

Caller-owned frontier for resuming a single-writer helper without reading the store.

Enums

QmdbVariant

QMDB proof/root variant supported by exoware-qmdb.

Constants

MAX_OPERATION_SIZE

Maximum encoded operation size for QMDB key and value payloads (u16 length on the wire).

Functions

build_immutable_upload

build_keyless_upload

Pure function: from the Merkle peaks preceding the batch, compute every store row needed to persist ops as a single atomic PUT. No I/O.

build_ordered_upload

Build every store row for one ordered batch: op rows, update-index rows, presence row, Merkle node rows (derived from the supplied peaks), current-state rows (from the caller-supplied current_boundary), and optionally the watermark row. No I/O.

build_unordered_upload

Pure row-build for an unordered batch. Produces op rows, update-index rows for keyed ops, presence row, Merkle node rows, and (optionally) the watermark row.

immutable_operation_log_connect_stack

keyless_operation_log_connect_stack

ordered_connect_stack

Mount key lookup, ordered key range, and operation subscription services on one endpoint, so a single HTTP URL serves the full ordered-QMDB surface.

recover_boundary_state

Recover the current-boundary delta for one batch from local proof material emitted by a Commonware current QMDB.

unordered_connect_stack

Mount current key lookup and operation subscription services on one unordered-QMDB endpoint. Unordered supports hit proofs for explicit keys but does not expose key-space range or missing-key exclusion proofs.

unordered_operation_log_connect_stack