Tag: Lineth L2 Lifecycle
All the articles with the tag "Lineth L2 Lifecycle".
Selecting more than one tag in the sidebar shows only posts that have every selected tag.
- #Lineth L2 Lifecycle#Ethereum#Layer 2
Lineth L2 Transaction Lifecycle (6) - Following an L2 Message to a Successful Claim on L1
The transaction from block 23,851 sent 0.02 ETH from L2 to L1 through the message service. I followed its message hash from the MessageSent event, through the postman, to the MessageClaimed event and a successful claim receipt on L1 six minutes later.
4 min read - #Lineth L2 Lifecycle#Ethereum#Layer 2
Lineth L2 Transaction Lifecycle (5) - Web3Signer: Transaction Signing, HTTPS, and L1 Sender Verification
Where the Coordinator's L1 transactions get signed. What Web3Signer signs, how the Coordinator reaches it over mutual TLS, and a check that the public keys in the config derive to the exact senders in the blob and aggregation receipts.
5 min read - #Lineth L2 Lifecycle#Ethereum#Layer 2
Lineth L2 Transaction Lifecycle (4) - Following an L2 Blob from Creation to Finalization on L1
One 80-block L2 range in my Lineth lab, from the Coordinator closing its blob, through the compression proof and the EIP-4844 blob transaction, to the DataFinalizedV3 event on the L1 rollup contract. Coordinator logs, cast receipts, and contract events, connected by range and hash.
5 min read - #Lineth L2 Lifecycle#Ethereum#Layer 2
Lineth L2 Transaction Lifecycle (3) - Inside the Prover: From a Coordinator Request to a Proof Response
What happens between the Coordinator writing a proof request and reading the result. I followed L2 blocks 26,605 to 26,684 through shared-storage request files, the prover controller, trace reading, module utilization, and the execution, compression, and aggregation responses in my Lineth lab.
6 min read - #Lineth L2 Lifecycle#Ethereum#Layer 2
Lineth L2 Transaction Lifecycle (2) - From L2 Blocks to Execution Proofs: Trace and Conflation in the Coordinator
How the Coordinator turns L2 blocks into proof work. I followed blocks 24,205 to 24,284 in my Lineth lab: an 80-block batch closed by a trace limit, a one-batch blob, an execution-proof request, and its result 3 minutes 24 seconds later.
4 min read - #Lineth L2 Lifecycle#Ethereum#Layer 2
Lineth L2 Transaction Lifecycle (1) - Following an L2 Transaction Through Besu and Maru
A transaction that is accepted, one that is included in a block, and one an RPC node can serve are three separate events. I followed L2 block 23,851 in my Lineth lab from the sequencer's payload, through the RPC node's import and head update, to a successful receipt, using only Kubernetes logs and JSON-RPC.
5 min read - #Lineth L2 Lifecycle#Ethereum#Layer 2
Lineth L2 Transaction Lifecycle (0) - The Lab Architecture
A map of the local Lineth rollup before the series opens it up: RPC Besu, the sequencer and Maru for execution, the Coordinator and Prover for proving, Web3Signer for signing, the rollup contract for settlement, and the postman for message delivery, with the evidence each one leaves.
5 min read