
NFTy 50
Platform to create and manage NFT Index Funds
Demo
About
The problem it solves NFTy 50 democratizes access to the NFT market, enhances liquidity, and reduces complexity, making NFT investing as simple and accessible as traditional financial instruments. - NFTy 50 simplifies access by allowing users to invest in the top-performing NFT collections through synthetic asset tokens, bypassing the need to purchase individual NFTs. - By offering an index fund of the top 50 NFTs, NFTy 50 provides diversified exposure, reducing risks while retaining growth potential. - Synthetic tokens based on NFT collections enable users to trade liquid assets on centralized and decentralized exchanges. - With chain abstraction, NFTy 50 eliminates the complexity of multi-chain interactions, creating a unified and user-friendly experience. - Synthetic tokens also fractionalize exposure, allowing smaller investors to benefit from high-value NFT market performance. - It also aggregates and tracks price feeds for top-performing NFTs, ensuring transparent and reliable market exposure. - Users will be able to hedge risks, leverage exposure, or trade based on NFT market performance without directly owning NFTs. - Finally, NFTy 50 provides a simplified portfolio overview, consolidating synthetic assets in one place with real-time performance data. Additional Features N/A We built whatever we could only during the duration of the hackathon. However, we'll be integrating this project into our larger product dripverse.org as an added utility for NFTs and other digital assets.
How it's made
Challenges we ran into We did run into several challenges into while building the project: - NFT Price Feeds are a rarity and is not easily accessible. For this project, we've simulated it, however this remains an open problem to solve later. - NFT bridges are almost non-existent. We plan to working on this problem as well later on. - Chain Abstraction is more complicated than we imagined it. Even with the promise of an easy interface, chain abstraction wasn't solved yet. We'll be working on this as well going forward.