Q markBridgeNative Vault Lanes

Native Vault Lanes

Bridge separates host-native posture from representation posture. A route can be described, tested, or listed without becoming a production native-vault lane.

What A Vault Means Here

Start with the noun before the lane language.

Controlled holding

A vault is a controlled holding posture for an asset: what is held, where it belongs, and what evidence Bridge has for it.

Movement rule

A vault label should make clear what rule can move the asset and what rule stops it from moving.

Not a yield product

A Bridge vault is not a public yield vault, redemption promise, reserve guarantee, or claim that a user can withdraw on demand.

Plain version: a pool is inventory Bridge can quote from; a lane is the route an asset may travel; a receipt is evidence something happened; a vault is the controlled holding posture around an asset.

Gold And Silver

Product class controls how a reader should interpret the asset posture.

Gold posture

Host-native evidence, finalized host movement or custody proof, native-vault view, and durable receipt labels.

Silver posture

Representation-style claim that must not pretend to be the underlying host asset.

Gold graduation

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

Silver issue

A convenience or small-size path where native-vault posture is not available or not worth opening.

Protocol inventory

A native inventory path that still needs route, receipt, cost, and authority labels.

Host action mandate

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

Lane Map

A lane map is a review map, not an activation list.

Tier 1 thesis lanes

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

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 or protocol proof posture.

Cosmos-native routes

Cosmos assets belong in Cosmos route and endpoint manifests. They are not automatically native-vault lanes.

Endpoint boundary

Endpoint access, host-chain listing, route metadata, or public JSON does not activate a native-vault lane.

Receiving-chain boundary

Bridge can carry evidence. The receiving chain owns what that evidence means inside its own economy.

Current Host Evidence

Live source-pool and owner-vault evidence helps readers see what Bridge is actually holding or handing off without treating every route as open.

Ethereum source pool

ETH, USDC, and PAXG source-pool receipts are visible as inventory posture, not spend authority or destination admission.

QUAD/Core owner vaults

USDC and PAXG owner-vault acknowledgements are recorded for completed slices. Receiver-local meaning stays receiver-owned.

INJ consideration

INJ source consideration can support more than one downstream asset path; it is not tied to a single PAXG story.

BTC pool label

BTC remains a Tier 1 native-vault thesis and pool label. It does not imply public exit, redemption, or reserve backing.

Solana thesis

Solana remains a Tier 1 host-action lane thesis, not current activation language by default.

Raw detail boundary

Raw denom traces and route identifiers belong in JSON and ledger detail. Reader pages should show asset, amount, posture, and boundary.

Public Scope

  • Host-native versus representation posture.
  • Lane candidates and proof categories.
  • Activation language that stays separate from endpoint visibility.

Public Boundary

  • No wrapper equivalence claim.
  • No local bank minting claim.
  • No Bridge sell, redeem, or swap authority.
  • No destination admission or reserve backing by default.