GET /api/v1/anchors//verify
Recomputes the Merkle root from the underlying events and checks that it matches the stored anchor. Also validates the anchor chain by verifyingprevious_anchor_hash references the preceding anchor correctly.
Path Parameters
The anchor identifier (e.g.,
anc_abc123).Response
Response Fields
The anchor identifier.
The 64-character hex Merkle root stored in this anchor record.
true if the Merkle root recomputed from the underlying events matches the stored merkle_root. false if the events have been modified, inserted, or deleted since the anchor was created.true if the previous_anchor_hash correctly equals SHA-256(previous_merkle_root + previous_tx_hash). false if the anchor chain has been tampered with. Always true for the first anchor in a workspace.The Merkle root recomputed from the current event data. If
valid is true, this matches actual.The Merkle root stored in the anchor record at creation time. If
valid is true, this matches expected.The number of events included in this anchor’s Merkle tree.
The blockchain transaction hash. Null if the anchor is not yet confirmed on-chain.
Direct link to the transaction on Basescan. Null if not yet confirmed.
Examples
Interpreting Results
valid | chain_valid | Meaning |
|---|---|---|
true | true | Everything is intact. Merkle root matches events, anchor chain is correct. |
false | true | Events were modified after this anchor was created. The anchor chain is fine, but the underlying data changed. |
true | false | Events are intact, but a preceding anchor was modified or deleted. |
false | false | Both the events and the anchor chain have been tampered with. |