docs: update leftover "current Shasta" references to Unzen - #24
Open
ggonzalez94 wants to merge 1 commit into
Open
docs: update leftover "current Shasta" references to Unzen#24ggonzalez94 wants to merge 1 commit into
ggonzalez94 wants to merge 1 commit into
Conversation
Follow-up to #23, which reframed the docs around Unzen as the current fork and Shasta as its underlying protocol architecture. A handful of places still called the live mainnet state "the current Shasta rollout / deployment / configuration". Update those to Unzen so the docs match the mainnet state after Aug 3, 2026. - based-rollups.mdx: "current Shasta rollout" -> "current Unzen rollout" (x2) - proving-system.mdx: "current Shasta deployment" -> "current Unzen deployment" (and fix the "In the X is a Y" phrasing), drop the fork name from "The deployed verifier set", "current live Shasta configuration" -> "current live Unzen configuration" - economics.mdx: "live Shasta configuration currently runs" -> "live Unzen configuration currently runs" - faq.mdx: same wording fix under Liveness bond Architectural mentions of Shasta (proposal-based derivation, Shasta inbox, Shasta proving model) are left as-is per the framing in #23. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0165y9iQpUDrtyKmTrtXRshV
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.
Why
Follow-up to #23, which reframed the docs around Unzen as the current fork and Shasta as its underlying protocol architecture. A handful of places still called the live mainnet state "the current Shasta rollout / deployment / configuration". After Unzen went live on Aug 3, 2026 (taiko-mono #21991), those phrases are stale — Unzen is what's actually running.
What
Only "current live state" wording is touched. Architectural mentions of Shasta (proposal-based derivation, Shasta inbox, Shasta proving model) are left alone, matching how #23 kept the architecture/fork distinction.
docs/pages/protocol/based-rollups.mdxdocs/pages/protocol/proving-system.mdxComposeVerifier" → "The current Unzen deployment uses aComposeVerifier" (also fixes the "In the X is a Y" phrasing); "The deployed Shasta verifier set" → "The deployed verifier set"; "current live Shasta configuration" → "current live Unzen configuration"docs/pages/protocol/economics.mdxdocs/pages/resources/faq.mdxNet diff: +7 / -7.
🤖 Generated with Claude Code
Generated by Claude Code