MZF Protocol lends USDC to web3 projects against milestones. Lenders pool capital in a master vault or back a single deal directly, and the contracts handle funding, releases, repayments and a set plan for loans that go wrong.
Web3 teams often need funding before they have revenue or a token to sell, and equity rounds dilute them. Lenders who would fund them want the protections of venture debt: milestones, covenants, warrants and a clear path when a borrower falls behind.
On-chain credit has a mixed record, mostly because defaults were handled by hand and late. MZF writes the whole life of a loan into contracts, from the proposal to the workout, so lenders can see in advance exactly what happens to their money in each case.
Every step below is a contract call. Off-chain due diligence feeds the decision; the money only moves on-chain.
Whoever proposes a deal stakes $MZF, sized by the loan. A committee approves it, or it goes live by itself after a challenge window. The stake is held for the life of the loan.
Each deal gets its own sub-vault. Direct lenders lock USDC and receive a transferable receipt; the master vault tops up the rest within its per-deal and buffer limits.
USDC goes to the borrower milestone by milestone. Repayments pay interest first, then principal and fees, split pro rata between direct lenders and the master vault.
A repaid loan returns the proposer's stake. A loan in trouble enters the workout protocol below, and if lenders lose money the stake is slashed and paid to them.
We designed about 50 screens before writing the app, then built them on the contracts. These are from the design canvas, with example data.
Each loan carries a payment schedule. Anyone can advance its stage once a deadline passes, so nobody has to decide when a borrower is in trouble.
The contracts have had an internal security review and are being prepared for an external audit. They are not deployed yet.
Pooled and direct funding, tranches, interest waterfalls, fees and redemption queues.
Positions, claims, documents and onboarding, designed for desktop and mobile together.
Allowlists, role separation, timelocked changes and spend caps built in from the first contract.
Fuzz and invariant testing, internal review and an audit-prep list before code goes to auditors.
Tell us what you're building and we'll come back with how we'd approach it.