Use Cases

How do protocols use CrossCall?

CrossCall's key usecases are for gear towards protocols involved with orderflow aggregation, liquidity (DEX) aggregation, bridging, crosschain liquidity, multichain marketplaces.

Bridging

Bridging is a daunting and potentially dangerous endeavor for protocols and end-users. Since our execution flow is funded by our solver layer, they are the liquidity provider for native execution. After completing execution of the users transaction, the solver is deterministically paid out of the users lock. This completely circumvents any traditional bridging layer.

Loses incurred by bridges via hacks from 2020 ~ 2023 (note there have been additional hacks since)

For CrossCall the risk is not for the end-users, since our execution flow is validated to be in a canonical order flow, rather the solver. It is theorized that the solvers in our network are potentially vulnerable to reorgs and thus the MEV from bids in their userop bundle execution could potentially be stolen.

How can a protocol (or user) create a bridge request using CrossCall?

// Execution orderflow of the Bridge is transfer of asset(s) from the signers SCW to the users EOA address
// Below is the exact bytecode submitted to the CrossCall API for a bridge request of native assets
0xb61d27f6000000000000000000000000[target][amount]0000000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000000

The CrossCall API call request can be referenced here.

---

Native Execution (Multi-Chain Execution/Marketplaces)

Normally protocols require multiple deployments to have a market presence on different blockchains. CrossCall also for native execution using the solvers. Protocols like Magic Eden and OpenSea operate on multiple chains (OpenSea is particular operates on 10 chains). To interact on new chain their infra needs to be redploy on new chains (not including modification to their backend, which is also required).

By deliberately executing through CrossCall for new chains, users can execute natively using existing infra while users utilize funds from any chain. This execution is seemless to the user. From the users prospective, they are executing on their native chain, but in-fact will execute on the protocols selected native chain.

// user wants to sell a DOGECHAIN NFT on the OpenSea
// OpenSea maps the DOGECHAIN NFTs to Polygon, but all prices (listings etc are shown in DOGE)
// 

Crosschain Liquidity

Crosschain liquidity is maintain through warp routes and is fragmented across chains. Wrap routes burn tokens on the native chain to supply tokens (or synthetic assets) on the target chain (see OHM). This is an inefficient use of liquidty. Liquidity can be concentrated on a single chain using CrossCall.

---

Crosschain Execution

DEX aggregators like sushiswap unify liquidity across multiple DEX. With CrossCall this system is extendable to liquidity across multiple chains, which maintaining the same atomic execution.

Orderflow aggregator like CowSwap or Coinbase can expand price matching to more chains.

For chains connected to obscure bridges like Wanchain but have active liquidity of CEXs, CrossCall enables instant atomic P2P bridging without the use of a bridge.

Marketplaces like Magic Eden and OpenSea operate on multiple blockchains but they stuggle to port new chains. CrossCall allows their users on new chains to use liquidity from new chains.