Q markBridgeProduct Journey

Native acquisition

Bridge Product Journey

A caller asks for a host-native asset. Bridge classifies the actual payment, quotes the route, sources inventory when policy allows, records the proof, assigns host-vault evidence, and hands off a receiver acknowledgement. The receiving chain still decides local meaning.

Bridge product promise

The product is not an open-ended bridge-across slogan. It is a bounded acquisition and evidence loop.

Ask

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

Classify

Bridge records whether the actual denom is admitted, refused, quarantined, host-native, or representation-only.

Quote

Asset cost, host execution cost, proof and memory cost, Bridge service margin, and risk buffer stay separated.

Source

Inventory can be used only inside policy. Shortfall may defer, refuse, quarantine, or require fresh sourcing.

Handoff

Bridge records receiver acknowledgement. Receiver admission and accounting remain receiver-owned.

Current product proof

Resident testnet evidence now proves the product shape without opening production movement.

Proof classnative liquidity purchase

Caller-neutral purchase readiness with an owner-chain receiver path.

First owner receiverInfra x/bridge

Infra is the first live owner-chain receiver in this proof slice.

Payment denomuinj admitted

The payment receipt observes the denom and amount. It does not execute payment or claim custody.

Readiness resultready=true

Readiness joined intent, payment receipt, inventory, owner pool, and boundary flags.

Receiver ackpacket-backed

A resident USDC proof shows exact receiver contract plus product packet ack evidence; receiver-local accounting remains receiver-owned.

Production movementclosed

No host execution, wrapper mint, sell/redeem/swap, public exit, reserve backing, or destination admission is opened.

Resident receipt trail

These are public chain proof identifiers, not private operator procedure.

Inventoryheight 9515 | tx E3843BB4D4A8D677C7651A3122BC3135E42DE0A1EFAD741273FBFA7314099E27committed
Orderresident-native-liquidity-purchase-infra-20260521T085229Z | height 9527 | tx C53BA249BA3C60585F3ABFB40BDBB7B12627C9F2E9056110B51840118BF5969Eintent
Receiptheight 9688 | tx 45ABE1B0A52D029578708B64E3565A0E02F825286FD4CBC21315E944CCEBA3B0observed
Owner poolheight 9528 | tx 257CC0702FAE7C536DB248D5104A9782B88FF787D11C2125F5DD075C283E97B7assigned
Legacy receiver ackheight 9815 | tx 951822A3F86AA229BCAEF2F2C77316D9F0CE71F6873E30EA941EDC1A4261FD40pending
Packet-backed ackresident-native-liquidity-purchase-infra-usdc-20260522T022152Z | height 13906 | tx DCCFCA62B97613518615726CB1832FA5A0006F4418A52B660B7F7ADCB05DD328admitted evidence

Product surfaces

The product is inspectable through stable receipt, readiness, data, and refusal surfaces.

Failure is part of the product

Bridge should stop cleanly when evidence is not strong enough.

RefusedMissing fields, bad denom, wrong factory, expired quote, disabled signer, or insufficient authority can close the path.
QuarantinedBridge can hold a suspect state label without turning it into destination admission or spend authority.
PendingReceiver acknowledgement can be visible while local receiver admission remains unknown.
RecoveredRecovery is a dated receipt path. It must not rewrite the original terminal fact.

What this does not open

The current product proof is useful because the closed surfaces stay closed.

  • No production bridge-across service. The resident proof shows product-state shape, not public production movement. Do not call this production liquidity.
  • No destination admission claim. Receiver-local admission, accounting, custody, treasury meaning, and protocol credit remain outside Bridge authority.
  • No wrapper mint or sell desk. Bridge does not silently turn gold native posture into silver representation, redemption, swap, public exit, or market-making authority.
  • No private route logic. Public pages may show receipt classes, proof identifiers, and boundary labels, not private operator timing, keys, provider URLs, caps, or exploit-sensitive procedure.