deploy: 7722954

interop/predeploys.html

@@ -266,15 +266,16 @@ <h4 id="_target"><a class="header" href="#_target"><code>_target</code></a></h4>
 <h3 id="executingmessage-event"><a class="header" href="#executingmessage-event"><code>ExecutingMessage</code> Event</a></h3>
 <p>The <code>ExecutingMessage</code> event represents an executing message. It MUST be emitted on every call
 to <code>executeMessage</code>.</p>
-<pre><code class="language-solidity">event ExecutingMessage(bytes,bytes);
+<pre><code class="language-solidity">event ExecutingMessage(bytes32 indexed msgHash, Identifier identifier);
 </code></pre>
-<p>The data encoded in the event contains the <code>Identifier</code> and the <code>msg</code>.
+<p>The data encoded in the event contains the keccak hash of the <code>msg</code> and the <code>Identifier</code>.
 The following pseudocode shows the deserialization:</p>
-<pre><code class="language-solidity">(bytes memory identifier, bytes memory log) = abi.decode(log.data, (bytes, bytes));
-Identifier id = abi.decode(identifier, (Identifier));
+<pre><code class="language-solidity">bytes32 msgHash = log.topics[1];
+Identifier identifier = abi.decode(log.data, (Identifier));
 </code></pre>
-<p>It is not possible to use solidity structs directly in events, which is why it is ABI encoded
-into <code>bytes</code> first.</p>
+<p>Emitting the hash of the message is more efficient than emitting the
+message in its entirety. Equality with the initiating message can be handled off-chain through
+hash comparison.</p>
 <h3 id="reference-implementation"><a class="header" href="#reference-implementation">Reference implementation</a></h3>
 <p>A simple implementation of the <code>executeMessage</code> function is included below.</p>
 <pre><code class="language-solidity">function executeMessage(Identifier calldata _id, address _target, bytes calldata _msg) public payable {
@@ -297,7 +298,7 @@ <h3 id="reference-implementation"><a class="header" href="#reference-implementat
 
     require(success);
 
-    emit ExecutingMessage(abi.encode(_id), _msg);
+    emit ExecutingMessage(keccak256(_msg), _id);
 }
 </code></pre>
 <p>Note that the <code>executeMessage</code> function is <code>payable</code> to enable relayers to earn in the gas paying asset.</p>

interop/sequencer.html

@@ -269,7 +269,8 @@ <h4 id="direct-dependency-confirmation"><a class="header" href="#direct-dependen
 
 for log in receipt.logs:
   if is_executing_message(log):
-      id, message = abi.decode(log.data)
+      id = abi.decode(log.data)
+      messageHash = log.topics[1]
 
       # assumes there is a client for each chain in the dependency set
       eth = clients[id.chainid]
@@ -282,7 +283,7 @@ <h4 id="direct-dependency-confirmation"><a class="header" href="#direct-dependen
       if len(log) == 0:
         return False
 
-      if message != encode(log[0]):
+      if messageHash != hash(encode(log[0])):
         return False
 
       block = eth.getBlockByNumber(id.blocknumber)

print.html

@@ -8619,15 +8619,16 @@ <h4 id="_target"><a class="header" href="#_target"><code>_target</code></a></h4>
 <h3 id="executingmessage-event"><a class="header" href="#executingmessage-event"><code>ExecutingMessage</code> Event</a></h3>
 <p>The <code>ExecutingMessage</code> event represents an executing message. It MUST be emitted on every call
 to <code>executeMessage</code>.</p>
-<pre><code class="language-solidity">event ExecutingMessage(bytes,bytes);
+<pre><code class="language-solidity">event ExecutingMessage(bytes32 indexed msgHash, Identifier identifier);
 </code></pre>
-<p>The data encoded in the event contains the <code>Identifier</code> and the <code>msg</code>.
+<p>The data encoded in the event contains the keccak hash of the <code>msg</code> and the <code>Identifier</code>.
 The following pseudocode shows the deserialization:</p>
-<pre><code class="language-solidity">(bytes memory identifier, bytes memory log) = abi.decode(log.data, (bytes, bytes));
-Identifier id = abi.decode(identifier, (Identifier));
+<pre><code class="language-solidity">bytes32 msgHash = log.topics[1];
+Identifier identifier = abi.decode(log.data, (Identifier));
 </code></pre>
-<p>It is not possible to use solidity structs directly in events, which is why it is ABI encoded
-into <code>bytes</code> first.</p>
+<p>Emitting the hash of the message is more efficient than emitting the
+message in its entirety. Equality with the initiating message can be handled off-chain through
+hash comparison.</p>
 <h3 id="reference-implementation"><a class="header" href="#reference-implementation">Reference implementation</a></h3>
 <p>A simple implementation of the <code>executeMessage</code> function is included below.</p>
 <pre><code class="language-solidity">function executeMessage(Identifier calldata _id, address _target, bytes calldata _msg) public payable {
@@ -8650,7 +8651,7 @@ <h3 id="reference-implementation"><a class="header" href="#reference-implementat
 
     require(success);
 
-    emit ExecutingMessage(abi.encode(_id), _msg);
+    emit ExecutingMessage(keccak256(_msg), _id);
 }
 </code></pre>
 <p>Note that the <code>executeMessage</code> function is <code>payable</code> to enable relayers to earn in the gas paying asset.</p>
@@ -9016,7 +9017,8 @@ <h4 id="direct-dependency-confirmation"><a class="header" href="#direct-dependen
 
 for log in receipt.logs:
   if is_executing_message(log):
-      id, message = abi.decode(log.data)
+      id = abi.decode(log.data)
+      messageHash = log.topics[1]
 
       # assumes there is a client for each chain in the dependency set
       eth = clients[id.chainid]
@@ -9029,7 +9031,7 @@ <h4 id="direct-dependency-confirmation"><a class="header" href="#direct-dependen
       if len(log) == 0:
         return False
 
-      if message != encode(log[0]):
+      if messageHash != hash(encode(log[0])):
         return False
 
       block = eth.getBlockByNumber(id.blocknumber)