AlphaFi, a yield aggregator that ran on the Sui network, is winding down after an oracle misconfiguration drained money from the vaults people had deposited into. The Sui Foundation is supporting the shutdown and helping depositors get out, but the terms of that support haven't been made public. AlphaFi's pitch was simple.
You handed it coins, it deployed them across a set of strategies on Sui, and it paid you a yield on top. Yield is the extra return you get for letting someone else decide what to do with your money. The appeal was not having to pick a strategy yourself.
What broke wasn't the strategy. It was the price feed sitting underneath it.
The mistake was in the price feed, not the strategy
An oracle is a bridge between a blockchain and the outside world. The chain itself has no idea what a coin is worth in dollars. Somebody has to feed that number in, and the thing that does it is called the oracle.
AlphaFi's oracle was misconfigured, which means the price it was working from wasn't the real market price. A feed that's off by a little is just wrong. A feed that's off by a lot is how a vault starts handing out more than it holds.
These bugs usually take one of a few shapes. A price that stopped updating and went stale. A calculation that averaged too few trades, so a single bad trade moved the number a long way.
A units mismatch, where the feed reported cents and the vault read them as dollars. The reporting doesn't say which one AlphaFi hit, and the difference matters for how the loss got created. The Defiant described the cause as a misconfiguration, and Crypto Briefing reported the same problem.
Neither has published the technical specifics or the amount lost.
A wrong price becomes missing money, and it doesn't come back
Here's the part that's easy to skip. A vault that believes a token is worth $100 when it's really worth $60 will happily value withdrawals too generously, or price shares so that people take out more than the vault can cover. The gap gets created at the moment of the transaction.
Fixing the feed later doesn't undo it. The vault is already short. Anyone who withdrew before the fix took out more than they were owed, and the shortfall lands on whoever still holds a claim.
That's why the clock matters as much as the bug itself. A misconfiguration caught within hours damages only the accounts that transacted during that window. One that runs for days pulls in every deposit and every withdrawal, and the number of affected accounts grows fast.
How long AlphaFi's feed was wrong hasn't been confirmed publicly.
The Foundation is helping, and nobody has said how much
The reporting agrees that the Sui Foundation is involved and disagrees on nothing except detail. Support is confirmed. The shape of it is not.
There's a plain reason a chain's foundation ends up in this position. AlphaFi ran on Sui, and a visible failure on a network is a bad look for that network. A foundation that runs a developer program has reason to help clean this up rather than leave it running as an open story.
A wind-down, meanwhile, is a specific and fairly boring process. Stop taking new deposits. Unwind whatever the vaults are still holding.
Work through the withdrawal queue and work out what each depositor is owed. It isn't a bankruptcy filing, because the money was never stolen. It's a project deciding to stop and hand back what it can.
What depositors actually need is narrower than the headline suggests. Three things: whether claims are honored, how fast, and whether the Foundation covers a shortfall or simply helps with the mechanics of unwinding. Those are different promises, and they mean very different things to someone waiting on a withdrawal.
The number that would settle all of this hasn't been published. That's the total user loss. Until AlphaFi releases a final figure and the Foundation says whether it's covering any of the gap, the size of the hole is a guess.
The next thing worth watching is that disclosure, and whether it arrives with a date attached.
Reader desk
Discuss the signal
Verified readers · 2 comments per post / 24h
No comments yet. Be the first verified reader to add context.