API ReferenceDatasets
Two-layer Merkle proof for a CF in a dataset
There is no `{version}` path segment because a `datasetId` **is** the version identifier — each assembled version has its own id. Address the exact version directly, as with every other `/v1/datasets/{id}/*` route. A 500 here may be an integrity failure — the recomputed root not matching the stored one. The response carries only a generic sentinel; the computed-versus-stored detail is logged server-side deliberately.
GET
/
v1/datasets/{id}/cf/{cfId}/proofPath Parameters
idRequiredstring
The dataset version's 32-byte id.
Pattern:
"^0[xX][0-9a-fA-F]{64}$"cfIdRequiredstring
The contribution fingerprint's 32-byte id. Note the spelling: the nested
dataset routes use {cfId} while the top-level /v1/cfs routes use
{cf_id} for the same value — see CfIdParam.
Pattern:
"^0[xX][0-9a-fA-F]{64}$"The proof bundle.
Last updated