06 · Verifiable Policy Registry
How it works
The registry's architecture and guarantees.
For those who want the technical detail
VPR separates two things: enforcement of the filtering and accountability.
- 01
Enforcement
Done by a standard DNS resolver in the country (the service that turns a site’s name into its address).
- 02
Accountability
Lives on an Ethereum layer-2 network (a lower-cost network built on Ethereum) that stores only cryptographic commitments: digital fingerprints of each rule, not the data itself.
Design decisions, still proposed
ProposedEvery policy version expires unless it is signed again. Proposed pilot maximum: 90 days; contract hard cap: 365 days.
ProposedPolicies are approved by a multi-signature of independent institutions. Proposed pilot model: 2 of 3 signers.
ProposedAggregates below a threshold are not published, nor is their number. Proposed starting value: k = 10. This is small-cell suppression, not differential privacy.
ProposedCommitments are anchored as daily Merkle roots on an Ethereum layer 2. Proposed: OP Mainnet; testnet: OP Sepolia.
Appeals store only a document hash.
Licenses
Code AGPL-3.0, schemas CC0, documentation CC BY 4.0.
Status
Research prototype v0.6.0. Contracts not audited. No public deployment. In preparation as a Digital Public Good (self-assessment).
v0.6.0 (research prototype, pre-release) · white paper v0.7 (draft for review)
What VPR does not claim
- Contracts not audited
- No formal verification (bounded symbolic checks only)
- No deployment on public networks
- No independent review
- No endorsement, funding or pilot commitment from the Ethereum Foundation, UNICEF, the ITU, Giga, ministries or the DPGA
- Not a registered Digital Public Good
- ZK proofs not implemented

If you review projects, do research or work on school connectivity, we want your perspective.
Xcapit team and local participants, Cusco · Photo: Xcapit