Q markBridgeNative Asset And Vault Surface

Bridge Native Asset Surface

Bridge is the stack's controlled contact surface with outside ecosystems: native asset acquisition, held-asset pool labels, reserve and host-fee ledgers, route intent, native-vault evidence, finality labels, delivery results, and receipts. It carries facts across borders; it does not decide what receiving chains mean by them.

Bridge is passage, not admission

Delivery is not admission. Bridge can show what was requested, what pool or vault label applies, what was refused, what is pending, and what receipt exists. Native host exposure, silver fallback, and counterparty routes stay bounded by Bridge law and the receiving chain's own rules.

Start Product Journey Observe Bridge Status Boundary Rules Proof Surfaces Raw Public JSON
Current label
Bridge native acquisition product evidence
Feed state
loading...
Last update
loading...

No seed phrase. No payment. No testnet reward, allocation, ownership, governance right, leverage, or future entitlement.

Product journey Native acquisition Pools and ledger Inventory truth Vault lanes Host evidence Production gates

Bridge product journey

Bridge now has a public product path: classify payment, quote the route, source inventory when policy allows, assign host-vault evidence, and hand off a receiver acknowledgement.

Ask

Caller, payment denom, amount, host asset, receiver, and boundary are explicit.

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 may be used only inside policy; shortfall can defer, refuse, or quarantine.

Handoff

Receiver acknowledgement is visible; receiver-local admission remains receiver-owned.

Open product journey Native acquisition Inventory truth

Product snapshot

Bridge-specific route, pool, vault, receipt, and readiness labels belong here, not scattered across the main site.

Product laneNative asset acquisition
Public movementClosed
Held assetsPool labels only
Reserve ledgerCategory labels only
ETH intakechecking
Native vaultchecking
Pricingchecking
Activation gatechecking
Proofchecking
Receiptschecking
Quarantinechecking
Open routeschecking

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. Product journeyNative liquidity purchase proof, caller-neutral receiver classes, receipt trail, and closed production movement. 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. 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 evidenceTestnet funding law, host-contract freeze law, fresh RPC observations, and 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-safe 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.

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.

Acquire

Bridge can record native acquisition intent, quote, route-output class, host assignment, and receipt posture.

Hold

Bridge names pool, vault, fee, buffer, receipt, refusal, and quarantine categories without making live balance claims.

Prove

Bridge shows passage, feeder evidence, proof labels, and receipt state without forcing destination admission.

Stop

When proof, fee, finality, route, or authority posture is not good enough, refusal and quarantine are normal outcomes.

Guard

Counterparty manifests keep QUAD, Infra, and Liquid receiver meaning separate from Bridge transit.

Freeze

Host evidence pages show what is pinned, observed, and still blocked before production activation.

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.