extend_dispute_timeout
Extends the deadline of an active dispute. Dispute must be in 'Resolving' state. Either party can call this. Returns unsigned transaction data.
Category: Dispute management.
Returns unsigned tx? Likely yes — sign locally and broadcast via send_signed_transaction or a meta-tx relay.
Input schema
| Field | Type | Required | Description |
|---|---|---|---|
exchangeId | string | yes | Numeric ID of the exchange/dispute to act on. Obtain from get_exchanges or the response of commit_to_offer. |
newDisputeTimeout | — | yes | New absolute Unix timestamp in SECONDS (not ms) for the dispute deadline. Must be later than current timeout. |
configId | string | yes | Boson/Fermion Protocol deployment identifier. Format: '<env>-<chainId>-<index>' e.g. 'production-137-0' (Polygon mainnet), 'testing-80002-0' (Amoy testnet). Call get_config_ids to list all valid values for this server. |
signerAddress | string | yes | Ethereum address that will sign and send this transaction. Must match the wallet that will sign the returned transaction locally. |
executionMode | direct | metaTx | no | 'direct' = standard on-chain tx (sign locally with your wallet → send_signed_transaction). 'metaTx' = gasless relay via Biconomy (send_meta_transaction). Defaults to 'direct'. |
Related
- Reference → MCP tools — full catalogue.
- Build for AI agents → The 3-step signing pattern — what to do with returned unsigned transactions.
- Concepts → Signing & meta-transactions — canonical signing reference.