BOB Gateway Swidge Overview
Discover exact-input routes, request quotes and execute through BOB Gateway with compatible WDK accounts.
Community modules are developed and maintained independently by third-party contributors.
Tether and the WDK Team do not endorse or assume responsibility for their code, security, or maintenance. Use your own judgment and proceed at your own risk.
BOB Gateway connects WDK accounts to a routing service for Bitcoin, EVM and TRON asset routes. You can discover chains and tokens, preview an exact-input quote, submit the source transaction and track the resulting order.
These draft pages target @gobob/wdk-protocol-swidge-gateway@0.5.0, which is pending publication. See release availability before using the examples.
Choose a starting point
| Goal | Start here |
|---|---|
| Discover tokens and preview a route without a signing account | Usage |
| Send from an EVM or TRON account | Execute a Swidge |
| Send or receive native BTC | Bitcoin Routes |
| Track payouts, refunds or uncertain submissions | Track Settlement |
| Set providers, request timeouts and fee controls | Configuration |
How a route runs
- Discover the gateway's chain and token identifiers, then request a quote for an input amount and destination.
- Show the input, destination token, recipient, output estimate and fees to the user.
- Complete any token approval required by the source account.
- Call
swidge(). It requests a fresh quote, checks the configured bounds and creates an order before submitting the source transaction. - Retain the order ID and transaction hashes, then query settlement separately.
The earlier quote is a preview, not a route reserved for execution. Set minAmountOut and the applicable fee limits on the execution request to constrain the fresh quote. See execution boundaries for what those checks establish.
Capabilities and limits
- Only exact-input requests are supported. Use
fromTokenAmount;toTokenAmountis rejected. - Discovery reports gateway routes, not guaranteed execution support for every returned chain. Source execution uses Bitcoin, EVM or TRON account methods.
- An accountless instance can discover routes, quote with an explicit recipient and retrieve status. Executing, checking allowances and simulating require the relevant account methods.
getRequiredApproval()may create an unfunded order and returns an unbounded allowance when approval is needed. The application submits and confirms approval transactions.simulateSwidge()creates an unfunded order; on Bitcoin it also signs a transaction without returning its signed bytes. It does not broadcast.- A source transaction hash does not establish destination delivery. Reconcile an uncertain submission before sending again.
- The package's source-transaction checks bound the source token, amount and certain native charges. Provider routing and destination execution still depend on BOB Gateway.
Use runtime discovery instead of maintaining a fixed network or token inventory. A token's presence does not establish liquidity or an executable route for a particular amount.
Next Steps
Usage
Discover routes and request a first quote.
Execute a Swidge
Handle approvals and submit through an EVM or TRON account.
API Reference
Check methods, return values and errors.