From 51d43cc86c60c900cdff63d3be3b91d5d4d16aae Mon Sep 17 00:00:00 2001 From: hamdiallam Date: Fri, 27 Sep 2024 21:20:03 +0000 Subject: [PATCH] deploy: 34dd8bd49b43d17ae1bd1bbf27cef520c4629e4f --- interop/messaging.html | 8 +- interop/predeploys.html | 165 ++++++++++++++++++++++---------------- print.html | 173 +++++++++++++++++++++++----------------- searchindex.js | 2 +- searchindex.json | 2 +- 5 files changed, 206 insertions(+), 144 deletions(-) diff --git a/interop/messaging.html b/interop/messaging.html index 12d7dc421..aed545b5e 100644 --- a/interop/messaging.html +++ b/interop/messaging.html @@ -284,9 +284,11 @@

Initi

An initiating message may be executed many times: no replay-protection is enshrined in the protocol.

Executing Messages

An executing message is represented by the ExecutingMessage event that is emitted by -the CrossL2Inbox predeploy. This event is coupled to a CALL with the payload that is emitted -within the event, allowing introspection of the data without needing to do call tracing. -All of the information required to satisfy the invariants MUST be included in this event.

+the CrossL2Inbox predeploy. If the cross chain message is directly executed via executeMessage, +the event is coupled to a CALL with the payload that is emitted within the event to the target +address, allowing introspection of the data. Contracts can also introduce their own public +entrypoints and solely trigger validation of the cross chain message with validateMessage.

+

All of the information required to satisfy the invariants MUST be included in this event.

Both the block builder and the verifier use this information to ensure that all system invariants are held.

The executing message is verified by checking if there is an existing initiating-message that originates at Identifier with matching Message Payload.

diff --git a/interop/predeploys.html b/interop/predeploys.html index 9b7b423b2..75e4c33bc 100644 --- a/interop/predeploys.html +++ b/interop/predeploys.html @@ -196,11 +196,10 @@

Predeploys