in the rapidly evolving realm of decentralized finance (DeFi), the rise of Layer 2 (L2) solutions has brought about a multitude of DeFi protocols across different blockchain networks. This abundance of options presents a challenge for users seeking to efficiently manage their investments across various chains. Enter Chain Diversify, a pioneering cross-chain DeFi solution designed to streamline investments across a diverse range of blockchain ecosystems, including non-Ethereum Virtual Machine (EVM) chains.
Key Highlights of Chain Diversify:
Multi-Chain Vault Protocol: Chain Diversify introduces a versatile multi-chain vault protocol, currently operational on the Avalanche (AVAX) Fuji Testnet. This protocol aims to provide a comprehensive DeFi experience.
Seamless Network Management: Chain Diversify offers a solution to the complex task of navigating between different blockchain networks. Users can effortlessly manage their investments without the need to constantly switch networks, making DeFi more user-friendly.
Core Features:
ERC-4626 Vaults: Chain Diversify utilizes ERC-4626 vaults to distribute ERC-20 Liquidity Provider (LP) shares. These shares can be easily withdrawn or staked in the MasterChef for additional rewards.
Wormhole Relayers and SDK Smart Contracts: The platform leverages Wormhole relayers and SDK smart contracts to enable smooth message transfers between distinct blockchain networks, ensuring interoperability and efficient communication.
Native Token Integration: To enhance the user experience, Chain Diversify employs the Stargate Bridge to acquire native ERC-20 tokens on destination chains, avoiding the need for wrapped tokens. In cases where Stargate is unavailable, the platform has proprietary liquidity pools for the exchange of wrapped and native tokens. Wormhole is used to mint wrapped tokens, further facilitating seamless cross-chain transactions
We encountered challenges when integrating the frontend with the smart contracts. Additionally, we faced difficulties with the bridges, particularly with the token wrapping process in Wormhole, which posed an issue as it required subsequent unwrapping.
Tracks Applied (2)
Wormhole
Avalanche
Technologies used
Discussion