Q token mark QUADPublic Accountability

Native asset acquisition / Vaults / Receipts

Bridge

Bridge is the product surface for controlled cross-boundary movement. It shows native acquisition, held-asset pools, reserve labels, host evidence, receipts, refusal, and public movement limits.

Bridge proves what crossed the border.

Bridge Snapshot

Product labels first. Runtime facts support the product; they are not the product.

SurfaceBridge
Product laneNative host-asset acquisition and boundary movement
Current labelBridge-1 is live with real-money posture, resident node evidence, IBC transport proof, product runtime proofs, source-pool ledger rows, quote-first intake shapes, owner-vault allocation proof, host-gas accounting, and Infra export wires; ungated public routes remain closed
First public assetsBTC, ETH, USDC, PAXG, and INJ source-pool evidence
Payment postureExplicit denom per request; no hidden default
Token roleOBOL is passage law: lane security, proof carriage, receipt work, finality risk, relayer work, and border friction
Live subdomainAcquisition, ledger, inventory, vaults, gates, counterparties, host evidence, proof, and status pages are published
Runtime evidenceLive checks show Bridge resident node, Bridge-QUAD Hermes transport, IBC transport proof node, fresh public status JSON, proof packets, source-pool receipts, source-backed BTC/ETH/USDC/PAXG/INJ ledger rows, PAXG/USDC/ATOM into OBOL intake shapes, owner-vault allocation receipts, and Core acknowledgement evidence
Gate caveatRoute proof is not public self-serve access; every lane still needs quote, fee, signer, finality, receiver, and destination evidence before stronger movement claims
Mainnet postureLive Bridge evidence exists for named lanes; open routes remain zero until lane evidence, quote binding, finality, receiver match, and acknowledgement support the route

How To Read This Page

Bridge owns passage evidence. It can record what crossed a boundary, but the receiving surface still decides local meaning.

Purpose

Acquisition intent, source-pool mapping, host evidence, owner vaults, route outputs, receipts, refusal, and quarantine-facing delivery posture.

Posture

Product runtime proofs, resident-node evidence, IBC transport proof, source-pool receipts, per-asset ledger rows, quote-first intake shapes, owner-vault allocation proof, public product pages, proof packets, and Infra export wires are active; ungated public movement remains closed until Bridge and destination evidence support the lane.

Public stats

Use bridge.uquad.org for product journey, ledger, inventory, vaults, gates, host evidence, proof, status, and data files.

Not inherited

Bridge receipt, source inventory, or host assignment does not prove destination admission, host-asset ownership, redemption, or live movement by itself.

Bridge Experience Contract

Bridge should read like border law: who sent what, through which host path, under which fees, with which proof, and what the destination still has to decide.

Bridge should answer the practical route question first: what is being sourced, where is it being held, what proof exists, and what still has to be accepted by the destination.

Open the Bridge route-label map
PathWhat Bridge should showWhat it must not imply
Route screenSource chain, host chain, destination chain, route provider, payment denom, host gas, Bridge fee, proof/memory fee, refund path, and destination handoff state.A route quote is not host execution, destination admission, custody, redemption, or live movement.
Vault journeyPersonal vault, protocol vault, silver wrapper, pooled backing label, native/gold vault posture, and destination admission state as separate fields.A wrapper or pool label is not native host-asset ownership or easy redemption.
Worthiness gateEligibility, pending review, accepted, refused, fallback wrapper, and terminal state where vault access is gated.A refused or fallback path is not hidden access, soft approval, or a promise to upgrade later.
Host finalityPending, confirming, finalized, expired, reorg/refused, recovered, and receipt-bound states for the host chain.Host finality does not force Core admission, Liquid settlement, or destination accounting.
RPC / provider healthProvider name or class where public, freshness, degraded state, backlog, gas posture, and activation blocker where it affects action.Provider health is not route safety, custody, admission, or a guarantee of delivery.
Refund and surplusRefund owed, refund pending, refund sent, surplus held, surplus credited, surplus quarantined, or surplus terminalized.Refund and surplus labels are not yield, reward, or discretionary Bridge profit.
Receipt pathSource observation, finality proof, host command, handoff, destination receipt where applicable, refusal, quarantine, and export label.A receipt proves a bounded passage event, not universal truth or another surface's admission.
Silver / gold outcomeWhether the reader received representation-style exposure, fallback wrapper, native/gold vault posture, or host-native delivery evidence.Silver exposure must not be summarized as gold vault movement.
Destination boundaryThe receiving surface owns admission, balance truth, wallet display, refusal, and local accounting.Bridge cannot force another chain to admit an asset or treat a route output as clean native value.

This is the main-domain reading contract. Current route records belong on Bridge-owned pages such as product, acquisition, ledger, vaults, host evidence, and proof.

Live Bridge Product Pages

The Bridge subdomain now owns the detailed product map. The main site keeps the public explanation and boundary.

Product JourneyBuyer intent, source-pool mapping, owner vaults, terminal receipts, and public movement limits. AcquisitionIntent, quote, route-output class, host assignment, funding evidence, receipt, and refusal posture. Reserve LedgerSource-backed per-asset pool rows plus host-fee, buffer, route-output, receipt, and refusal categories. Inventory TruthProtocol inventory, user-bonded, host-vault, and public accounting labels. Vault LanesNative-vault posture, silver/gold product classes, and admission boundaries. Production GatesVerifier, signer, finality, DA receipt binding, quarantine, fee, and authority gates. CounterpartiesRoute-ticket boundaries, external receiver blockers, and destination-admission limits. Host EvidenceEthereum-mainnet source-pool, owner-vault, host-gas, finality, and assigned-vault evidence with route-specific boundaries. ProofProof, receipt, quarantine, refusal, and public evidence labels. StatusCurrent Bridge status labels, including lane-gated public movement.

What The Product Does

Bridge turns a movement request into a bounded record instead of a vague promise.

1. Accept intent

The caller supplies a payment denom, amount, requested host asset, lane, and destination boundary. Bridge does not invent a default asset or route.

2. Quote the lane

The quote separates asset cost, host execution cost, proof and memory cost, Bridge service margin, and risk buffer.

3. Classify output

The route-output denom is classified before any public meaning is implied: admitted route by policy, quarantine, host-native, or wrapper-style representation.

4. Use inventory or source

Bridge can draw from protocol inventory first and record approved fresh sourcing for shortfalls when that lane is allowed.

5. Assign the host surface

Host-account or native-vault assignment is recorded as evidence. Assignment is not destination admission, sale access, or reserve backing.

6. Publish receipts

Bridge records quote, payment intent, route, funding evidence, receipt state, refusal state, and safe export labels for later review.

Pools And Reserve Ledger

Public labels for what Bridge tracks, including source-backed per-asset pool rows where Bridge can safely publish them.

Bridge tracks inventory, bonded value, host-vault assignment, route output, fees, buffers, receipts, refusal, and quarantine. The ledger can show an asset amount where Bridge has a current published source, but that amount is still not liquidity, redemption, destination admission, or open public movement.

Open ledger categories
Protocol inventory pool

Bridge-owned or Bridge-tracked inventory that can satisfy an approved acquisition lane before fresh sourcing is needed.

User bonded pool

User-supplied or request-linked value held for a bounded acquisition, quote, or route decision.

Assigned host vault

The host-chain account or vault label tied to a specific request or lane. It proves assignment posture, not receiving-chain admission.

Host-fee ledger

Gas, miner fee, rent, relay submission, deployment, and host execution costs stay visible as pass-through categories, not hidden Bridge margin.

Reserve and finality buffer

Buffers account for slippage, reorg/finality risk, dust, and safety posture. A buffer label is not a yield, backing, or redemption promise.

Route-output ledger

Each committed order records what the output claims to be and what policy action applies before any destination can treat it as meaningful.

Receipt and export ledger

Bridge preserves public receipts and Infra export labels so later readers can inspect what happened without seeing private route procedure.

Refusal and quarantine ledger

If price, proof, finality, fee, route, or authority posture fails, the record can refund, refuse, or quarantine rather than reinterpret the request.

Product Classes

Not every Bridge movement is the same product. The class matters.

Bridge separates representation posture, native-vault posture, inventory use, and host action mandates. That keeps product language from pretending every route is the same.

Open product classes
Silver issue

A representation-style claim when native-vault posture is not available or not worth opening for the request.

Silver topup

A small follow-on representation update that stays explicitly below host-native vault posture.

Gold graduation

A movement from representation posture into a native host-vault posture when evidence, size, and policy allow it.

Gold purchase

A native host-asset acquisition path where host-side evidence and finality posture matter more than convenience.

Protocol native inventory

Bridge-managed inventory used to satisfy allowed host-native requests while keeping route, receipt, and cost labels reviewable.

Host action mandate

A bounded request for a host-side action, not a generic trading desk, AMM, wrapper mint, or sell/redeem/swap surface.

Native Vault Lane Map

A lane map is not an activation list. Endpoint access is not native-vault admission.

Bridge can name candidate host lanes without opening them. Native-vault language requires lane-specific proof, custody posture, and finality rules.

Open lane map
Tier 1 thesis lanes

Bitcoin, Ethereum, and Solana are the primary native-vault shapes: hard-asset UTXO, account-style host action, and high-value host execution respectively.

EVM venue lanes

Base, Arbitrum, OP Mainnet, Polygon PoS, Avalanche C-Chain, BNB Smart Chain, and similar venues are candidates, not production-native lanes by default.

Issuer and protocol lanes

USDC, PAXG, USDP, KAG, USDe, ONDO, Pendle, DAI, MKR, LINK, and related assets need issuer/protocol proof posture, not generic bridge language.

Cosmos-native reminder

Cosmos assets belong in Cosmos route and endpoint manifests. They are not automatically native-vault lanes just because Bridge can name them.

Production Gates

Bridge can show evidence before it opens movement. That is the point.

Before a route opens, Bridge needs verifier, signer, finality, receipt-binding, fee, refusal, and authority boundaries for that lane.

Open production gates
Verifier

The host-chain proof source has to be production-ready for the lane being claimed.

Signer

Signing and custody posture must be named and bounded before production movement exists.

Finality

Reorg, timeout, replay, and confirmation rules must be clear enough for the lane.

DA receipt binding

Accepted Infra export or receipt binding must exist where the lane depends on durable proof memory.

Quarantine and refusal

Bad proof, mismatched routes, bad price, dust, fee failure, or unsafe authority must have a normal stop path.

Fee and dust policy

Host-chain costs, proof cost, memory cost, dust limits, and buffers must be visible as categories before quotes are trusted.

Authority boundary

Bridge can prove passage and acquisition posture. It cannot force Core admission, Liquid settlement, Infra truth, or any destination's accounting decision.

Current Public Evidence

Bridge can show product evidence without opening a production route.

Bridge has product journey, source-pool receipts, per-asset pool ledger rows for BTC, ETH, USDC, PAXG, and INJ, quote-first PAXG/USDC/ATOM into OBOL intake shapes, owner-vault allocation proof, Core acknowledgement evidence, split-denom receipts, host-gas accounting, resident runtime evidence, and proof-packet folders. Public movement remains lane-gated unless a route-specific page says otherwise.

Open evidence detail
Product journey

The Bridge subdomain now has a product-first path that separates buyer intent, source-pool mapping, owner vaults, terminal receipts, and lane-gated labels.

Source-pool ledger

Bridge publishes source-backed pool rows for BTC, ETH, USDC, PAXG, and INJ under Bridge-specific labels. Inventory evidence is not free spend, wrapper minting, redemption, liquidity, or destination admission.

Shared source pool

Bridge models a single Bridge-side source pool for an asset and lane, then maps approved requests to stable owner vaults. The pool is not the buyer vault and the buyer vault is not Bridge-owned liquidity.

Provider-scoped asset identity

USDC, PAXG, and INJ keep their source context in Bridge data files, so a ticker is not treated as a vague asset without receipt or query backing.

Core acknowledgement loop

Core can acknowledge Bridge owner-vault allocation evidence without minting local bank funds. Delivery and acknowledgement remain separate from Treasury admission and ordinary spendability.

Split-denom order path

Bridge has product receipts for split input and output denoms, route classification, host-gas reserve, Bridge fee, net owner-vault allocation, and readiness labels without claiming generic public bridge access.

Host-gas accounting

Host-chain gas is now quoted or reserve-labelled separately from the Bridge route fee, so cost accounting does not disappear inside spread language.

Runtime posture

Bridge can package runtime records for movement, Infra delivery, Liquid handoff, receipts, custody, settlement, and refusal reasons.

Live box posture

The Bridge box is running a resident Comet/ABCI node, an IBC transport proof node, Bridge-QUAD Hermes transport, public status data, source-pool evidence, and proof packets.

Reconciliation caveat

Bridge runtime evidence is active, but route opening still depends on current lane evidence: quote, source settlement, host finality, signer posture, receiver acknowledgement, and destination boundary.

Host-contract freeze law

Bridge law pins ABI, source, runtime, creation, artifact hashes, admin posture, event schema, and smoke records before any host contract can be treated as production-active.

No self-serve movement

This page opens no generic sell, redeem, swap, wrap, unwrap, public exit, destination admission, production liquidity, bank debit, or host execution claim beyond route-specific owner-published evidence.

What To Check

Bridge should be judged by ledgers, classes, gates, and receipts, not promises.

Pool label

Whether the record is protocol inventory, user bonded value, host-vault assignment, reserve buffer, receipt, refusal, or quarantine.

Quote shape

Whether asset cost, host execution cost, proof and memory cost, service margin, and risk buffer are separated.

Route-output class

Whether output is host-native, admitted by policy, representation-style, refused, or quarantined.

Lane gates

Whether verifier, signer, finality, receipt binding, fee/dust, and authority boundaries are complete before a lane is called production-active.

OBOL role

Whether passage, proof carriage, receipt work, relayer cost, and border friction are separated from Core admission, Infra memory, and Liquid settlement.

Outside evidence

Whether Ethereum-mainnet evidence is treated as lane-specific host evidence, not internal admission, settlement, redemption, or a generic public bridge-across product.

IBC readiness

Whether record-only readiness stays separate from live packet handshakes, relayer compatibility, and keeper-backed IBC state transitions.

If Bridge Is Unavailable

The main site keeps Bridge's boundary role readable when the Bridge subdomain, host-evidence page, route ledger, or readiness surface is stale or offline.

Still shown

Bridge purpose, product classes, native-vault boundary, pool labels, public scope, and lane-gated posture.

Downgraded

Current route records, host observations, vault evidence, RPC/provider health, proof pages, and receipt lookup.

Not inferred

Bridge outage does not imply destination admission, Core custody change, production value movement, route safety, or host-chain finality.

Next check

Use Status, Verify, and the Bridge subdomain once it is reachable again.

Public scope

  • Native acquisition intent, quote, route, and payment-denom posture.
  • Held-asset pool labels, source-backed per-asset amounts, host-vault assignment, and reserve/fee ledger categories.
  • Receipt, refusal, quarantine, and public export summaries.
  • Source-pool, owner-vault, host-gas, finality, and Core acknowledgement evidence without granting ordinary Core admission.
  • Record-only IBC testing, runtime packaging, and lane-gate posture without opening generic public movement.

Public boundary

  • Core admission decisions.
  • Private movement review.
  • Operator timing.
  • Private selection procedure.
  • Credentials, provider URLs, keys, signatures, or host-wallet material.
  • Production value movement unless an official page says a lane is open and points to evidence.