This is a straightforward demonstration of how to achieve cross-chain communication between Goerli and Optimism Goerli using LayerZero. You can easily transfer strings between the two networks by following these steps:
1. Edit the provided code into Remix.
2. Deploy the code on both LayerZero Optimism Goerli and LayerZero Goerli networks using the provided lzEndpoints in the constructor argument.
3. Approve the other contract address on both deployed contracts using the trustAddress(address _otherContract) function.
4. Once approved, you can send messages between the two contracts using the send("Hello World") function. Remember to include some funds by adding a value amount.

This function is an internal override of the _nonblockingLzReceive function. It decodes the payload passed to it as a parameter using the ABI (Application Binary Interface) and stores the result in the data variable. The payload is expected to be a string. (autogenerated documentation)

This function sends a message to a destination chain ID. It takes a string as an argument and encodes it into a byte array. It then calls the _lzSend function, passing in the destination chain ID, the encoded message, the address of the sender, an address of 0x0, an empty byte array, and the value of the message. The _lzSend function is responsible for sending the message to the destination chain. (autogenerated documentation)

This function allows the owner of the contract to trust a specific address. It takes in an address of another contract as an argument and stores it in the trustedRemoteLookup mapping. The mapping is indexed by the destChainId and stores the address of the other contract and the address of the current contract. The data is encoded using the abi.encodePacked function. (autogenerated documentation)

Layer Zero Message Example

// SPDX-License-Identifier: MIT
// OpenZeppelin Contracts v4.4.1 (utils/Context.sol)

pragma solidity ^0.8.0;

/**
 * @dev Provides information about the current execution context, including the
 * sender of the transaction and its data. While these are generally available
 * via msg.sender and msg.data, they should not be accessed in such a direct
 * manner, since when dealing with meta-transactions the account sending and
 * paying for execution may not be the actual sender (as far as an application
 * is concerned).
 *
 * This contract is only required for intermediate, library-like contracts.
 */
abstract contract Context {
    function _msgSender() internal view virtual returns (address) {
        return msg.sender;
    }

    function _msgData() internal view virtual returns (bytes calldata) {
        return msg.data;
    }
}


Layer Zero Message Example

*Visit desktop site to download or deploy

Version

Creator

Last Publish

Get Cookin'
Share

Last Publish

Version

Creator

Layer Zero Message Example

*Visit desktop site to download or deploy

Version

Creator

Last Publish

Get Cookin'Share

Last Publish

Version

Creator

Get Cookin'
Share