Acquisition Snapshot
Readable product posture before runtime detail.
BridgeNative Acquisition
Readable product posture before runtime detail.
One request, one bounded product record.
The request names payment denom, amount, requested host asset, lane, and destination boundary.
Bridge separates asset cost, host execution cost, proof and memory cost, service margin, and risk buffer.
The output is labeled as host-native, admitted by policy, representation-style, refused, or quarantined.
Allowed requests can draw from protocol inventory first and record approved fresh sourcing for shortfalls.
The record preserves route, funding evidence, assignment, refusal, quarantine, and export labels.
Bridge does not hide weaker or more expensive products behind one generic route fee.
The requested host asset cost or inventory value used for the request.
Gas, miner fee, rent, deployment, relay submission, or other host-chain cost.
Receipt, Infra export, retention, and later proof categories when the lane depends on durable evidence.
The Bridge service component. It stays separate from host fees and proof costs.
Slippage, reorg/finality, dust, and operational safety categories.
If price, proof, route, finality, fee, or authority posture fails, the request can stop instead of being reinterpreted.