Skip to content

feat(approach): Private Registry - #219

Open
Darkjay123 wants to merge 1 commit into
ethsystems:masterfrom
Darkjay123:approach-private-registry
Open

Darkjay123 wants to merge 1 commit into
ethsystems:masterfrom
Darkjay123:approach-private-registry

Conversation

@Darkjay123

Copy link
Copy Markdown
Contributor

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

What this adds

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

  • Sparse Merkle registry with selective proofs (documented, I2I+I2U) — entries as leaves, proofs for individual lookups, cheap updates, anchored roots.
  • Encrypted registry state with scoped viewing keys (documented, I2I+I2U) — state stored encrypted; role-scoped viewing keys for operators, regulators and entry owners.
  • Cross-border attestation bridge (documented, I2I) — foreign queries answered with signed attestations rather than bulk data exchange.

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. The open questions carry forward the use case's own, including the eWpG interaction and operator trust questions.

Accompanying changes

  • use-cases/private-registry.md: the "Approach TBD" recommended-approaches section now links the card.
  • 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-registry (issue ethsystems#138). Adds the
approach card comparing a sparse Merkle registry with selective proofs,
encrypted registry state with scoped viewing keys and a cross-border
attestation bridge; 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