emo-eth

###########
# Imports #
###########

# the RPCs file should include RPC URLs and Etherscan API Keys for relevant networks
# (in a separate file so they don't get committed)
source "$(dirname "$0")/rpcs.sh"
# any useful addresses for various networks for easy reference
source "$(dirname "$0")/addresses.sh"
# any useful functions and definitions for interacting with Seaport

cwhinfrey

An Incomplete Taxonomy of Cross-Chain Messages

Single or Batched

Single Messages - Single messages have a single target address, target chainId, and data payload. The vast majority of cross-chain messages today are single messages.

Example:

function dispatchMessage(uint256 toChainId, address to, bytes calldata data) external payable returns (bytes32 messageId);

Alexintosh

pragma solidity ^0.8.0;

 contract AtomicityGuard {

    // address => block => status
    uint256 private constant _ENTERED = 1;

    mapping(address => mapping( uint256 => uint256)) ledger;

    modifier nonAtomic() {