Evidence Snapshot
The current product evidence is useful, but it does not unlock public value movement.
BridgeHost Evidence
The current product evidence is useful, but it does not unlock public value movement.
Bridge separates source-pool inventory from product solvency, reserve, collateral, and destination-chain admission.
Source-wallet inventory policy names which assets can be used inside a live lane.
Pool refill receipts are evidence of source-pool posture only.
Per-lane spend records, low-balance warnings, and overspend refusal keep routes bounded.
Pool balance is not reserve backing, collateral, product solvency, or a redemption promise.
Pool balance is not a guarantee that every target asset or route is currently open.
Public pages must not expose private wallet, key, seed, signer, or provider material.
Contract identity has to be frozen before a host lane can be treated seriously.
The interface shape is recorded before public activation language is allowed.
Source, runtime, creation, and artifact hashes are pinned for review.
Deployer, owner, admin, proxy, and upgrade posture are explicitly bounded.
Event schema and smoke records define what can be observed later.
Fresh endpoint evidence, production audit packet, and production acceptance are still missing.
Read-only host observations can support a drill without becoming destination movement.
Fresh RPC refresh records observe host-chain state. They do not admit destination value.
Observation does not mint wrapped assets or create Bridge custody authority.
Observation does not create sell, redeem, swap, or public exit access.
Source-pool receipts across the supported assets can be published without opening every downstream path.
USDC and PAXG owner-vault acknowledgements prove Bridge handoff only.
Each lane still requires fresh proof, fee posture, finality, receiver matching, and published opening status.
Open proof surfaces Production gates Readiness Raw public JSON