Q markBridgeBoundary And Native Vault Surface

Readiness posture

Readiness

Bridge is live as a chain and conservative as a passage product. Public movement stays lane-gated until route, proof, receipt, native-vault posture, finality, fee, and receiver-ack evidence open a specific lane.

Readiness labels

Bridge is public-described here; public movement is not open unless this page and the public JSON say so.

Current labelBridge live-chain evidence
Public routesLane-gated
Source pools14 protocol/source-pool asset rows published where source-backed
Intake lanesPAXG, USDC, ATOM, STRD, and NTRN source lanes are quote-first; payment gated by lane readiness
Native vaultBoundary posture documented
Pricing modelSeparated components documented
DA receipt gateAccepted Infra DA receipt required
Lane gateVerifier, signer, finality, DA, quarantine, fee, and authority gates required
Host feesPass-through execution cost, not Bridge margin
Counterparty routeBoundary ticket gated
Proof soakHistorical proof soak passed
Resident nodeResident Comet/ABCI node active
Infra wiresThree wires acknowledged
BoundaryNon-inheritance rules published
ChainLive Bridge chain

Allowed public claims

  • Bridge is controlled passage, not blind bridging.
  • Bridge is the passage, native-vault, and boundary-movement workstream.
  • Bridge is live as its own chain.
  • Delivery is not admission.
  • Receipts prove boundary events, not universal meaning.
  • ETH, USDC, PAXG, and INJ source-pool labels can be published without opening every route.
  • USDC and PAXG receiver acknowledgements prove Bridge handoff only.
  • Native purchase pricing separates asset cost, host execution, proof/memory, Bridge service margin, and risk buffer.
  • Host-chain gas is pass-through execution cost, not Bridge margin.
  • Routes remain lane-gated unless the public surface says otherwise.
  • Boundary labels do not create destination admission, route-owner authority, or Core truth.

Yellow flags

  • Claims of live public value movement without a lane-specific route page and receipt state.
  • Claims that a receipt proves destination-chain value admission.
  • Claims that endpoint availability is native-vault activation.
  • Claims that transport timeout proof is product-runtime IBC.
  • Claims that product surface, query, or tx rehearsals are keeper execution or value movement.
  • Claims that proof-soak records are the same thing as resident Comet block history.
  • Claims that Bridge exposes sell, redeem, swap, wrap, unwrap, public exit, or Reserve backing.
  • Flat-fee claims that hide host-chain execution costs, proof costs, or risk buffers.
  • Requests for payment, seed phrases, private keys, signatures, or provider credentials.
  • Reward, allocation, or airdrop framing around route rehearsal.