Q token mark QUADPublic Accountability

Bridge market path

Controlled Passage, Not Blind Bridging

Bridge is the passage surface. It records native acquisition, source-pool use, owner vaults, route-output classification, host evidence, receipts, refusal, and quarantine without forcing another surface to admit the result.

The Fast Answer

Bridge turns a movement request into a bounded passage record.

It can show what was requested, what denom was observed, which source pool or host lane was named, which receipt exists, and which claims stayed closed. It does not make Bridge a wallet, AMM, exchange, wrapper minter, redemption desk, or destination-admission authority.

Current Bridge Path

Use the Bridge-owned subdomain for current product routes. The main domain explains how to read them.

1. Open BridgeStart at the Bridge product surface for acquisition, inventory, ledger, vault, gate, proof, data, and status routes. 2. Read product journeyFollow buyer intent, source-pool mapping, owner vaults, terminal receipts, and movement-closed labels. 3. Check acquisitionRead intent, quote, payment denom, output denom, host assignment, funding evidence, receipt, and refusal posture. 4. Check inventory truthSeparate receipt-ledger inventory from live host balance, solvency, backing, or redemption claims. 5. Check vault lanesRead native/gold posture, silver representation posture, host-lane gates, and endpoint-activation limits. 6. Check receiptsUse proof, host evidence, counterparties, status, and data routes before trusting a stronger claim.

What Bridge Owns

Bridge is useful because it keeps movement, proof, and admission separate.

Intent

Caller, request id, payment denom, output denom, host asset, amount, quote fields, and destination boundary should be explicit.

Classification

The actual output denom is classified as admitted, non-admitted, host-native, or representation-style before any route meaning is applied.

Inventory

Bridge can use source-pool receipts and fresh-sourcing policy, but receipt-ledger availability is not live host balance.

Owner vaults

Bridge separates the shared Bridge source pool from the purchaser or receiver owner vault after policy passes.

Receipts

Bridge records payment observation, fee settlement, route evidence, receiver acknowledgement, refusal, quarantine, and Infra export posture where applicable.

Closed states

Pending, refused, quarantined, stale, timed out, or destination-unknown are normal product states, not failures to hide.

Product Classes

Bridge should be read by class. A route label is not enough.

ClassPublic meaningNot implied
AcquisitionIntent, quote, payment/output denom classification, host asset request, fee, route evidence, and owner-vault destination label.Guaranteed fill, public swap, sale access, host execution, or destination admission.
InventoryLocal replenishment/depletion receipts, committed reservations, available receipt-ledger balance, shortfall policy, and fee totals.Live host balance, solvency, reserve backing, redemption, or guaranteed liquidity.
Reserve ledgerHost fees, buffers, route fees, refusal categories, refund posture, and surplus labels as accounting categories.Bank balance, NAV, redemption promise, yield, or hidden profit.
Vault lanesNative/gold posture, silver representation posture, host-lane candidates, and lane-specific gates.Endpoint access, wrapper/native equivalence, or production native-vault activation.
Host evidenceHost account assignment, provider/finality posture, contract or lane evidence, and stale/conflict labels.Host execution, private-key control, final custody, or receiving-chain accounting.
ProofDated proof id, receipt type, evidence class, what opened, what stayed closed, and freshness state.Universal truth, launch status, market access, or another chain's admission.
Refund and surplusRefund owed, refund pending, refund sent, surplus held, credited, quarantined, or terminalized.Reward, discretionary Bridge profit, yield, or price support.

Why Closed Until Evidence Exists Is A Strength

Bridge should refuse cleanly instead of inventing motion.

No destination admission by default

A Bridge handoff can name the receiver boundary. The receiving chain or owner route still decides local admission.

No wrapper shortcut

Host-native value must stay host-native unless a representation lane says exactly what it is and what it is not.

No hidden sell lane

Bridge does not quietly become a sell, redeem, swap, wrap, unwrap, or public-exit product.

No endpoint activation

An RPC, websocket, explorer, provider, contract address, or test surface does not activate a native-vault lane.

No loose receiver ack

Receiver acknowledgement should be tied to route/order evidence. Pending remains pending until the receiver proves its own state.

No payment execution claim

Payment receipts can observe evidence without executing bank movement, external settlement, custody, or destination accounting.

Provider And Counterparty Risk

A route can be shaped correctly and still wait on provider, host, relayer, fee, finality, or receiver evidence.

Provider path

Provider health, quorum, stale-head posture, rate limits, and rollback drills help readers judge observation quality without exposing raw endpoints.

Host chain

Host finality, reorg rules, fee/dust policy, contract posture, and signer posture belong to the lane being claimed.

Relayer state

Relayer activity, backlog, gas float, and retry state can support transport posture, but transport is not product movement by itself.

Receiver boundary

Core, Infra, Liquid, another stack chain, or an external owner route must publish its own admission, refusal, quarantine, or pending result.

Payment evidence

Source/input denom and settled output denom must stay separate when a conversion receipt is involved.

External blockers

Missing invoice, missing policy, stale provider, wrong contract, disabled signer, missing DA receipt, or missing receiver ack should downgrade the claim.

Current Evidence Readers Can Ask For

Bridge has product receipts to inspect. Each receipt opens only the named claim.

EvidenceWhat it can showBoundary
Payment receiptObserved payment denom, amount, request id, route reference, and observation-only flags.Not bank movement, external settlement, custody, or destination admission.
Inventory truthReceipt-ledger replenishment, depletion, reservations, available inventory, fees, surplus, and shortfall policy.Not live host balance or guaranteed liquidity.
Receiver acknowledgementReceiver id, receiver module, destination ref, and pending/admitted/refused/quarantined label where available.Bridge does not invent receiver accounting.
Route-output evidenceSource/input denom, settled output denom, classifier decision, and conversion binding where needed.Not wrapper/native equivalence or default denom selection.
Fee sinkBridge routing-fee record, spend-decision class, and external-settlement receipt where an allowed lane exists.Not hidden payment execution, reserve support, or foundation distribution.
Production readinessVerifier, signer, finality, DA receipt, quarantine/refusal, fee, and authority gates for native-vault lanes.Not production activation until every lane gate is closed by evidence.

Bridge Is Not

These refusals keep the product honest.

Not a live bridge claimPublic product routes and receipts do not open public value movement by themselves.
Not an AMMAcquisition and inventory records are not an automated market maker, swap desk, or trading venue.
Not a wrapper minterSilver representation must remain clearly labeled and must not be summarized as native/gold vault movement.
Not destination admissionThe receiver owns local accounting, wallet display, admission, refusal, quarantine, and final result.
Not redemption accessLedger, reserve, fee, refund, surplus, or vault labels do not create redemption, sell, unwrap, or exit access.
Not counterparty bank debitObserved payment, external-settlement, provider, relayer, or host-gas receipts do not execute external bank movement.