BridgeLive Chain And Passage Surface
Bridge is the stack's passage chain for outside contact. It records lane status, native acquisition evidence, held-asset labels, vault posture, finality, delivery, refusal, quarantine, and receipts; receiver chains decide what those facts mean.
Passage is visible; admission stays local. Bridge shows the chain, lanes, requests, pool or vault labels, refusals, pending states, and receipts. Host exposure, fallback lanes, and counterparty routes stay bounded by Bridge law and receiver rules.
Reading Bridge is free. Public labels do not create reward eligibility, allocation, ownership, governance rights, redemption, or future entitlement.
Bridge has a running public chain surface. Use the status page for the freshest generated feed and the lane page for what each route currently permits.
Bridge now has a public product path: classify payment, quote the route, source inventory when policy allows, assign host-vault evidence, and hand off a receiver acknowledgement.
Caller, payment denom, amount, host asset, receiver, and boundary are explicit.
Bridge records admitted, refused, quarantined, host-native, or representation-only posture.
Asset cost, host execution, proof and memory, Bridge margin, and risk buffer stay separate.
Inventory may be used only inside policy; shortfall can defer, refuse, or quarantine.
Receiver acknowledgement is visible; receiver-local admission remains receiver-owned.
Bridge-specific route, pool, vault, receipt, and readiness labels belong here, not scattered across the main site.
The overview stays readable. Open the page that owns the detail you want.
The homepage stays broad. Detailed evidence lives on the product and proof pages.
This surface is for outside contact, native acquisition intent, passage, host evidence, route labels, vault posture, proof, and receipts.
Bridge delivery can land evidence at a receiver, but Core still controls custody, quarantine, refusal, and local value meaning.
Infra can retain Bridge receipts and proofs as paid memory work without becoming the Bridge or the receiving chain.
Liquid can use Bridge provenance as ingress context, then must pass its own risk, clearing, and settlement rules.
Bridge has to expose movement without letting movement turn into authority.
A packet crossing, route ticket, or receipt does not force Core, Infra, Liquid, or any destination chain to accept meaning or value.
A receipt proves Bridge handling. It does not prove endorsement, moral legitimacy, accounting acceptance, or production readiness.
Usefulness, public attention, feeder evidence, or route-shaped labels do not create a route owner, public bridge-across product, reward, allocation, or entitlement.