Skip to main content

Related work

DPO2U sits inside an already active design space. The relevant question is not whether related work exists — it clearly does — but how DPO2U is positioned relative to it.

1. Zero-knowledge compliance systems​

The general idea of using zero-knowledge proofs for compliance and selective disclosure is now well established. DPO2U therefore does not claim novelty for the abstract phrase "ZK compliance."

What matters is the implementation target:

  • compliance statements as typed machine-readable artifacts
  • narrow disclosures instead of raw document exchange
  • replayable verification by software agents

2. Verifiable credentials and selective disclosure​

Credential systems matter because they provide a vocabulary for claims, issuers, holders, and verifiers. Work such as Vega is especially relevant because it shows how low-latency proofs can be generated over existing credentials without revealing full underlying data.

That line of work informs DPO2U's attestation design even when DPO2U is not itself a credential standard.

3. Modern proof-system literature​

The 2025 survey literature on zk-SNARKs and folding-based proof systems is relevant because it changes the engineering envelope:

  • proof generation is becoming faster
  • recursive and compositional designs are becoming more practical
  • application protocols can outsource more complexity to mature proving stacks

DPO2U is a consumer of these advances, not the inventor of the primitive.

4. Agent identity and machine payments​

ERC-8004 and x402 matter because they define adjacent surfaces:

  • ERC-8004 — trustless agent identity, validation, and self-funding patterns
  • x402 — machine-native HTTP payment flows

DPO2U's position is complementary: it specializes these broader currents for compliance workflows.

5. Multi-jurisdiction compliance infrastructure​

DPO2U begins from LGPD, but its architecture assumes that single-jurisdiction schemas are insufficient over time. Work on digital identity, selective disclosure, and regulated crypto-assets suggests a future where attestations must cross legal boundaries without expanding disclosure.

That is why references such as eIDAS 2, AMLA, and MiCAR matter in the documentation context: not because DPO2U already solves every jurisdiction, but because they define the environment in which a protocol like this must evolve.

DPO2U's real contribution claim​

The strongest defensible claim is a compositional one:

DPO2U combines schema-first compliance artifacts, agent-facing execution, and incentive-aware attestation design into a single protocol framing.

That is narrower and more credible than claiming to have originated zero-knowledge compliance as a category.