docs: Linea Stack -> Lineth naming migration (Protocol & Stack), Phase 2#1527
Open
Othryades wants to merge 5 commits into
Open
docs: Linea Stack -> Lineth naming migration (Protocol & Stack), Phase 2#1527Othryades wants to merge 5 commits into
Othryades wants to merge 5 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…Stack prose
Renames every stack/codebase-sense occurrence of "the Linea Stack" to Lineth,
dual-named once per page ("Lineth (formerly the Linea Stack)") then short form.
Network/product/governance senses are unchanged (Linea Mainnet, Linea network,
Linea Besu, LineaRollup, the Linea protocol).
Phase 2 / Commit A of 3.
…r Lineth GATED ON PRODUCT/MARKETING SIGN-OFF - separable; drop via git revert without affecting the Commit A renames. - Operator-deployed chains: 'their own Linea network' -> 'networks built on Lineth' (stack overview, how-it-works, deployment-models). LFDT blog says operators launch their own Ethereum-compatible networks, not 'Linea networks'. - Feature pages: 'the Linea protocol and operator stack' -> 'Lineth and operator-controlled integrations' (compliance, security, data-availability, fast-finality). Phase 2 / Commit B of 3.
…erviews New docs/protocol/linea-vs-lineth.mdx stating the network-vs-stack distinction once (incl. protocol-vs-stack: 'the Linea protocol' stays Linea, 'Lineth' is the implementation). Added to the protocol sidebar and linked from the Protocol and Stack overviews. Slug /protocol/linea-vs-lineth is provisional [VERIFY placement with docs owner]. Phase 2 / Commit C of 3.
Othryades
force-pushed
the
docs/lineth-rename-phase2
branch
from
f1dce0b to
d9a8b31
Compare
Per review (Arthur): the protocol/rules are part of the technical stack and apply to every chain built on it, so technical 'the Linea protocol' becomes 'Lineth'. 'Linea Protocol' is kept only where it means the Consortium-governed entity. Tokenomics stays Linea (Mainnet).
Per review (Arthur + Simon): drop the 'Linea protocol = network rules' carve-out and frame it as two buckets — Linea = Linea Mainnet-specific (brand, token, tokenomics, Consortium); Lineth = the technical stack and protocol, for all chains. Retitle 'Linea and Lineth', lead with 'What is Linea', add 'Linea Mainnet is built on Lineth'. Title uses 'and' (not '&') to avoid a social-card XML error; link text matched. Slug /protocol/linea-vs-lineth unchanged — no redirect needed.
Othryades
changed the title
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.
Phase 2 — Linea → Lineth naming (Protocol + Stack)
Finishes the cleanup started in #1516. Where the docs mean the open-source stack/protocol they now say Lineth; where they mean the public network/product they stay Linea.
The rule (from review):
Linea — Linea Mainnet-specific: brand, token, tokenomics, Consortium, Mainnet, Sepolia, Linea SDK.
Lineth — the technical stack and protocol, for every chain built on it.
"Linea Protocol" kept only where it means the Consortium-governed entity.
Commits:
"Linea Stack" → "Lineth" across Protocol/Stack prose
Operator chains → "networks built on Lineth"; enterprise feature pages reworded
New "Linea and Lineth" explainer (linked from both overviews)
Technical "Linea protocol" → "Lineth"
Explainer reworked to the two-bucket model
Unchanged: Linea Mainnet/Sepolia/network, Linea Besu, LineaRollup, Linea Consortium, Linea Enterprise.
Out of scope (not now): renaming tabs/sidebar sections, reframing the Protocol section, moving tokenomics.
Note: title is "Linea and Lineth" (not "&") — a raw "&" broke the social-card image generator.
Note
Low Risk
Documentation and navigation text only; no runtime, contract, or API behavior changes.
Overview
Phase 2 documentation rename: prose that meant the open-source rollup stack now says Lineth (with "Lineth (formerly the Linea Stack)" on first mention), while Linea stays for the public network, brand, token, governance, Mainnet/Sepolia, and unchanged product names (Linea Besu, LineaRollup, etc.).
Adds
docs/protocol/linea-vs-lineth.mdxas the canonical Linea vs Lineth explainer (LFDT naming model, when to use each term), registers it insidebars.js, and links it from protocol/stack overviews and quickstarts. Protocol architecture, stack features, deployment/trust/how-to pages, and related metadata/descriptions are updated accordingly; operator-owned chains are described as networks built on Lineth rather than generic "Linea stack" deployments.Reviewed by Cursor Bugbot for commit 9750a02. Bugbot is set up for automated code reviews on this repo. Configure here.