Report a deposit transaction
report_depositSubmits the source-chain deposit transaction hash for an existing swap so the router detects it immediately instead of waiting for the next scan; it never moves funds.
Instructions
Tell the router the hash of the deposit transaction the user just sent, so the swap is detected immediately instead of on the next scan. Optional: swaps are detected without it, and it never moves funds. swap_id is the id create_swap returned for this swap. tx_hash is the hash of the transaction that sent funds to that swap's deposit_address on the source chain (0x-prefixed on EVM chains); never pass a payout hash or another swap's id. An unknown swap_id returns an error. Use it once, right after the user shares their tx hash, then follow up with get_swap_status. Calling it again with the same hash is harmless.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"swap_id": "<swap_id>",
"tx_hash": "<tx_hash>"
},
"name": "report_deposit"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| swap_id | Yes | swap_id returned by create_swap. | |
| tx_hash | Yes | Hash of the user's deposit transaction on the source chain (0x... on EVM chains). Letters and digits only, up to 128 characters. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | True when the router accepted the hash. | |
| next_step | No | What to do next. |