Storage-proof boundary
@monolythium/[email protected] includes an RpcClient.lythGetStorageProof(...) method and related types. That package surface alone does not establish that a particular endpoint serves the method, that its proof format is stable, or that an application has verified the proof against trusted finality data.
This documentation therefore does not publish an executable storage-proof or value-transfer recipe. Before relying on the method, an integrator must pin the exact chain and runtime, obtain the versioned proof schema, independently implement or audit verification, define trusted roots and retention behavior, and exercise malformed, stale, wrong-chain, non-inclusion, and re-genesis cases.
Explicit interop boundary
Section titled “Explicit interop boundary”There is no in-tree bridge or Foundation-operated production route. A storage-proof type or historical cross-chain example is not bridge activation evidence and must not be used to construct a value-transfer path.
Safe starting point
Section titled “Safe starting point”Use the verified read-only identity probes first. If a future release publishes storage proofs as a supported integration contract, this page must be updated with the exact runtime pin, proof specification, verifier test vectors, and security assumptions before an executable example is added.