Skip to main content
POST
Records a mined acceptCuratorRole transaction on this instance. The call verifies the receipt against the lending factory and checks that the factory now names the signing wallet as lender of record. It then writes the market onto this instance with the parties the factory recorded. It returns 201 with the recorded market, the satellite handover state and the asset data approval the receipt carries. Call it after broadcasting the transaction from Accept Lender Role. The returned market.id is this instance’s ID for the market: every /markets/{marketId} endpoint takes it from here on. Confirming the same hash again is safe and converges on the same records. This call records the adoption on the adopting instance only. The deploying instance learns of it when it reads the market with Get Market or Get Operator, which reconcile its record with the factory.

Path Parameters

string
required
Market contract address, 0x followed by 40 hex characters. It must match the market the transaction adopted.

Body Parameters

string
required
Hash of the mined acceptCuratorRole transaction, signed by one of this instance’s verified wallets.
boolean
true when the adoption installed a whitelist as provider register on your attestation. It is written to the audit record of the adoption. Send what the build’s confirmWith.body carries.

Whitelist gates

When a register the adoption installed is a whitelist, the lender of record can maintain it only as one of its managers. accessListSteps offers that step for each whitelist gate, as on Get Identity Gates: the setManager transaction for the list’s owner to sign, confirmed with Confirm Whitelist Manager. A step is withheld with code: ACCESS_LIST_SHARED when the list also gates a product of another lender of record or a vault.

Handover

Adoption hands the price oracle, the interest rate model and the insurance fund to their named owners inside the same transaction. handover.complete then reads true and acceptOwnershipCalldata is empty. Get Handover reads the same state later.

Standing policy terms

When this instance holds an enabled standing policy that matches the market’s deployer or collateral token and binds a terms library template, the confirm publishes the template’s current version as the market’s terms of use. It does so only while the market has no published terms. termsApplied reports the result. A repeated confirm, sent again because the first answer was lost, reports the terms the first confirm published and adds alreadyPublished: true. It does so also after the policy was switched off, removed or bound to another template in the meantime. A failure there does not undo the adoption: it is reported in termsApplyError, and terms can be saved afterwards with Save Terms. When the bound template is archived, standingPolicy.template.archived is true and nothing is published: termsApplyError.code reads TEMPLATE_ARCHIVED. Bind another template to the policy with Update Standing Policy, and publish terms on the adopted market with Save Terms.

Response Fields

object

Error Codes

Confirming can also return any transaction verification error.