Aurora

Integrate Widget 👇 docs.intents.aurora.dev/swap-widget/wi…

✨ Aurora Intents Widget Update ✨ @AleoHQ is now added to the Widget Studio. Aleo brings privacy-focused infrastructure to Web3 - now added as another entry point for cross-chain swaps, deposits, and app flows. One widget. More chains. Cleaner paths into your app. Live in Aurora Studio 👇 studio.aurora.dev

Integrate Widget 👇 docs.intents.aurora.dev/swap-widget/wi…

✨ New in Aurora Intents Widget ✨ @BitcoinCashOG is one of the original payment-focused blockchain networks - now added as another entry point for cross-chain swaps, deposits, and app flows. Try it here 👇 studio.aurora.dev

Use cases this unlocks: ✨ Staking apps: accept deposits from non-native chains ✨ Vaults: let users enter strategies from the assets they already hold ✨ Lending markets: route source assets into accepted collateral ✨ LP products: convert incoming assets into pool-ready liquidity ✨ Trading apps: fund balances from external chains ✨ Consumer apps: turn cross-chain funding into one embedded action The technical shift is simple: Apps stop asking users to route themselves. They define the outcome, and Aurora Intents handles the path. Demo: intents-connect-landing.vercel.app/demo-tonstaker…

Example flow: User has funds on TON. Protocol requires a different asset and/or destination chain for staking. ❇️ Without Intents: leave app → find bridge → bridge → swap → get gas → return → deposit ❇️ With Intents: stay in app → send from TON → intent handles routing → protocol receives the intended deposit The app keeps the user inside the product flow.

Most deposit flows assume users already have the right setup: - Correct chain and asset - Enough gas - Wallet connected - Ready to deposit That’s rarely true. Users show up with funds on TON, Ethereum, Base, Solana, Tron, or elsewhere. Aurora Intents abstracts the journey: - Users start with what they have - Apps define the destination/action - Intents handle routing - Protocols receive the required deposit The shift: From “bridge to the app” → “deposit into the outcome.”

Integrate Widget 👇 docs.intents.aurora.dev/swap-widget/wi…

✨ Widget Update ✨ Aurora Intents Widget now supports @Scroll_ZKP, an EVM-equivalent zkEVM with lower fees and faster execution. Apps can onboard Scroll users smoothly, without forcing an ecosystem switch. Configure it in Aurora Studio 👇 studio.aurora.dev

Integrate Widget 👇 docs.intents.aurora.dev/swap-widget/wi…

✨ New in Aurora Intents Widget ✨ We now support @Dashpay, giving users another entry point for cross-chain swaps, deposits, and app flows. More chains. More ways to enter your app with the assets users already have. Try it 👇 studio.aurora.dev

Request integration 👇 intents.aurora.dev

In the latest episode of Alpha Leaks, @declan_hannon covered how Intents Connect is revolutionizing DeFi by automating swaps, deposits, and staking directly within your dApp. Say goodbye to user drop-off and hello to seamless crypto experiences. Hear it out 👇

Integrate Widget 👇 docs.intents.aurora.dev/swap-widget/wi…

✨ Widget update ✨ Aurora Intents Widget now supports @Plasma, a high-performance EVM Layer 1 for stablecoin payments with zero-fee USDT transfers. Faster, cheaper cross-chain entry so users can use your app without switching ecosystems. Configure it in Aurora Studio 👇 studio.aurora.dev

5/ That is the execution gap Aurora Intents is built for. From moving assets across chains to completing actions across apps. From “how do I get the right asset here?” to “how do I get the outcome done?” Explore Aurora Intents: intents.aurora.dev

4/ Bridges move assets. But your users do not want to “move assets.” They want to deposit into a vault, fund a trading balance, enter a market, stake, mint, or take an action. Cross-chain UX should end inside the app.

Most cross-chain flows still look like this: Bridge → switch network → find gas → swap asset → approve → retry → deposit → hope it worked. Maybe. And somehow we still call this onboarding.