Skip to main content

@morph-l2/sdkDocs


@morph-l2/sdk / MessageStatus

Enumeration: MessageStatus

Enum describing the status of a message.

Enumeration Members

FAILED_L1_TO_L2_MESSAGE

FAILED_L1_TO_L2_MESSAGE: 1

Message is an L1 to L2 message and the transaction to execute the message failed. When this status is returned, you will need to resend the L1 to L2 message, probably with a higher gas limit.

Source

src/interfaces/types.ts:186


IN_CHALLENGE_PERIOD

IN_CHALLENGE_PERIOD: 5

Message is a proved L2 to L1 message and is undergoing the challenge period.

Source

src/interfaces/types.ts:206


READY_FOR_RELAY

READY_FOR_RELAY: 6

Message is ready to be relayed.

Source

src/interfaces/types.ts:211


READY_TO_PROVE

READY_TO_PROVE: 4

Message is ready to be proved on L1 to initiate the challenge period.

Source

src/interfaces/types.ts:201


RELAYED

RELAYED: 7

Message has been relayed.

Source

src/interfaces/types.ts:216


UNCONFIRMED_L1_TO_L2_MESSAGE

UNCONFIRMED_L1_TO_L2_MESSAGE: 0

Message is an L1 to L2 message and has not been processed by the L2.

Source

src/interfaces/types.ts:179


WITHDRAWAL_HASH_NOT_SYNC

WITHDRAWAL_HASH_NOT_SYNC: 3

Message is an L2 to L1 message and withdrawal hash has not been published to backend yet.

Source

src/interfaces/types.ts:196


WITHDRAWAL_ROOT_NOT_PUBLISHED

WITHDRAWAL_ROOT_NOT_PUBLISHED: 2

Message is an L2 to L1 message and withdrawal root has not been published yet.

Source

src/interfaces/types.ts:191