KYC Proofs
Attest Proofs
File proof-backed claims and rotate the on-chain root when the bundle is newer
POST
Files claims from a bundle and, unlike Add Claims from Proof, can rotate the identity’s on-chain root to this bundle’s root in the same flow. Use it when re-proving a subject against a new batch, where the root on the registry is the old one.
It also records a ledger row per claim, so List Proofs can later say which proof backs which slot.
Body Parameters
string
required
The subject. Must already be verified on chain and not revoked.
object
required
The bundle’s
manifest.json, parsed.string
The bundle’s
manifest.sig. Required under enforcement.object
A map of field name to base64 STARK bytes.
array
Which leaves to file and where. Each entry names a
fieldName, optionally the claimType slot to use, and optionally expiryDays for that claim alone. Omit it to file every attestable leaf under its canonical slot.A leaf with no canonical meaning has no default slot, so it needs an entry naming one of AML, TAX_RESIDENCY, SANCTIONS_CHECK or PEP_CHECK.string
The hash of the transaction that registered this bundle’s root on the identity. Required when the bundle’s root differs from what the registry holds.
array
Send this to confirm. An array of
{ fieldName, txHash }.Root rotation
The registry holds one root per identity. A bundle proved in a later batch has a different root, and its leaves cannot be checked against the old one. When the bundle’s root differs from the chain’s, the calldata leg returns the root-rotation transaction as the first step and the claim transactions after it. Broadcast the rotation first, then pass its hash back asrootTxHash alongside txResults.
Confirming without it is refused with ROOT_ROTATION_REQUIRED. The rotation receipt is checked to target this wallet and to register this bundle’s root, so a hash from an unrelated transaction fails with TX_ROOT_MISMATCH.
Response Fields
object
success is false with NO_PROOFS_ADDED when the confirm leg files nothing, on a 200. Read added against total.