BridgeLane Status
The lane matrix starts from the current Bridge chain feed, then names route posture separately.
These are public status labels. They are not private route logic, caps, signing policy, or execution instructions.
| Lane | Current posture | What it means | Must not infer |
|---|---|---|---|
| Bridge chain | loading | Public RPC status and chain height are observable. | RPC visibility is not universal truth or route execution. |
| Native acquisition | gated product path | Intent, payment evidence, quote, inventory, host-vault evidence, and handoff can be recorded when receipts satisfy the lane. | No automatic public bridge-across service. |
| Core receiver | route-only boundary | Bridge may deliver evidence toward Core's boundary. | Bridge does not admit Core Treasury, Reserve, Mint, Alloc, Seller, or quarantine state. |
| Infra receiver | receipt-backed path | Infra can receive Bridge evidence and owner-chain acknowledgements when the receiver path is proven. | Infra memory is not Bridge authority or destination admission. |
| Liquid receiver | sleep-gated | Liquid routing waits for the relevant native-vault and receiver boundary to be active. | No Liquid settlement, clearing, market execution, or route credit. |
| IBC packets | handoff and ack evidence | Bridge can show packet-backed receiver acknowledgement evidence where the receipt exists. | Packet ack is not receiver-local accounting unless receiver proves it. |
| ETH host lane | evidence-gated | Host-native posture, contract/factory evidence, finality, and smoke receipts can be shown. | No public host execution or wrapped ETH claim by convenience. |
| BTC host lane | observation and source-pool evidence | BTC source-pool and host observation proofs can be referenced where receipts are public. | No spend authority, custody promise, or redemption path from observation alone. |
| Refund | receipt-required | Refund posture must name the request, reason, amount, and settlement state. | No refund is implied by a failed route unless a refund receipt says so. |
| Refusal | open as terminal state | Bridge can refuse missing fields, expired quotes, unsupported denoms, stale provider data, wrong contract, or disabled signer paths. | Refusal is not punishment, entitlement, or discretionary seizure. |
| Quarantine | open as containment state | Unsupported or boundary-breaking value can be contained under explicit receipt labels. | Quarantine is not admission, backing, sale, or route success. |
| Provider fallback | loading | Fallback readiness and activation are separate labels. | A ready fallback is not an activated route. |
Open the page that owns the evidence instead of treating this lane matrix as the whole product.