Cross-chain + INTU

INTU Account addresses and signatures are EVM-compatible, meaning the same address and keys may be used to interact with any EVM-compatible chain. In order to support broader cross-chain functionality and capabilities, INTU provides for broad flexibility in gateway/RPC selection.

The network and configuration used at account creation becomes the default orchestration network. That is, by default, the SDK will attempt to use this configuration for the signature formation process between participating factors, as well as account management functions such as account recovery.

The target or destination network for any transaction, as well as the routing to broadcast that transaction, can be defined by the INTU SDK directly when proposing an interaction. The orchestration network will be used for signature formation, but then ultimately broadcast to the destination network.

As an example, a low-cost network with quick blocktimes such as Arbitrum can be used as an orchestration network, but form transactions for slower, more expensive networks such as Ethereum Mainnet or Bitcoin. Once the signature has been aggregated, any participating factory can broadcast the fully signed transaction directly to the destination network. (Bonus points if they operate their own node and not a third party service!)

Note: INTU does not currently support cross-chain state or oracles for sharing INTU account data across different networks. INTU may support multiple orchestration networks in the future.