Asset Data
Acknowledge Asset Data
Build the transaction that records the lender of record approval of an asset data version
POST
Returns the unsigned
acknowledgeAssetData transaction that records the lender of record’s approval of the asset data version it reviewed. The lender of record, or the admin it named, signs it with its own wallet and confirms it with Confirm Asset Data Acknowledgement.
Name the hash that was actually read, from Get Asset Data Bundle. The build refuses a hash that no longer stands with ASSET_DATA_STALE, rather than approving whatever stands now. The factory applies the same rule when the transaction mines: if the issuer re-attests in between, the acknowledgement reverts with AssetDataMismatch. Read the new bundle and acknowledge again.
An acknowledgement records a review, and the chain stores only the hash. The market contracts never read it, and no loan, liquidity or liquidation operation depends on it.
Who can acknowledge
The caller must pass the market access check described on Get Asset Data. One of this instance’s verified wallets must also be the wallet that took the lender-of-record role, or the admin it named. Any other instance is refused withNOT_ACKNOWLEDGER, and details.acknowledgers names the wallets that can sign.
Before a lender of record adopts the market there is nobody to acknowledge, and the call is refused with NOT_ADOPTED. The adoption itself can carry the first acknowledgement: name the reviewed hash as assetDataHash in the adoption terms on Accept Lender Role.
Path Parameters
string
required
The market contract address, as 40 hex characters with a
0x prefix.Body Parameters
string
required
The hash of the version reviewed, as
0x and 64 hex characters. The zero hash is refused with INVALID_CONTENT_HASH, because it names no version.Response Fields
object
Error Codes
The asset data routes report a validation failure with the first failing rule asmessage and no details list. Every access code from Get Asset Data applies here too.
