Skip to main content
POST
Returns unsigned calldata for the wiring and authorization steps a market still needs, with the authority that must sign each one. Nothing is signed or sent by Trusset: the party named on each step signs and broadcasts it, then records it with Confirm Configuration. Omit action to receive every outstanding step at once, exactly as Get Configuration Status offers them. Name an action to receive that one step. A step that is already complete on-chain comes back with nothing to sign rather than an error. The steps have different signers. The collateral token steps are signed by the token’s own authorities: its agent administrator, its compliance administrator, or an agent of its identity registry. None of those is a role the market assigns, so they never wait for a lender of record. Every other step names the market admin, the router admin or the oracle owner, and is refused with MARKET_PENDING_CURATOR until a lender of record has taken the market.

Path Parameters

string
required
The market’s record ID, as id on List Markets, not its contract address. See Market IDs.

Body Parameters

string
The step to build. Omit it for every outstanding step. See the table below for the supported values.
string
verifyAdapterAsHolder, verifyRouterAsHolder and verifyVenueAsHolder only. The ONCHAINID an ERC-3643 identity registry should register the subject under. It must be a deployed contract carrying a valid claim for every topic the registry requires, or the step is refused.
integer
The same three actions only. Country code for the ERC-3643 registration, an integer from 0 to 65535. Defaults to the country a wallet of your instance is registered under on that registry, or 0 when none is.
string
The same three actions only. The wallet that will sign. If it is an agent of the token’s identity registry and holds a claim key of its trusted issuer for every required topic, the answer is a holderPlan. See below.
object
The same three actions only. The ONCHAINID deployed in the DEPLOY_IDENTITY phase, keyed by the subject’s address: { "<subject>": "<contractAddress from the deployment receipt>" }. At most 4 entries.
array
The same three actions only. The signatures of a SIGN_CLAIMS phase, each { walletAddress, signature, claimType, issuedAt }, where walletAddress is the subject and signature signs what the message’s scheme names: the EIP-191 personal message over messageHash, or the EIP-712 typedData on the newest T-REX registries. issuedAt echoes the message’s own value; the claim is rebuilt from it, so a signature without it stays pending and the phase answers SIGN_CLAIMS again. At most 10 entries.
The five holder fields above only shape the three holder actions, but their format is checked on every call, whatever the action. A malformed value is refused with its INVALID_* code below, never ignored.

Actions

upgradeMarket and upgradeRouter build the same transactions as Upgrade Market, which also covers the interest rate model and the insurance fund. authorizeOnRouter answers routerAdmin: the lender-of-record wallet that holds DEFAULT_ADMIN_ROLE on the liquidation router and has to sign it, or null when none of those wallets holds it. Another wallet’s signature reverts, so send the calldata to that wallet. Get Configuration Status names it too while the market is not authorized.

Registering a holder from your own wallet

For a token your instance issued, a wallet of your instance is usually an agent of its identity registry and a claim key of its trusted issuer. In that case the three registry actions answer with holderPlan instead of one call. The subject gets its own ONCHAINID with the registry’s required claims, signed by that wallet:
  1. DEPLOY_IDENTITY: one contract-creation transaction deploys the subject’s ONCHAINID, managed by that wallet. Send it, then call again with identities set to the deployed address.
  2. SIGN_CLAIMS: messages to sign, one per required claim. Each names its scheme: eip191 signs the personal message over messageHash; eip712 (the newest T-REX registries) signs the message’s typedData and carries an issuedAt. Call again with claimSignatures, each entry keeping its message’s issuedAt.
  3. REGISTER: steps adding each claim and calling registerIdentity, sent in order. Confirm the last one with Confirm Configuration.
Each answer names the next phase, so a client repeats the same call with what it has collected. Trusset builds the transactions and never signs one. Where no wallet of your instance can write to the registry, the answer stays plain. The step is blocked with ONCHAINID_REQUIRED and names the address to send to the token issuer’s KYC operator. Its registryAgent names the wallet of your instance that is an agent of the registry, if one is: only then can an ONCHAINID the KYC operator hands you be registered from your instance with identityAddress. Without one, the registry’s own agent registers it, and an identityAddress from your instance is refused with IDENTITY_REGISTRY_WRITE_REJECTED. On a token that keeps its own KYC whitelist (getKYCData and modifyKYCData, as DigiShares v1.3 does), verifyAdapterAsHolder, verifyRouterAsHolder and verifyVenueAsHolder return a modifyKYCData call with tokenWhitelist: true when a wallet of your instance holds the token’s WHITELIST_ROLE. It keeps the restriction values that already admit the subject. Without such a wallet the action answers TOKEN_REFUSES_HOLDER and names the role. See KYC whitelist tokens.
verifyAdapterAsHolder checks the router as well. Once the adapter is registered it returns the router’s registration, keyed verifyRouterAsHolder. On a token that gates holders through a contract allow-list, verifyAdapterAsHolder and verifyRouterAsHolder return the allow-list call instead of a registration. Confirm a transaction under the action that matches the function it calls, because Confirm Configuration checks the function and the subject.

Response Fields

object

Error Codes