Creative Bank
Create. Save. Earn.
About
The problem it solves The Creative Bank is being built as a fintech app tailored for the creative economy that acts as an easy on-ramp to decentralized finance (DeFi). **Core Features** USDC Focus: Allows users (creatives) to buy USDC (a digital US dollar) and easily earn yield on their holdings. **Tiered Yield Generation** Integrates the highly secure Aave V3 Vault for a baseline, reliable yield. Integrates the Yearn Kalani Vault for an optimized, automated, and potentially higher yield strategy. NFT Token-Gated Access: The premium, high-yield Yearn Kalani Vault is exclusively unlocked by holding a Creative Brand, Investor, or Creator membership NFT, giving substantial financial utility to your ecosystem assets. AI-Powered Experience: Uses the Crossmint GOAT AI agent to provide a conversational, "teller-like" interface. This agent simplifies complex on-chain tasks, handles transactions, and guides users through the yield options (Aave vs. Yearn), removing the common friction of crypto for the non-technical creative user. Ecosystem Liquidity: Enables seamless swapping of USDC and other digital assets supported by your Creative platform ecosystem. The platform solves the creative's challenge of low financial returns and the complexity of crypto, offering a secure way to generate passive income and manage digital wealth with the simplicity and personalization of an AI assistant.
How it's made
Challenges we ran into The hardest parts were the integration glue between on-chain protocols and the app. For the **Aave** vault, the tricky area is the deployment flow in VaultDeployModal: it has to orchestrate @aave/react’s useVaultDeploy, handle approval + execution branches, validate fee/recipient inputs, and surface wallet errors—getting every path to succeed/rollback cleanly is fussy, especially given the reliance on wagmi wallet clients. For the **Kalani** vault, the biggest challenge is probably reliable APR reporting in useKalaniApr: it depends on a Base-mainnet-only oracle, so you have to branch by environment, cope with the BigInt return format, and surface a friendly error when the oracle isn’t reachable. Those two touchpoints—complex transaction execution and cross-network oracle reads—are where I’d expect most of the time to go.