`recipient` is typed as `address` (non-EVM compatibility)

[CluEleSsUK]

The recipient field is currently typed as address limiting compatibility with non-EVM chains.

Some non-EVM chains (e.g. Sui) also lack a chainId, suggesting a different contract type may be required to interoperate with them.

Wormhole solves this by assigning each chain its own "wormhole chainId", but these sometimes differ from EVM chainIds (e.g. Solana is chainId 1 and ETH is chainId2 :o).
Alternative approaches: reserve an upper uint256 range, or use a bytes type for recipients.

Consider this ticket a discussion on best approach for multi-chain support.

[najienka]

Adding some links / suggestions here from the design session for discussion to come back to:

• ERC-7683: https://ethereum-magicians.org/t/erc-7683-cross-chain-intents-standard/19619/2
• Hash chain name and convert to uint265 for chain id in a chain id provider contract
• CAIP2: https://chainagnostic.org/CAIPs/caip-2
• Crosschain Identifier specification: https://entethalliance.github.io/crosschain-interoperability/crosschainid.html