Asset Data
Get Asset Data
Read the asset data attestation and acknowledgement standing on a market
GET
Returns a market’s asset data record: the hash of the bundle the issuer side attested and the hash the lender of record acknowledged. It also says who may write each one next, and whether this instance can. A lender of record adopting a market underwrites an asset it did not issue, described by data no contract can read. The factory makes that description attributable and tamper-evident. It does not verify it.
The record lives on the lending factory as two hashes per market. The attested hash is written only by the attestor’s own transaction and the acknowledged hash only by the lender of record’s or its admin’s own transaction. The bundle itself never goes on chain. Read its exact bytes with Get Asset Data Bundle.
This endpoint takes the market’s contract address, not its market ID.
Who can read it
The market must be registered on the v2 lending factory this instance deploys to, or the call is refused withMARKET_NOT_V2. Access then follows the lender-of-record queue, and origin in the response says which rule admitted the caller.
Every other caller is refused with
NOT_NOMINATED. On an open market the refusal names what is missing instead: WALLET_NOT_CONFIGURED or CURATOR_NOT_APPROVED. The write routes check their own authority on top of this one.
Status
status is null when the factory record could not be read. factorySupport then says why: false for a factory implementation that predates asset data attestation, null for a read that failed.
DIVERGED is the signal a lender of record watches. The description moved after approval, and a re-attestation never removes the earlier acknowledgement. Neither the market contracts nor this API act on a divergence. Whether the new version still supports the credit already extended is the lender of record’s decision, and Acknowledge Asset Data records a new approval.
diverged is the factory’s own assetDataDiverged answer, which compares the two hashes. It also reads true on ATTESTED, where nothing was acknowledged. Branch on status.
Who writes next
The attestor follows who answers for the data at that point in the market’s life. While the market seeks a lender of record it is the wallet that deployed it (attestorRole: DEPLOYER). Once a lender of record adopts it, it is the issuer wallet that lender named in its adoption terms (ISSUER). A market whose deployer the factory never recorded has no attestor, and nobody can attest on it.
The acknowledgers are the wallet that took the lender-of-record role and the admin it named. Before adoption there are none. A lender of record can also acknowledge inside the adoption itself, by naming the reviewed hash in its adoption terms on Accept Lender Role.
Path Parameters
string
required
The market contract address, as 40 hex characters with a
0x prefix.Response Fields
object
profile is built from this instance’s own import of the collateral token. On the issuer instance whose profile was attested, changedSinceAttestation: true means the profile was edited since and a re-attestation is due. On any other instance that imported the same token, it compares a profile the issuer never attested.
Error Codes
The asset data routes report a validation failure with the first failing rule asmessage and no details list.
A
403 or 412 is a statement about this instance’s access to this market. A 503 says a read failed, and nothing about the market or the caller.