Q markBridgeLive Chain And Passage Surface

Bridge moves value by lane, not by guesswork.

Bridge is the passage chain in the QUAD stack. It gives a route a quote, checks the source asset, records the receipt, and hands off evidence to the receiver. Each lane says what it can move, what it is waiting on, and what it refuses.

Bridge is live

Quote first. Move second. Admit locally. Bridge shows route lanes, source-pool inventory, vault labels, refusals, pending states, and receipts. It is not a generic wrapped-token conveyor or a promise that every visible lane is payable.

Open Intake Lane View Asset Pools How Bridge Works Lane Status
Product
Quote-first passage
Ledger
Asset-first pools
Status
Live chain, lane-gated routes

Reading Bridge is free. Public labels do not create reward eligibility, allocation, ownership, governance rights, redemption, or future entitlement.

Start with a quote Pools and ledger Proof surfaces

What Bridge Does

The homepage translates the product. Raw runtime labels live on the status and data pages.

Quote a lane

Pick the source asset, target output, receiver, and amount. Bridge returns the route shape and exact instruction when that lane is payable.

Open intake
Check inventory

Visible pools are shown by asset: ETH, USDC, PAXG, INJ, Cosmos assets, and zero-capacity labels where relevant.

View ledger
Read receipts

Proof pages show what Bridge handled without pretending that receipt equals receiver-chain admission.

Open proof
Networkbridge-1 Heightloading Routeslane-gated Freshnessstatus page

Bridge product journey

Bridge now has a public product path: request, classify, quote, source, move, hand off, and record. Each step has its own evidence and refusal boundary.

Request

Source asset, target asset, receiver, amount, and constraints are explicit before movement.

Classify

Bridge records admitted, refused, quarantined, host-native, or representation-only posture.

Quote

Asset cost, host execution, proof and memory, Bridge margin, and risk buffer stay separate.

Source

Inventory, vault, pool, or acquisition path may be used only inside policy.

Move / Handoff

Passage and receiver acknowledgement are visible; receiver-local admission remains receiver-owned.

Open product journey Passage intake Native acquisition Inventory truth

Product Snapshot

Bridge-specific route, pool, vault, receipt, and readiness labels belong here, but the homepage keeps them readable.

Movement modelLane by lane

No cached address, guessed memo, or generic bridge-across claim should be treated as payable.

Visible pools14 asset rows

The ledger shows assets individually; it does not flatten the basket into an unsourced TVL number.

ReceiptsPublic proof, bounded meaning

Bridge receipts prove Bridge handling. Receiver chains keep their own accounting authority.

Public routesQuote gated

Routes open only when lane status, source finality, receiver matching, and proof quality allow them.

Product paths

The overview stays readable. Open the page that owns the detail you want.

AcquisitionIntent, quote, route-output class, host assignment, funding evidence, receipts, and refusal. Intake laneSource asset, target asset, route quote shape, memo boundary, and no-payment-until-live receiver rule. Product journeyNative liquidity purchase surface, caller-neutral receiver classes, receipt trail, and gated public movement. Lane statusOpen, paused, pending, watch-only, and closed route posture for live Bridge lanes. LedgerProtocol inventory, user bonded value, assigned host vaults, host-fee categories, buffers, receipts, and quarantine. Inventory truthCommitted orders, local inventory receipts, shortfall states, and live-balance boundaries. VaultsGold host-native posture, silver fallback, lane candidates, and endpoint-access boundaries.
Open evidence, gates, and data routes
GatesVerifier, signer, finality, DA receipt, quarantine/refusal, fee/dust, and authority gates. CounterpartiesQUAD, Infra, and Liquid receiver boundaries, route-only posture, and local meaning rules. Host evidenceSource-pool receipts, host-contract freeze law, fresh RPC observations, and historical smoke evidence. StatusPhase, route posture, freshness, and public readiness labels. ProofLane, finality, proof, receipt, and quarantine evidence categories. BoundaryNon-inheritance rules: transit is not admission, receipt is not truth, route power is not authority. DataRaw public JSON and generated labels for readers and tools.

Bridge in one minute

The homepage stays broad. Detailed evidence lives on the product and proof pages.

You are on Bridge

This surface is for outside contact, native acquisition intent, passage, host evidence, route labels, vault posture, proof, and receipts.

OBOL pays passage

OBOL supports crossing, route work, receipt work, and border friction. It does not become the destination asset or receiver-chain authority.

Core decides Core meaning

Bridge delivery can land evidence at a receiver, but Core still controls custody, quarantine, refusal, and local value meaning.

Infra remembers evidence

Infra can retain Bridge receipts and proofs as paid memory work without becoming the Bridge or the receiving chain.

Liquid moves locally

Liquid can use Bridge provenance as ingress context, then must pass its own risk, clearing, and settlement rules.

Acquisition flow Intake lane Held-asset ledger Vault lanes Proof surfaces Counterparties

Boundary rule

Bridge has to expose movement without letting movement turn into authority.

Transit is not admission

A packet crossing, route ticket, or receipt does not force Core, Infra, Liquid, or any destination chain to accept meaning or value.

Receipt is not truth

A receipt proves Bridge handling. It does not prove endorsement, moral legitimacy, accounting acceptance, or production readiness.

Route power is not authority

Usefulness, public attention, feeder evidence, or route-shaped labels do not create a route owner, public bridge-across product, reward, allocation, or entitlement.