Skip to main content

L1MessageManagerV1

INBOX_STATUS_UNKNOWN​

uint8 INBOX_STATUS_UNKNOWN

The 2 legacy status constants for message statuses.

INBOX_STATUS_RECEIVED​

uint8 INBOX_STATUS_RECEIVED

OUTBOX_STATUS_UNKNOWN​

uint8 OUTBOX_STATUS_UNKNOWN

The 3 legacy status constants for message statuses.

OUTBOX_STATUS_SENT​

uint8 OUTBOX_STATUS_SENT

OUTBOX_STATUS_RECEIVED​

uint8 OUTBOX_STATUS_RECEIVED

outboxL1L2MessageStatus​

mapping(bytes32 => uint256) outboxL1L2MessageStatus

DEPRECATED in favor of the rollingHashes mapping on the L1MessageManager for L1 to L2 messaging.

inboxL2L1MessageStatus​

mapping(bytes32 => uint256) inboxL2L1MessageStatus

Mapping to store L2->L1 message hashes status. messageHash => messageStatus (0: unknown, 1: received). For the most part this has been deprecated. This is only used for messages received pre-AlphaV2.

_updateL2L1MessageStatusToClaimed​

function _updateL2L1MessageStatusToClaimed(bytes32 _messageHash) internal

Update the status of L2->L1 message when a user claims a message on L1.

The L2->L1 message is removed from storage. Due to the nature of the rollup, we should not get a second entry of this.

Parameters​

NameTypeDescription
_messageHashbytes32Hash of the message.
Contributions not accepted
These reference pages are automatically generated based on Linea's smart contracts. To ensure they accurately match the deployed smart contracts, we cannot accept any contributions that edit these pages.