mirror of
https://github.com/vacp2p/linea-monorepo.git
synced 2026-01-09 04:08:01 -05:00
* placeholder docs * adding more documentation * documentation work in progress * add main linking or index documents * add a link images * add messaging flows * linking operator documentation and folder cleanup * use correct pathing on tokenbridge.md * link workflow documents * add function signatures * remove welcome to * cross reference blob submission and finalization * remove confusing text * use better definition of shnarf * fix broken link * add charter, diagram and address book * docs(LSC): Rename security-council-charter-v1.3.md to security-council-charter.md Signed-off-by: Julien Marchand <julien-marchand@users.noreply.github.com> * Update contracts/docs/mainnet-address-book.csv Co-authored-by: Julien Marchand <julien-marchand@users.noreply.github.com> Signed-off-by: The Dark Jester <thedarkjester@users.noreply.github.com> --------- Signed-off-by: Julien Marchand <julien-marchand@users.noreply.github.com> Signed-off-by: The Dark Jester <thedarkjester@users.noreply.github.com> Co-authored-by: Julien Marchand <julien-marchand@users.noreply.github.com>
904 B
904 B
📩 Interaction Flow: Canonical Message Sending (L2 → L1)
This document describes the step-by-step flow of how a canonical message is sent from L2 to L1 in the Linea network.
🔄 Step-by-Step Flow
- L2 User calls
sendMessage()on theL2MessageService. - The contract:
- Verifies non-empty data
- Gets the next message number
- Computes the message hash with all the message fields
- Stores the message hash and emits events
- Coordinator captures the event and message hash.
- Coordinator:
- Anchors the messaging Merkle root(s) on L1 during finalization
- Emits events for the L2 user to construct a Merkle proof
- L1 User claims the message with proof on the
LineaRollup/L1MessageService. - The contract verifies and delivers the message to the recipient.
🖼️ Diagram