1
Quote
One request prices the transfer at every venue that serves the corridor. Each answers with a price, its own fees and an ETA, or is listed in
rejected with a reason. Rows are ranked on net output in the asset’s atomic units. See Ranking.2
Build
Building a quote returns the unsigned transactions for the chosen row: an approval where one is needed, a fee step where the venue has no fee parameter of its own, then the bridge call. The transfer record exists before the steps are returned, so it can be tracked even if nothing is ever signed.
3
Sign
Your user’s wallet signs the steps in order. Bridg has no signer and no key. Wallets with EIP-5792 batching sign the fee and bridge steps as one bundle.
4
Submit
Hand back either the signed bytes, which Bridg broadcasts through its own nodes, or the hash of a transaction the wallet already sent. Either way the transaction is checked against the steps that were built. Anything else is refused.
5
Track
Bridg polls the venue until the transfer reaches a terminal state. Read
GET /bridge/transfers/{id} at any time; the statuses are listed in Track a transfer.