Edit pass: Lineth Stack evaluation docs - #1714
alexandratran wants to merge 8 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
LGTM |
bgravenorst
left a comment
bgravenorst
left a comment
There was a problem hiding this comment.
One bit of feedback that I'm not 100% certain of. Either way, may require some additional content.
| Typically that data lives on the validium's <GlossaryTerm term="Archive node">archive nodes</GlossaryTerm>. | ||
|
|
||
| ### Use cases | ||
| ### Public validiums |
There was a problem hiding this comment.
I'm not 100% sure of this, but I'm assuming Linea does not accept type 3 blob transactions, correct? If so may require some updates.
Rollups. The table cell "Posted to the finalization layer via EIP-4844 blobs" and the sentence "for example, using EIP-4844 blobs on Ethereum" both leave Linea open. Say that blob posting works only when the finalization layer is Ethereum, because Linea does not accept type 3 blob transactions?
Public validiums. The Linea Mainnet use case is currently mentioned as a cost choice. It is also the open-access model for an L3? Transaction data should stay on the network's nodes because it cannot be written to Linea as blobs.
There was a problem hiding this comment.
Rollups. The table cell "Posted to the finalization layer via EIP-4844 blobs" and the sentence "for example, using EIP-4844 blobs on Ethereum" both leave Linea open. Say that blob posting works only when the finalization layer is Ethereum, because Linea does not accept type 3 blob transactions?
Changed instances to say the rollups post data as blobs (not just an example). Will refrain from naming Ethereum as only option for rollup, since #1716 updates the "Finalization layer" page to note that Ethereum is typically used, but any network that can run the system contracts and accepts EIP-4844 blobs can theoretically be used.
There was a problem hiding this comment.
Public validiums. The Linea Mainnet use case is currently mentioned as a cost choice. It is also the open-access model for an L3? Transaction data should stay on the network's nodes because it cannot be written to Linea as blobs.
Elaborated that the public validium model is used by public L3s finalizing to Linea. The use case bullet is slightly tweaked to say: "Applications that need the lower finalization cost and faster settlement on Linea Mainnet, while keeping open access" -> which essentially covers the "open-access L3 model," since the main benefit of running an L3 instead of an L2 is cheap and fast finalization.
| Consider these questions when choosing a deployment model: | ||
|
|
||
| - [Privacy](validium.mdx) requirements: Should transaction data remain private to authorized participants? | ||
| - Privacy requirements: Should transaction data remain visible only to authorized participants? |
There was a problem hiding this comment.
We ask questions here, but the answer is in the table below, but it's not mapped identically, so the user needs to infer.
So in the table, perhaps "Transaction data" should be "Privacy requirements", or vice versa? Or we find an alternate way to answer the questions.
There was a problem hiding this comment.
Decided to simplify to just the table, with questions in the first column.
# Conflicts: # docs/stack/deployment/access-control.mdx # docs/stack/evaluate/deployment-models.mdx # docs/stack/evaluate/validium.mdx
This branch was successfully deployed
3 participants
Edit pass of Lineth Stack evaluation section, primarily:
Note
Low Risk
Documentation-only edits with redirects for removed URLs; no runtime or security behavior changes.
Overview
Removes the standalone Privacy and data visibility doc and folds that material into Deployment models, which is reframed around rollups vs validiums (with public vs private validium distinguished by who can read transaction data).
Compliance is shortened to avoid repeating Security and assurance: it now emphasizes how operators use deployment evidence, retention/disclosure via DA and access control, and cross-links instead of long “what Lineth does not claim” sections.
Navigation drops the validium page from the evaluate sidebar and index; redirects send old
/stack/evaluate/validium(and legacy feature paths) todeployment-models#private-validiums. Minor See also tweaks on access-control and security.Reviewed by Cursor Bugbot for commit 1f077e2. Bugbot is set up for automated code reviews on this repo. Configure here.