Anchoring

Anchoring

Verbitas anchors cryptographic commitments of signed manifests to public timestamp ledgers. This enables independent verification that a manifest existed at a specific point in time and has not been altered since.

What goes on chain

Only the SHA-256 Merkle root of a batch of manifest digests.

• Domain-separated leaf: SHA256("verbitas-anchor-v1" || manifest_digest)
• No asset bytes, manifest contents, prompts, tenant identifiers, or PII ever go on chain

Anchor stack

Tier	Chain	Default	Confirmation
1	Bitcoin (via OTS)	Always on	1–6 hours
2	Arbitrum One	Public Beta+	Seconds (L2)
3	Customer chain (BYOC)	Recipe opt-in	Chain-dependent

Batching

By default, manifests are batched hourly. Legal-evidence recipes use 5-minute batches. The batch Merkle tree includes all manifests confirmed in the API during the previous interval.

Independent verification

Once anchored, anyone can verify a manifest inclusion proof without trusting Verbitas:

1. Download the .ots proof from GET /v1/anchors/{batch_id}/ots
2. Run ots verify locally against the Bitcoin blockchain

Recipes that enable anchoring

All preset recipes include at minimum OpenTimestamps (Tier 1) anchoring. The enterprise-strict-v1 recipe adds Bitcoin, Arbitrum One, and optional BYOC.

Full anchoring policy →