Move tokens to yourself, send to another address, or bridge and call any smart contract in one action.
In Nexus, apart from crosschain swaps, users can do Bridge, Transfer, Execute, and Bridge & Execute which use Nexus chain abstraction (aka Bridge Methods).All of these operations share the same core parameters: toTokenSymbol (the token to receive), toAmountRaw (the amount as a bigint in the token's smallest units), toChainId (the destination chain), and an optional sources array to limit which chains liquidity comes from.Let's understand what each Nexus operation is and what it does.
Bridge
During the Bridge operation, the funds are bridged from N source chains to the user's preferred destination chain.Sender = RecipientShowing a subset of supported chains. See Supported Chains & Tokens for the full list.
This operation uses the BridgeParams type and the bridge() function from the Bridge Methods in the SDK.
Transfer
During the Transfer operation, the funds are bridged from N source chains from the Sender to the user's preferred destination chain at a different Recipient address. This is a compound operation: funds are bridged from multiple source chains to a destination chain, then transferred to the Recipient address.Sender != RecipientShowing a subset of supported chains. See Supported Chains & Tokens for the full list.
This operation uses the TransferParams type and the bridgeAndTransfer() function from the Bridge Methods in the SDK.
Execute
The Execute operation calls any smart contract function on a destination chain using funds the user already holds there. All the developer needs is the contract address and calldata. It is the building block that Bridge & Execute composes with a bridge.This operation uses the ExecuteParams type and the execute() function in the SDK.
Bridge & Execute
The Bridge & Execute operation is a more complex compound operation in Nexus. In this operation, the user bridges liquidity from N source chains if there is a lack of enough liquidity on the destination chain, and then executes any arbitrary smart contract function.Note that the smart contract can be any onchain contract on the destination chain. All the developer needs is the contract address and calldata.If the user already holds enough funds on the destination chain, the SDK skips the bridge entirely and only runs the contract call — the result reports this via bridgeSkipped: true. Either way, the operation's intent hook still lets the user review and approve before anything executes.For users, this means they don't have to do a separate bridge action to use a Liquid App (Nexus powered application), and just use the app as they would if they had liquidity onchain.Showing a subset of supported chains. See Supported Chains & Tokens for the full list.