Repository navigation
Conversation
Two pointer entries, left at 0000 for numbering on merge. anon-rpc specifies anonymized RPC through a hash-pinned client running in a sandbox with an explicit capability API; KPS is the key-pinned transport it reaches the network over, which stands on its own as an Access Layer primitive rather than as an appendix to anon-rpc. Both texts are maintained in their own repositories under the ethereum org, so each entry is a notice naming where the text lives plus enough context to read the registry without leaving it. Both carry index_reason: moved, the only one of the two permitted values that passes CI here — dependency is unavailable because build_registry.py counts depends_on from hosted specs only. The intake issue puts the choice to the maintainers.
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
2 participants
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.
Follows #36.
Two new folders, both
role: indexed, both left at0000for a maintainer to number on merge.specs/0000-anon-rpc/ANON-RPCinterfacespecs/0000-kps/KPSprotocolanon-rpc specifies how a wallet or application makes anonymized RPC requests without trusting the endpoint serving them: a pluggable anon-client, pinned by the hash of its bundle rather than by where it was downloaded from, runs sandboxed away from the DOM, storage, cookies and signing keys, and reaches the network only through a small explicit capability API. The host gets back an ordinary
fetch. Currently at version 0.3.1, draft.KPS (Key Pinned Streams) identifies a peer by the hash of its self-signed certificate rather than by a CA-signed domain, and carries multiplexed reliable byte streams and datagrams over WebRTC or QUIC. It is entered on its own terms rather than as an appendix to anon-rpc — taking the certificate authority and the DNS root out of the path by which a client reaches anything is an Access Layer primitive in itself — and anon-rpc is simply the first spec here to sit on it. Currently at draft version 0.2.1.
Each entry is a pointer in the shape 5/ZK-PROOF-OF-PERSONHOOD uses: the notice blockquote naming where the text lives, then enough context that a reader of the registry knows what the spec is without leaving. Neither carries a CC0 waiver, matching that stub and governance.md — the text is not here to waive.
Notes for review
index_reasonis the open question, and it is the one thing here worth arguing about. Both entries carrymoved, which passes CI (movedonly requiresupstreamto be set) but stretches the sentence infront-matter.mdthat reads it as "its text was hosted here and now lives in another standards body". Neither text was ever hosted here.dependencyis not available as an alternative:build_registry.pybuildsdepended_onfromhostedspecs only, so anindexedanon-rpc naming KPS independs_onfails that check. Intake: anon-rpc (interface), pointing at ethereum/anon-rpc #36 lays out the three ways forward, including hosting the text here instead. Happy to rewrite for whichever you pick.specs/0000-anon-rpc/carriesdepends_on: [0], meaningspecs/0000-kps/in this same pull request, per step 4 of intake.md. Both need their0s replaced on merge:0000-kpstakes one number,0000-anon-rpctakes the other and points itsdepends_onat the KPS number.python3 scripts/build_registry.py --checkpasses unchanged. Both specs sit at0000, soregistry.yamland the README table are untouched by this pull request and will need regenerating once the numbers are assigned.🤖 Generated with Claude Code