create_dispute_resolution_proposal
Generates EIP-712 typed data for a mutual dispute resolution proposal. Both buyer and seller must sign the same buyerPercentBasisPoints value locally with their wallet (EIP-712) before calling resolve_dispute. Returns: typed data structure (domain, types, message).
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. |
buyerPercentBasisPoints | — | yes | Proposed percentage of disputed funds for the buyer, 0–10000 (basis points). The counterparty must sign this same value. |
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. |
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.