Build Unchained Apps
summary
Avail Nexus claims developers can deploy once and pull user liquidity from anywhere, turning many 1→1 bridges into a single N→1 bridgeAndExecute that can optionally call a contract after funds arrive. The SDK offers core methods bridge, transfer, bridgeAndExecute and cross-chain swaps, React Widgets and shadcn Elements, simulation tools and requires an EIP-1193 wallet provider. Demo shows simulated N→1 deposits (e.g., pull USDC from Base/OP/Arbitrum), gasless user-side calls, and unified balances across ~12 chains with solver-dependent latency.
AI-written summary · about
chapters (17)
- 0:00Start
- 0:10Intro & goal: “unchained apps”
- 1:37Real UX pain: needing exact token on exact chain
- 3:24Nexus solves by aggregating user liquidity via intents/solvers
- 5:23Why native bridges (secure) and LP bridges (faster) still hurt UX
- 7:02Positioning: not “just a bridge”; dev SDK in-app, keep users on your UI
- 8:59From 1→1 to N→1 actions; bridge + optional execute
- 12:28TAM example: Avalanche vs rest of Web3 liquidity
- 14:00SDK (core): bridge, transfer, simulate
- 15:43bridgeAndExecute (contract addr, ABI, fn, args)
- 17:14Cross-chain swaps (exact-in / exact-out)
- 18:38UI options: Widgets (ready) & shadcn Elements (customizable)
- 19:49ETHOnline bounties & docs, starter templates, ideas
- 21:35Weekly office hours + POAP raffle
- 24:18Dev setup: init with wallet provider, get unified balances
- 29:11Demo: N→1 deposit + execute (e.g., supply to Aave)
- 32:58Q&A: liquidity sources, gas/time, security notes
