Skip to content

sendl2tol1msg.md

Latest commit

 

History

History
93 lines (69 loc) · 2.4 KB

sendl2tol1msg.md

File metadata and controls

93 lines (69 loc) · 2.4 KB

← Back to Instruction Set: Quick Reference

SENDL2TOL1MSG

Send L2-to-L1 message

Opcode 0x38

l2ToL1Messages.append({recipient: M[recipientOffset], content: M[contentOffset]})

Details

Sends a message to L1, with the specified recipient, from the currently executing contract. Both recipient and content must have type tag FIELD. Reverts in static calls.

Gas Costs

Component Value Scales with
L2 Base 418 -
DA Base 512 -
L2 Addressing 3 3 L2 gas per indirect memory offset
3 L2 gas per relative memory offset

* See Gas Metering for details on how gas costs are computed and applied.

Operands

Name Type Description
recipientOffset Memory offset Memory offset of the L1 recipient address
contentOffset Memory offset Memory offset of the message content

Wire Formats

See Wire Format page for an explanation of wire format variants and opcode naming (e.g., why ADD_8 vs ADD_16).

SENDL2TOL1MSG (Opcode 0x38):

---
title: "SENDL2TOL1MSG"
config:
  packet:
    bitsPerRow: 48
---
packet-beta
0-7: "Opcode (0x38)"
8-15: "Addressing modes"
16-31: "Operand: recipientOffset"
32-47: "Operand: contentOffset"
Loading

Addressing Modes

See Addressing page for a detailed explanation.

8-bit bitmask: 2 bits per memory offset operand (indirect flag + relative flag)

Memory offset operands (recipientOffset, contentOffset) are encoded as follows:

---
title: "Addressing Mode Bitmask"
config:
  packet:
    bitWidth: 128
    bitsPerRow: 8
---
packet-beta
  0: "recipientOffset is indirect"
  1: "recipientOffset is relative"
  2: "contentOffset is indirect"
  3: "contentOffset is relative"
  4: "Unused"
  5: "Unused"
  6: "Unused"
  7: "Unused"
Loading

Tag Checks

  • T[recipientOffset] == FIELD
  • T[contentOffset] == FIELD

Error Conditions

  • INVALID_TAG: Recipient or content is not FIELD
  • STATIC_CALL_VIOLATION: Attempted L2-to-L1 message send in static call context
  • SIDE_EFFECT_LIMIT_REACHED: Exceeded maximum L2-to-L1 messages per transaction (MAX_L2_TO_L1_MSGS_PER_TX)
  • MEMORY_ACCESS_OUT_OF_RANGE: Memory offset operand exceeds addressable memory

← Back to Instruction Set: Quick Reference