docs(proofs): specify hinted TEE registration in the Registrar spec - #2044
Merged
Merged
Conversation
Bring over Leopold's changes from #1956 (merged into the #1953 branch, never landed on master): replace the ZK/Boundless registrar description with the hinted P-384 flow shipped in Cobalt, and add the Hinted TEE Registration page. Past tense where the migration has now shipped, and link the new page from the Cobalt overview. Co-authored-by: Leopold Joy <leo@leopoldjoy.com> Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Collaborator
✅ Heimdall Review Status
|
Per Leopold: the hinted flow is the Registrar's architecture going forward, and only the migration itself is upgrade-specific. Drop the standalone page, replace Upgrade Compatibility with a Hinted Registration Migration section (previous flow, why, what was preserved), and link that anchor from the Cobalt overview. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
leopoldjoy
reviewed
Oct 1, 2026
- Condense Responsibilities into a high-level summary - State that revocation/expiry does not invalidate registered signers - Drop the repeated no-fallback safety bullet Co-authored-by: Leopold Joy <leo@leopoldjoy.com> Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
* docs(proofs): align hinted registration references * docs(proofs): keep hinted API references readable
leopoldjoy
approved these changes
Oct 1, 2026
Collaborator
|
Review Error for leopoldjoy @ 2026-10-01 17:50:21 UTC |
soheimam
approved these changes
Oct 1, 2026
This branch was successfully deployed
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
5 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.
What changed? Why?
Brings over @leopoldjoy's changes from #1956. That PR was stacked on #1953 (Upcoming Features, still a draft), so it merged into the #1953 branch and never reached master. The live Registrar page still describes the old RISC Zero / Boundless attestation-proof flow, which Cobalt replaced.
proofs/registrar.mdx): Leopold's rewrite, which replaces the ZK/Boundless registrar with the hinted P-384 flow. It covers the attestation challenge, registration plan, P-384 hints, certificate cache, final registration, revocation, orphan deregistration, upgrade compatibility, operator inputs, and safety requirements./specifications/base-protocol/proofs/registrar#hinted-registration-migration.upcoming-features.mdxrow change. That page only exists on docs: add Upcoming Features page for planned protocol work #1953.AGENTS.md,llms.txt,llms-full.txt.Notes to reviewers
proofs/proof-contracts.mdxstill documentsNitroEnclaveVerifierwith RISC Zero / SP1 attestation proofs, and its diagram showsRegistry → NitroEnclaveVerifier → ZK verifier. The new registrar spec describesNitroValidator/CertManager/P384Verifierinstead, so that page needs a follow-up.How has it been tested?
node scripts/lint-mdx.json each changed page: 0 errors (1 advisoryhighlightwarning on the Mermaid block, same as docs: specify hinted TEE registration #1956).node scripts/validate-docs-structure.js: passes.Screenshots
Screenshots to follow.