Merge branch 'master' into feature/erc7802bridge-v2

Author: Amxx

docs/modules/ROOT/pages/crosschain.adoc

@@ -14,9 +14,9 @@ To address the lack of composability in a simple and unopinionated way, ERC-7786
 
 The ERC defines a source and a destination gateway. Both are contracts that implement a protocol to send a message and process its reception respectively. These two processes are identified explicitly by the ERC-7786 specification since they define the minimal requirements for both gateways.
 
-* On the **source chain**, the contract implements a standard xref:api:crosschain.adoc#AxelarGatewaySource-sendMessage-string-string-bytes-bytes---[`sendMessage`] function and emits a xref:api:crosschain.adoc#AxelarGatewaySource-MessagePosted-bytes32-string-string-bytes-bytes---[`MessagePosted`] event to signal that the message should be relayed by the underlying protocol.
+* On the **source chain**, the contract implements a standard xref:api:crosschain.adoc#AxelarGatewaySource-sendMessage-bytes-bytes-bytes---[`sendMessage`] function and emits a xref:api:crosschain.adoc#AxelarGatewaySource-MessageSent-bytes32-string-string-bytes-bytes---[`MessageSent`] event to signal that the message should be relayed by the underlying protocol.
 
-* On the **destination chain**, the gateway receives the message and passes it to the receiver contract by calling the xref:api:crosschain.adoc#ERC7786Receiver-executeMessage-string-string-string-bytes-bytes---[`executeMessage`] function.
+* On the **destination chain**, the gateway receives the message and passes it to the receiver contract by calling the xref:api:crosschain.adoc#ERC7786Receiver-receiveMessage-bytes32-bytes-bytes-[`receiveMessage`] function.
 
 Smart contract developers only need to worry about implementing the xref:api:crosschain.adoc#IERC7786GatewaySource[IERC7786GatewaySource] interface to send a message on the source chain and the xref:api:crosschain.adoc#IERC7786GatewaySource[IERC7786GatewaySource] and xref:api:crosschain.adoc#IERC7786Receiver[IERC7786Receiver] interface to receive such message on the destination chain.
 
@@ -37,7 +37,7 @@ NOTE: Developers can register supported chains and destination gateways using th
 
 === Sending a message
 
-The interface for a source gateway is general enough that it allows wrapping a custom protocol to authenticate messages. Depending on the use case, developers can implement any offchain mechanism to read the standard xref:api:crosschain.adoc#IERC7786GatewaySource-MessagePosted-bytes32-string-string-bytes-bytes---[`MessagePosted`] event and deliver it to the receiver on the destination chain.
+The interface for a source gateway is general enough that it allows wrapping a custom protocol to authenticate messages. Depending on the use case, developers can implement any offchain mechanism to read the standard xref:api:crosschain.adoc#IERC7786GatewaySource-MessageSent-bytes32-string-string-bytes-bytes---[`MessageSent`] event and deliver it to the receiver on the destination chain.
 
 [source,solidity]
 ----
@@ -48,9 +48,9 @@ NOTE: The standard represents chains using https://github.com/ChainAgnostic/CAIP
 
 === Receiving a message
 
-To successfully process a message on the destination chain, a destination gateway is required. Although ERC-7786 doesn't define a standard interface for the destination gateway, it requires that it calls the `executeMessage` upon message reception.
+To successfully process a message on the destination chain, a destination gateway is required. Although ERC-7786 doesn't define a standard interface for the destination gateway, it requires that it calls the `receiveMessage` upon message reception.
 
-Every cross-chain message protocol already offers a way to receive the message either through a canonical bridge or an intermediate contract. Developers can easily wrap the receiving contract into a gateway that calls the `executeMessage` function as mandated by the ERC.
+Every cross-chain message protocol already offers a way to receive the message either through a canonical bridge or an intermediate contract. Developers can easily wrap the receiving contract into a gateway that calls the `receiveMessage` function as mandated by the ERC.
 
 To receive a message on a custom smart contract, OpenZeppelin Community Contracts provide an xref:api:crosschain.adoc#ERC7786Receiver[ERC7786Receiver] implementation for developers to inherit. This way your contracts can receive a cross-chain message relayed through a known destination gateway gateway.
 
@@ -125,10 +125,10 @@ function sendMessage(
 }
 ```
 
-On the receiving end, the bridge implements a threshold-based confirmation system. Messages are only executed after receiving enough confirmations from the gateways, ensuring message validity and preventing double execution. The xref:api:crosschain.adoc#ERC7786OpenBridge-executeMessage-string-string-string-bytes-bytes---[`executeMessage`] function handles this process:
+On the receiving end, the bridge implements a threshold-based confirmation system. Messages are only executed after receiving enough confirmations from the gateways, ensuring message validity and preventing double execution. The xref:api:crosschain.adoc#ERC7786OpenBridge-receiveMessage-string-string-string-bytes-bytes---[`receiveMessage`] function handles this process:
 
 ```solidity
-function executeMessage(
+function receiveMessage(
     string calldata /*messageId*/, // gateway specific, empty or unique
     string calldata sourceChain, // CAIP-2 chain identifier
     string calldata sender, // CAIP-10 account address (does not include the chain identifier)
@@ -146,7 +146,7 @@ function executeMessage(
         emit Received(id, msg.sender);
 
         // if already executed, leave gracefully
-        if (tracker.executed) return IERC7786Receiver.executeMessage.selector;
+        if (tracker.executed) return IERC7786Receiver.receiveMessage.selector;
     } else if (tracker.executed) {
         revert ERC7786OpenBridgeAlreadyExecuted();
     }
@@ -160,7 +160,7 @@ function executeMessage(
 
         // ... Prepare execution context and validate state ...
         bytes memory call = abi.encodeCall(
-            IERC7786Receiver.executeMessage,
+            IERC7786Receiver.receiveMessage,
             (uint256(id).toHexString(32), sourceChain, originalSender, unwrappedPayload, attributes)
         );
 
@@ -169,7 +169,7 @@ function executeMessage(
         // ... Handle the result ...
     }
 
-    return IERC7786Receiver.executeMessage.selector;
+    return IERC7786Receiver.receiveMessage.selector;
 }
 ```