Skip to main content
POST
Verifies a configuration transaction you broadcast from Configure Market or Get Configuration Status. It records the transaction in the market’s ledger and returns the market’s readiness, read fresh from the chain. Called without txHash, it only re-reads readiness. Name the action the transaction performed. The transaction must then call one of that action’s functions and target its contract. Where the action is about the adapter, the router or the auction venue, it must also authorize that address. Without an action, any successful transaction to one of the market’s contracts is recorded as a configuration change, whatever it did. Nothing on the chain changes here. A transaction that failed verification is not recorded, and readiness reflects only what the chain holds.

Path Parameters

string
required
Market ID.

Body Parameters

string
Hash of the mined configuration transaction, 0x followed by 64 hex characters. Omit to re-read readiness without recording anything.
string
The configuration action the transaction performed, 1 to 60 characters. One of setInsuranceFund, grantLiquidatorRole, authorizeOnRouter, upgradeMarket, upgradeRouter, authorizeAdapterOnToken, authorizeRouterOnToken, grantAgentRoleToAdapter, authorizeRelayerOnOracle, verifyAdapterAsHolder, verifyRouterAsHolder, authorizeVenueOnToken, verifyVenueAsHolder.

What Each Action Accepts

The market’s contracts are the market, its oracle, insurance fund, adapter and liquidation router, and the collateral token. The market’s recorded identity register and the collateral token’s identity registry count too. A transaction sent anywhere else is refused with TX_WRONG_TARGET.

Response Fields

object

Error Codes