Phase 2 – Trust, Scale & Ecosystem | 2026
Phase 2 is about making the proofs checkable by anyone and easy to adopt. This is where each item stands today.
Shipped
- Batch anchoring on Horizen. Every 5 minutes, new proofs are grouped into a Merkle tree and the root is anchored through
Anchor.sol. This replaced the earlier plan of one snapshot per day. - Public Explorer. explorer.adpriva.com lets anyone look up a proof, a batch or an anchor without an account.
- Validity scoring. Every view proof gets a validity score and a verdict, published with the proof. See Proofs of Engagement.
- Traffic certificates. Portable Verification Certificates can be downloaded from the console for any date range.
- Consent certificates. Sealed, anchored evidence of consent given on a web form, including Consent Evidence certificates that can be verified offline. See Consent Certificates — Quickstart.
- WordPress plugin. Available on WordPress.org. It connects a site with one click, loads the tag and shows a traffic summary in wp-admin.
Not enabled yet
- Enforcement. Verdicts are recorded in shadow mode and do not block or exclude anything. Turning enforcement on is a separate, gated decision.
Not built
- An SDK for native apps. Websites use the tag.
- Plugins for platforms other than WordPress, such as Shopify.
Dropped
- Batch zero-knowledge verification on zkVerify. Retired on 2026-10-16. New view batches are anchored directly on Horizen, and batches anchored before 2026-09-28 keep their zkVerify attestation. See Legacy: zero-knowledge step.
- On-device proof generation in a consumer app. The consumer app is being retired; proofs are sealed on AdPriva’s server.