deploy: 34dd8bd

interop/messaging.html

@@ -284,9 +284,11 @@ <h3 id="initiating-messages"><a class="header" href="#initiating-messages">Initi
 <p>An initiating message may be executed many times: no replay-protection is enshrined in the protocol.</p>
 <h3 id="executing-messages"><a class="header" href="#executing-messages">Executing Messages</a></h3>
 <p>An executing message is represented by the <a href="./predeploys.html#executingmessage-event">ExecutingMessage event</a> that is emitted by
-the <code>CrossL2Inbox</code> predeploy. This event is coupled to a <code>CALL</code> 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.</p>
+the <code>CrossL2Inbox</code> predeploy. If the cross chain message is directly executed via <a href="./predeploys.html#executemessage">executeMessage</a>,
+the event is coupled to a <code>CALL</code> 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 <a href="./predeploys.html#validatemessage">validateMessage</a>.</p>
+<p>All of the information required to satisfy the invariants MUST be included in this event.</p>
 <p>Both the block builder and the verifier use this information to ensure that all system invariants are held.</p>
 <p>The executing message is verified by checking if there is an existing initiating-message
 that originates at <a href="#message-identifier"><code>Identifier</code></a> with matching <a href="#message-payload">Message Payload</a>.</p>