$KAVA fell more than 40% in its first hour on Saturday, yet Kava says no coins were minted and the damage stayed inside one app, Kava Lend.
Short answer: this looks like one broken lending market, not a broken chain. That decides who carries the loss.
What happened:
- Kava said on Nov 14 that KAVA was bridged to BNB Chain and sold, calling it "not an infinite mint" and isolated to Kava Lend. It then paused the Axelar bridge (Cybersixt).
- Bitquery's block-by-block read: two wallets borrowed 55.2 million KAVA in 127 loans over 98 minutes, each cleared by a liquidation; the pool fell from 55.3 million to 519 KAVA.
- 48.4 million of those coins were sold on BNB Chain in 35 minutes for about $2.1 million; Upbit and Coinone paused transfers (Bitquery, TokenPost).
- Cybersixt's 17:00 UTC check found 55.2 million KAVA still on Kava Lend's books and 0.19 KAVA in the wallet behind them.
Why it matters:
- A pool's balance is an accounting number, not cash. When the share maths breaks, the app shows a deposit the pool cannot pay.
- The loss crossed a bridge: on BNB Chain it met thin liquidity, so about $2 million of sales cut the price by roughly half.
- Exchange pauses protect venues but also trap holders who did nothing wrong.
What I am watching:
- Kava's incident report: does it name the flaw and say whether depositors recover anything. No date as of 21:30 Kyiv.
- When the Axelar bridge reopens, and whether bridged KAVA trades at a visible discount first.
- Whether the 55 million KAVA gap is written down openly. On Binance, KAVA traded near $0.029, down about 57% in 24 hours at my 21:32 Kyiv snapshot.
My rule from cases like this: when a lending app's ledger and its wallet disagree, I trust the wallet, not the screen.
#KavaSaysAbnormalActivityLimitedToKavaLend #Write2Earn
If a lending app showed a balance the pool could not pay, what would you check first, and why?
Short answer: this looks like one broken lending market, not a broken chain. That decides who carries the loss.
What happened:
- Kava said on Nov 14 that KAVA was bridged to BNB Chain and sold, calling it "not an infinite mint" and isolated to Kava Lend. It then paused the Axelar bridge (Cybersixt).
- Bitquery's block-by-block read: two wallets borrowed 55.2 million KAVA in 127 loans over 98 minutes, each cleared by a liquidation; the pool fell from 55.3 million to 519 KAVA.
- 48.4 million of those coins were sold on BNB Chain in 35 minutes for about $2.1 million; Upbit and Coinone paused transfers (Bitquery, TokenPost).
- Cybersixt's 17:00 UTC check found 55.2 million KAVA still on Kava Lend's books and 0.19 KAVA in the wallet behind them.
Why it matters:
- A pool's balance is an accounting number, not cash. When the share maths breaks, the app shows a deposit the pool cannot pay.
- The loss crossed a bridge: on BNB Chain it met thin liquidity, so about $2 million of sales cut the price by roughly half.
- Exchange pauses protect venues but also trap holders who did nothing wrong.
What I am watching:
- Kava's incident report: does it name the flaw and say whether depositors recover anything. No date as of 21:30 Kyiv.
- When the Axelar bridge reopens, and whether bridged KAVA trades at a visible discount first.
- Whether the 55 million KAVA gap is written down openly. On Binance, KAVA traded near $0.029, down about 57% in 24 hours at my 21:32 Kyiv snapshot.
My rule from cases like this: when a lending app's ledger and its wallet disagree, I trust the wallet, not the screen.
#KavaSaysAbnormalActivityLimitedToKavaLend #Write2Earn
If a lending app showed a balance the pool could not pay, what would you check first, and why?