Skip to content

feat(approach): Private Oracles - #217

Open
Darkjay123 wants to merge 2 commits into
ethsystems:masterfrom
Darkjay123:approach-private-oracles
Open

Darkjay123 wants to merge 2 commits into
ethsystems:masterfrom
Darkjay123:approach-private-oracles

Conversation

@Darkjay123

Copy link
Copy Markdown
Contributor

Fills the "Approach TBD" gap on the Private Oracles use case from issue #138.

What this adds

New approach card Private Oracles (approaches/approach-private-oracles.md) comparing three sub-approaches:

  • Private information retrieval (documented, I2I+I2U) — fetch a record without the server learning which record was read.
  • TEE-served encrypted queries (documented, I2I+I2U) — queries encrypted to an attested enclave key; the operator never sees content, only counters.
  • Batched delivery with anchored provenance (documented, I2I) — consumption hidden inside delivery rounds; provider provenance and consent receipts attested on-chain.

Each sub-approach carries CROPS scores with written justification; the card follows the v2 template (issue #151) with the 10-row comparison matrix, persona perspectives, a conditional recommendation and open questions.

Accompanying changes

  • use-cases/private-oracles.md: the "Approach TBD" recommended-approaches section now links the card (architectural considerations kept).
  • CHANGELOG.md: [Unreleased] entry in the style of the recent approach PRs.

Checks

All six required v2 sections present, title prefix and frontmatter complete, body word count within the documented approach limit. The Vale prose gate runs in CI.

Part of #138.

Fills the Approach TBD gap on private-oracles (issue ethsystems#138). Adds the
approach card comparing private information retrieval, TEE-served
encrypted queries and batched delivery with anchored provenance; links
the use-case card and adds the changelog entry.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant