Repository navigation
Conversation
This was referenced Sep 14, 2026
phipsae
force-pushed
the
ci/registry-generator
branch
from
September 14, 2026 23:02
c232a3a to
8484514
Compare
This spec was written in this repository on 18 March 2026, imported into zkID on 14 May, and reduced here to a four-line pointer on 1 July in #24. The repo ended up pointing at its own spec. Brings the text back and sets role to hosted. It takes zkID's current version, not the copy this repo had in March, because the spec has grown since, a split CertChain and DeviceSig circuit design, a verifier API with error codes, and nullifier persistence. The body is byte-identical to zkID's main branch apart from the governance line, which now names process/ instead of a URL pointing back here. Editors and contributors are unchanged. The Access Layer spec map drops the proof-of-personhood row, since the spec no longer lives elsewhere, and the two remaining rows move from privacy-ethereum/zkID to ethereum/zkID, which had only been resolving by redirect. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The imported text still said "this spec's canonical home is privacy-ethereum/zkID", which contradicts the front matter in this same commit saying role: hosted and upstream: null. A reader would have got opposite answers from the metadata and the prose. The passage now names ethereum/access-layer-specs, and describes zkmopro/zkID as a fork of the ethereum/zkID implementation repo rather than "a fork of this repository", which stopped making sense once the spec moved here. Two OpenAC paper links also pointed at privacy-ethereum/zkID, which only resolved through a redirect after zkID moved to the ethereum org. The body now differs from zkID's main branch in four places rather than one, all of them recorded above. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
phipsae
force-pushed
the
specs/host-proof-of-personhood
branch
from
September 14, 2026 23:03
3d53e8d to
b0dfb0f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This needs the spec's editors to agree before it merges. Based on #32.
This one is a question about where the spec should live, not a cleanup.
What happened to spec 5
specs/folder, commit message says "import ... human verification"So the text started in this repository, moved to zkID, and this repository was left pointing at its own spec. That is the split #29 exists to fix. It also means hosting it here is restoring the original arrangement rather than taking anyone's work, and the editor and contributors are unchanged either way.
Worth noting that zkID's copy still says it is governed by 1/COSS in this repo, so zkID already treats this repository as the process home.
What this pull request does
Brings the text back and sets
role: hosted.It takes zkID's current version, not the March copy from here. The spec has grown from 434 to 721 lines since, gaining a split CertChain and DeviceSig circuit design, a verifier API with error codes and status queries, and nullifier persistence. Taking the old local copy would have thrown six months of work away.
The body differs from zkID's main branch in exactly four places, and nothing else. Front matter authorship is unchanged.
process/instead of a URL pointing back hereethereum/access-layer-specsprivacy-ethereum/zkID, contradictingrole: hostedin the same filezkmopro/zkIDdescribed as a fork ofethereum/zkIDprivacy-ethereum/zkIDtoethereum/zkIDAn earlier version of this description claimed the body was byte-identical apart from the governance line. That was wrong, and review caught it. The canonical-home sentence would have shipped saying the spec belongs to zkID while the metadata said it belongs here.
Status moves from
ideatodraft, since a 721-line spec with a full circuit design is past an idea.The spec map also drops the proof-of-personhood row, because the spec no longer lives elsewhere, and its two remaining rows move from
privacy-ethereum/zkIDtoethereum/zkID, which had only been resolving through a redirect.The ask
That zkID keeps the implementation and links here for the spec, rather than holding both. If you would rather keep the canonical text in zkID, say so and I will close this, and #31 already marks spec 5 as
indexedwith the history recorded, which is at least honest about where the text is.The same question applies to OpenAC and ZK Age Verification in zkID, but one at a time.
🤖 Generated with Claude Code