Q markBridgeNative Acquisition

Native Acquisition

Bridge records a native host-asset request as intent, quote, route-output class, host-account assignment, funding evidence, receipt state, refusal state, and quarantine state. It does not turn a request into live movement by wording alone.

Acquisition Snapshot

Readable product posture before runtime detail.

ProductNative host-asset acquisition
Intake laneQuote-first lanes across the supported assets separate quote shape from payment truth
Payment ruleExplicit source asset, amount, sender, receiver, fee, expiry, and finality per quote
Current targetSource-pool and owner-vault evidence across the supported host chains
Public movementQuote-first and lane-gated by finality and receiver acknowledgement

Acquisition Path

One request, one bounded product record.

1. Intent

The request names payment denom, amount, requested host asset, lane, and destination boundary.

2. Quote

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

3. Class

The output is labeled as host-native, admitted by policy, representation-style, refused, or quarantined.

4. Source

Allowed requests can draw from protocol inventory first and record approved fresh sourcing for shortfalls.

5. Receipt

The record preserves route, funding evidence, assignment, refusal, quarantine, and export labels.

Quote Components

Bridge does not hide weaker or more expensive products behind one generic route fee.

Asset cost

The requested host asset cost or inventory value used for the request.

Host execution

Gas, miner fee, rent, deployment, relay submission, or other host-chain cost.

Proof and memory

Receipt, Infra export, retention, and later proof categories when the lane depends on durable evidence.

Bridge margin

The Bridge service component. It stays separate from host fees and proof costs.

Risk buffer

Slippage, reorg/finality, dust, and operational safety categories.

Refusal path

If price, proof, route, finality, fee, or authority posture fails, the request can stop instead of being reinterpreted.

Current Evidence

  • Source-pool receipts across the supported assets are published as Bridge inventory evidence.
  • USDC and PAXG owner-vault receiver acknowledgements are recorded for completed QUAD/Core paths.
  • Sepolia evidence is retained as historical host-contract smoke only, not the current product target.

Not Opened By This Page

  • Ungated bridge-across service.
  • Sell, redeem, swap, wrap, unwrap, or public exit access.
  • Destination admission or receiving-chain accounting decisions.
  • Host execution or live counterparty bank debit unless an official page says so with evidence.