AaveThena is still the most risk-adjusted loop out there:
► can handle size
► is consistently 8-13%
► only SC exposures are Aave & Ethena
The only issue is it's a pain to enter/exit.
@ipor_io's Aavethena vaults optimize this on Plasma & Mainnet, averaging 9-11% for weeks.
Fusion has the most composable and detailed view of vault strategies of any protocol out there.
Honestly better positioned than most vault protocols for the assets/markets composition shift currently underway
Vault Summit in Cannes brought strong interest in Fusion's vault architecture and the newly announced collaboration with @tesseractcrypto
Conversations at the event were consistently shaped around compliance, risk frameworks, and how institutional capital can operate onchain within regulatory boundaries. The demand for dedicated, per-client vault deployments was a recurring theme across panels and side meetings.
Tesseract CEO @jemharris11 highlighted the newly launched Dedicated Client Vault product line during his panel, with @21shares among the pilot partners and Fusion as the key infrastructure layer underneath.
Thanks for having Fusion and Tesseract as part of the event, @Vault__Summit!
Fusion vaults are accessible to institutional users within @Anchorage Digital's Porto App.
For qualified vault operators building on Fusion, this opens a path to institutional visibility.
Full case study ↓
🥈 YO Treasury, built by @le_brande, is an app that wraps all YO vaults into a single position and securely manages that position through an AI agent.
Deposit once, and an AI copilot handles the rest — allocating across YO vaults, swapping between assets, and rebalancing — all executed as batch transactions with a single wallet signature.
Learn more: https://t.co/HyYXpHeE9u
Porto users: Fusion from @ipor_io is now discoverable in the featured dApp section, allowing you to connect your wallet to access 25+ professionally curated, fully automated yield strategies.
@_jxom My mistake I referred only to Promise_all. Yes, that’s cool and seamless feature, I love it, thanks for that ❤️. But how to manage sequential calls when output of the prev one is an input for another? Either like in the post or dedicated smart contract. Do I miss anything?
Same evolution here. Hook per call pattern becomes unmanageable regardless of how well viem+wagmi batches RPC. you end up fighting React instead of working with it. Moving data composition to plain async functions with Promise_all control was the turning point.
A powerful transparency upgrade is coming to the IPOR Fusion app.
Credit Markets breakdown - a transparent view of where liquidity sits, how it’s deployed, and what drives performance, market by market.