Kava Lend’s idle BUSD market was used for abnormal borrowing, with approximately 55.2 million KAVA borrowed. The team limited the scope of the incident to Kava Lend and explicitly stated that this was not an unlimited token mint.
Limiting the scope doesn’t mean the shortfall on the books has been filled. Abnormal collateral valuations supported 127 loans; approximately 49.2 million KAVA was then bridged to BNB Chain, where some of it was sold for about $2.09 million. The risk spread from the lending pool to external markets.
The pool data from November 14 is more direct: against deposit liabilities of approximately 55.2 million KAVA, only 0.19 KAVA remained in the pool at one point. But that was the balance at the time, and it shouldn’t be treated as the final loss; subsequent deposits, recoveries, or compensation could all change the books.
Next, we need to see the full post-mortem and whether the pool’s latest assets can cover its deposit liabilities. If the vulnerability has been contained but depositors’ shortfall remains unresolved, should the market treat this as a technical incident or a credit event?
Limiting the scope doesn’t mean the shortfall on the books has been filled. Abnormal collateral valuations supported 127 loans; approximately 49.2 million KAVA was then bridged to BNB Chain, where some of it was sold for about $2.09 million. The risk spread from the lending pool to external markets.
The pool data from November 14 is more direct: against deposit liabilities of approximately 55.2 million KAVA, only 0.19 KAVA remained in the pool at one point. But that was the balance at the time, and it shouldn’t be treated as the final loss; subsequent deposits, recoveries, or compensation could all change the books.
Next, we need to see the full post-mortem and whether the pool’s latest assets can cover its deposit liabilities. If the vulnerability has been contained but depositors’ shortfall remains unresolved, should the market treat this as a technical incident or a credit event?