MoveIt

Aptos

The protocol uses hash-time-locked contracts (HTLC) with escrow accounts to enable secure cross-chain token swaps.

Protocol Flow

Order Announcement: Maker deposits tokens into Aptos escrow with secret hash Destination Funding: Resolver funds the destination escrow on the target EVM chain Claim: Resolver reveals the secret to claim makers' tokens from Aptos escrow Completion: Maker claims resolver's tokens from EVM escrow using the revealed secret

Core Functions

initialize_swap_ledger: Setup swap ledger resource account announce_order: Create swap order and escrow account fund_dst_escrow: Fund destination escrow (resolver operation) claim_funds: Claim funds using revealed secret cancel_swap: Cancel expired order and return funds

Sui Setup For local testing, setup a sui node with RUST_LOG="off,sui_node=info" sui start --with-faucet --force-regenesis Also run npm i ts-node @mysten/sui dotenv, for testing purposes https://dev.to/goodylili/how-to-use-the-sui-typescript-sdk-2dep - Reference for local Sui node setup, with TS SDK Implementation First on the EVM chain you have Alice making an escrow account, and putting the token in chain A and locking it -> Not done by SUI

Then Bob creates an escrow account on chain B and locks the token in chain B there -> This will be done by the createEscrow function, and this resolver will manage that

After that Alice can claim the token on chain B and Bob can claim the token on chain A -> After the escrow account is created, the resolver does the claiming on behalf of Alice

MoveIt

APTOS Implementation

The Aptos Fusion+ implementation uses a hash-time-locked contract (HTLC) pattern with resource accounts for secure cross-chain swaps. The process begins when a maker creates an order by depositing tokens into an Aptos escrow account and providing a secret hash. A resolver then funds a destination escrow on the target EVM chain with corresponding tokens. Once both escrows are funded, the resolver reveals the secret to claim the maker's tokens from the Aptos escrow, while the maker can claim the resolver's tokens from the EVM escrow using the same revealed secret. The protocol ensures atomicity through the shared secret hash and uses resource accounts with signer capabilities for secure fund management.

Sui

Then Bob creates an escrow account on chain B and locks the token in chain B there -> This will be done by the createEscrow function, and this resolver will manage that

After that Alice can claim the token on chain B and Bob can claim the token on chain A -> After the escrow account is created, the resolver does the claiming on behalf of Alice

The Sui Fusion+ implementation follows a similar HTLC pattern but operates differently in the cross-chain coordination. Unlike Aptos, Sui doesn't handle the initial EVM escrow creation - that's managed on the EVM side. The Sui implementation focuses on the destination chain role, where a resolver creates an escrow account on Sui and locks tokens there. The resolver then manages the claiming process on behalf of users, handling the coordination between the EVM source escrow and the Sui destination escrow. The protocol uses Sui's object model and transaction capabilities to ensure secure token transfers and proper escrow management across the two chains.