Smart Contracts

CK App does not deploy its own swap or bridge contracts. Instead, it leverages the LI.FI Protocol which routes transactions through audited smart contracts of established protocols.

Architecture

User Wallet → LI.FI Diamond Contract → DEX/Bridge Contracts → Destination

When you execute a swap or bridge through CK App:

1. The LI.FI SDK generates transaction data targeting the LI.FI Diamond Proxy contract
2. The Diamond contract routes the call to the appropriate DEX or bridge facet
3. The underlying protocol's contracts execute the swap or transfer
4. Tokens arrive in your wallet (same chain or cross-chain)

Audited Protocols

All swaps and bridges route through established, audited protocols:

• Uniswap — Audited by Trail of Bits, ABDK
• Aave — Audited by Certora, SigmaPrime, Trail of Bits
• Curve — Audited by Trail of Bits
• Stargate — Audited by Quantstamp, Zellic
• LI.FI Diamond — Audited by multiple firms, bug bounty active

Contract Addresses

LI.FI Diamond Proxy addresses by chain:

LI.FI uses the same Diamond address across all EVM chains for consistency.

Integration Note

Always use the LI.FI SDK or CK App frontend rather than interacting with contracts directly. The SDK handles:

• Correct calldata encoding for each DEX/bridge
• Token approval checks and management
• Gas estimation and optimization
• Routing across multiple steps when needed