Skip to main content

Module source

Module source 

Source

Structs§

CommitSources
Ordered labelled sources tried until one returns bytes. A miss or error moves to the next source; the set errors only when every source errored. The error table is locked only to read or write, never across a fetch.
LitecoinSource
Checkpoint-relative Litecoin light client. Does not validate scripts, UTXOs or MWEB consensus. Opening it does not start network connections; the first sync attempt does. An application start before the configured anchor is an explicit error, never silently replaced with the anchor’s height.
LocalRpcCommitSource
Optional local Litecoin Core: it may start, stop or restart at any time. Holds only the URL and cookie path; every lookup and probe reads the cookie, and a node is rebuilt and its txindex verified whenever the cookie changes.
PublicCommitSource
Default public providers for one chain, without a light client. Creating it does no I/O; the first fetch builds the Node. A failed build is not rebuilt for RETRY and its error is returned meanwhile. Untrusted bytes.
RuntimeCommitSource
Share an explicitly configured, owner-provided runtime Node. Constructing this wrapper or reading its chain creates no Node, connection or defaults. Only fetch calls the existing Node; no header/placement authority is added.

Traits§

ChainSource
Port implemented by a chain verifier, not by an untrusted remote JSON API. The implementation owns header difficulty, PoW and branch selection. Bodies remain untrusted bytes and are checked again against the selected header. Provider-claimed observations used by autonomous clients are a different contract and do not enter this port by relabelling them as verified.
CommitSource
Untrusted auxiliary parent bytes, not a chain verifier. The chain getter reads local configuration without I/O. Each fetch must bound its own I/O; Engine cancellation is cooperative and cannot interrupt a running fetch.

Functions§

verify_parent
Decode with the Engine’s chain decoder, so Litecoin MWEB/HogEx encodings are accepted, and require the computed TXID to equal the requested one.