Skip to content

Define the node and role vocabulary - #1693

Merged
alexandratran merged 7 commits into
Consensys-Incorporated:mainfrom
bgravenorst:terminology-node-roles
Sep 2, 2026
Merged

Define the node and role vocabulary#1693
alexandratran merged 7 commits into
Consensys-Incorporated:mainfrom
bgravenorst:terminology-node-roles

Conversation

@bgravenorst

@bgravenorst bgravenorst commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator

Summary

Defines the node and role vocabulary (validator, sequencer, follower, full node, RPC node)
and applies it consistently across the docs. These terms were used interchangeably in
places, most damagingly "validator" and "sequencer", which are different things: a Maru
validator is a consensus process, and the sequencer is a set of Linea Besu plugins. There
was no term at all for the two running together, so this adds sequencer node.

Follows up on @Othryades' review of #1684.

What changed

Glossary is the source of truth. Four new entries (Maru validator, Maru non-validator,
Sequencer node, Follower execution client) and eight revised (Sequencer, Full node,
Archive node, RPC node, Linea Besu, Maru, QBFT, Transaction order). Full node now
follows Ethereum's definition, keyed to verification and data retention rather than consensus
role. 59 terms to 63.

Architecture and RPC pages explain that one Maru node can drive several execution clients,
when Linea Besu is actually required (sequencer nodes and trace generation, not everything), and
that RPC nodes differ by method availability as well as state history.

Contradictions fixed. The sequencer page described multiple sequencers as something Lineth
"could adopt" while the consensus page documented it as shipping. Linea Besu was listed as a flat
requirement when follower and non-validator execution clients can be any Ethereum client. Three
pages equated a validator with a sequencer.

"Follow" disambiguated. The word carried three incompatible meanings. The client pages told
readers Geth, Besu, Erigon, and Nethermind were for people who don't want to "interact with the
network", which was never true. They now state the real constraint: these clients serve standard
Ethereum JSON-RPC, and the linea_ namespace needs Linea Besu plugins.

Ethereum vs Lineth validators separated where both meanings are live, with first-use
qualification on the yield-boost pages rather than blanket renaming.

Diagram converted to SVG. multi-validator-diagram.webp was a flat raster with no source
file and ten stale strings baked into pixels, including the retired name "Linea Stack". Replaced
with a hand-authored SVG matching lineth-deployment-architecture.svg: theme-aware CSS variables
so it tracks light and dark mode, and 47 real <text> elements so future terminology passes
catch it by grep.


Note

Low Risk
Documentation, glossary, and UI tooltip rendering only; no runtime protocol or application logic changes.

Overview
Standardizes Lineth node terminology so Maru validator (consensus), sequencer (Linea Besu plugins), sequencer node (the pair that produces blocks), follower execution client, and full/RPC node are defined once and used the same way across the site.

The glossary (src/lib/glossary.json and the generated reference page) adds four terms and revises eight others; architecture, RPC, sequencer, deployment, and run-a-node pages are rewritten to match— including when Linea Besu is required vs any Ethereum EL client, that one Maru instance can drive multiple execution clients, and that linea_ RPC needs Besu plugins while standard JSON-RPC does not. Client guides (Besu, Geth, Erigon, Nethermind) drop the misleading “don’t interact with the network” framing in favor of that RPC split.

Fixes prior contradictions (multi-sequencer as future vs shipped QBFT, flat “Linea Besu everywhere” requirements) and separates Ethereum validators from Maru validators on yield-boost copy. GlossaryTerm tooltips now show link labels as plain text (links stay on the glossary page). The multi-validator diagram is replaced with a theme-aware SVG component instead of a stale raster.

Reviewed by Cursor Bugbot for commit c3ee2e6. Bugbot is set up for automated code reviews on this repo. Configure here.

Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
@vercel

vercel Bot commented Aug 28, 2026

Copy link
Copy Markdown

@bgravenorst is attempting to deploy a commit to the Consensys Team on Vercel.

A member of the Team first needs to authorize it.

@vercel

vercel Bot commented Aug 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
doc-linea Ready Ready Preview Aug 31, 2026 11:30pm UTC

Request Review

@alexandratran alexandratran left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor feedback

Comment thread docs/protocol/architecture/sequencer/index.mdx Outdated
Comment thread docs/protocol/architecture/index.mdx Outdated
Comment thread docs/protocol/reference/zero-knowledge-glossary.mdx Outdated
Comment thread docs/protocol/architecture/index.mdx Outdated
Comment thread docs/protocol/reference/zero-knowledge-glossary.mdx Outdated
Comment thread docs/protocol/reference/zero-knowledge-glossary.mdx Outdated
Comment thread docs/protocol/reference/zero-knowledge-glossary.mdx
Comment thread docs/protocol/reference/zero-knowledge-glossary.mdx Outdated
Comment thread docs/stack/deployment/core-components.mdx Outdated
Comment thread docs/stack/deployment/data-availability-finalization.mdx Outdated
bgravenorst and others added 2 commits September 1, 2026 07:38
Co-authored-by: Alexandra Carrillo <12214231+alexandratran@users.noreply.github.com>
Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>

@alexandratran alexandratran left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@alexandratran
alexandratran merged commit 2e7de0e into Consensys-Incorporated:main Sep 2, 2026
18 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants