Conversation
Lists planned protocol features with ballpark quarter targets and spec links, independent of any named upgrade, per Henri's proposal to defer named upgrade pages until an upgrade is scheduled and locked in. 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
|
Collaborator
|
Review Error for akkolins-cmyk @ 2026-09-13 11:00:47 UTC |
Collaborator
|
Review Error for akkolins-cmyk @ 2026-09-13 11:01:16 UTC |
* docs: specify hinted TEE registration Co-authored-by: OpenCode <opencode-noreply@coinbase.com> * docs: clarify permissioned TEE registration Co-authored-by: OpenCode <opencode-noreply@coinbase.com> * docs: simplify TEE registration summary Co-authored-by: OpenCode <opencode-noreply@coinbase.com> * docs: remove obsolete rollback references Co-authored-by: OpenCode <opencode-noreply@coinbase.com> * docs: add hinted TEE registration feature spec Co-authored-by: OpenCode <opencode-noreply@coinbase.com> --------- Co-authored-by: OpenCode <opencode-noreply@coinbase.com>
Co-authored-by: Toshi <toshi-noreply@coinbase.com>
roethke
added a commit
that referenced
this pull request
Sep 25, 2026
…2014) * docs: correct Cobalt TEE feature summary to registration migration The Cobalt overview described the TEE feature as migrating Base infrastructure to run inside a TEE. The actual work, specified in #1953, replaces the RISC Zero and Boundless proving flow for registering new TEE signers with onchain AWS Nitro attestation verification using checked P-384 hints. Retitles the accordion to "TEE Registration Migration", rewrites the summary to match, links the Registrar specification, and updates the page description plus its llms.txt / llms-full.txt index lines. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com> * docs: apply review feedback to Cobalt TEE summary Per review: emphasize that verification is now trustless and fully onchain, clarify that the removed proving dependency was offchain, and drop the certificate-caching transaction counts as too nuanced for a high-level summary. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com> * docs: reword TEE summary to attribute verification to onchain contracts The registrar is the offchain component; verification happens in the onchain contracts. Recast the clause in the passive to avoid implying the registrar performs the verification. --------- Co-authored-by: Claude <noreply@anthropic.com>
roethke
added a commit
that referenced
this pull request
Oct 1, 2026
…2044) * docs(proofs): specify hinted TEE registration in the Registrar spec 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> * docs(proofs): fold Hinted TEE Registration into the Registrar page 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> * docs(proofs): apply Leopold's Registrar review suggestions - 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 (#2045) * docs(proofs): align hinted registration references * docs(proofs): keep hinted API references readable --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Leopold Joy <leo@leopoldjoy.com> Co-authored-by: Youssef <youcefea99@gmail.com>
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
4 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?
Adds
upgrades/upcoming-features.mdx, a feature-first list (200ms blocks, B20 improvements, validity transactions, dynamic upgrades, TEE migration, EIP-8130) with ballpark quarter targets and spec links, decoupled from any named upgrade, per Henri's proposal to only publish a named upgrade page once that upgrade is scheduled and locked in.Notes to reviewers
First draft to visualize the concept and iterate; open decisions are whether to pull the still-"Planning" Cobalt/Denim entries off the timeline, whether to relocate their spec pages out of the named groups, and the exact quarter targets (EIP-8130 is currently TBD since it's parked for a later upgrade).
How has it been tested?
node scripts/validate-docs-structure.jspasses and the AGENTS.md / llms.txt indexes were regenerated.Screenshots
Pending — I can run
/screenshotto capture the new page and the updated Upgrades landing once you want them in the body; the Mintlify PR preview also renders both.