Skip to main content
POST
Reads a manifest, checks its signature and recomputes its Merkle root, then reports every leaf and whether it can be filed as a claim. Nothing is written and no chain read happens. Call it before Add Claims from Proof to build a selection screen. A leaf that comes back with attestable: false will be refused there too, and blockedReason says why in words you can show.

Body Parameters

object
required
The manifest.json from the bundle directory the proof tool wrote, parsed as JSON.
string
required
The contents of manifest.sig, the ed25519 signature over a canonical view of the manifest. Verified against the key from Set Operator Key.

Response Fields

object

Leaves

array

Why a leaf is blocked

Three things block a leaf, and each blocks only that leaf. The rest of the bundle stays usable. The predicate parameters are outside policy. A trust anchor decides which thresholds and which allowlists this network accepts. A leaf proving an age floor nobody approved is reported rather than failing the whole bundle. A canonical field was proved with the wrong circuit. country must be proved with set_membership, nationality likewise, investorType with tier_threshold. A country leaf proved with preimage_knowledge is not filed anywhere, because filing it elsewhere would let it pass as an unrelated attestation. It is commitment-only and proofs are enforced. There is no STARK to check, so under enforcement there is nothing to verify.

Error Codes

Every failure below means the bundle did not hold together. See Add Claims from Proof for the full list, which is the same set.