Turning fund operations into a usable interface
This internship PoC explores how a web application can make on-chain fund operations understandable. It focuses on two roles: a manager creating a fund and configuring fees, and an investor browsing funds, subscribing and redeeming shares.
I connected a Next.js interface to Enzyme Protocol through Ethers.js on Sepolia.
What I worked on
- Manager journey: fund creation, denomination-asset selection and fee configuration.
- Investor journey: wallet connection, fund browsing, token approval, subscription and redemption.
- Transaction feedback: distinguish a wallet signature from a submitted transaction and an on-chain confirmation, then refresh the relevant balances.
Built on Enzyme’s existing contracts, my work focused on the application layer: turning protocol operations into clear user journeys and transaction feedback.
The boundary that mattered
Signing is not settlement. A web interface needs to distinguish approval, pending confirmation and the resulting fund position. A rejected signature should not look like a completed subscription, and a redemption should show which assets the user receives rather than imply a guaranteed cash payout.
I treated those states as part of the interface, not as details to hide behind a loading indicator.
Scope
This is a testnet PoC, with demonstration data used in parts of the application. It is not a live investment service, an independently audited product or a record of investment performance. The focus is the interaction between the interface, wallet and fund protocol.
Implementation reference: On-chain Fund repository.