PiggyBank is taking a direct hit to its USDC vault after a hedge tied to its LAB token didn’t work.

In a disclosure dated June 6, the Solana-based DeFi yield protocol said a “basis-trading position” in LAB went “badly wrong,” cutting the vault’s net asset value by an estimated 15%. It’s the kind of loss that doesn’t come from a DeFi bug or a hack. It comes from markets behaving differently than the hedge math expected.

What PiggyBank says happened

PiggyBank frames the episode as a hedge unwind. The protocol says it closed the hedge once funding costs made the position unattractive.

The key detail is that the hedge was designed around basis trading. Basis trades live or die by relative pricing. If the spread you’re targeting widens against you, hedges can add losses rather than contain them, depending on how liquidity, leverage, and funding costs interact.

PiggyBank did not present a long narrative in the excerpt we have. But the sequence matters.

First, the LAB hedge ran as a basis-trading position. Then funding costs rose enough that the protocol chose to close the hedge. After closing, PiggyBank reported the resulting damage to the USDC vault’s NAV.

Why funding costs turn hedges into liabilities

“Funding costs” sounds like a footnote until you remember how basis trading is financed. In perpetual and related mechanisms, funding can steadily drain or credit a position. If the funding regime flips against the hedge while the underlying spread also moves the wrong way, you can end up paying to unwind losses you can’t reverse quickly.

PiggyBank’s disclosure points to exactly that failure mode. The protocol says it closed the hedge because funding costs had made it worse to keep running. That implies the cost of carry exceeded the benefit of whatever relative price protection the hedge was meant to provide.

A hedge that only works when costs stay tame is not really a hedge. It’s a bet with a faster countdown clock.

Where the money sits, and what NAV drop means

The vault in question is a USDC vault. That matters because depositors usually expect USDC-wrapped exposure with limited direct exposure to volatile token price action. Yet the protocol’s reported NAV cut indicates the vault absorbed the hedge outcome.

NAV is the accounting reality. An estimated 15% NAV reduction means the vault’s net value fell relative to its prior level after the hedge was closed. Even without additional numbers from the full report, the direction is clear. The vault didn’t escape the LAB hedge consequences.

In DeFi risk terms, this is also a reminder that “vault” does not mean “immune.” If the vault’s risk budget includes hedged positions, then failed hedges become vault losses.

What to watch next

PiggyBank hasn’t just revealed a loss. It has also provided a timing marker: the protocol disclosed the outcome on June 6 after closing the hedge.

For users, the next practical questions are the unspoken ones that follow every reported NAV hit.

How will the protocol account for remaining exposure. How will it adjust vault strategy to prevent the same hedge dynamics from repeating. And what does PiggyBank consider an acceptable hedge cost before it decides to close?

For the broader market, this serves as a live case study. Basis trades can look clean on paper and still unravel once funding, liquidity, and spread behavior align against you.

PiggyBank’s disclosure comes from The Defiant, which reported on PiggyBank’s admission that its LAB basis-trading hedge went wrong and that the USDC vault’s NAV fell by an estimated 15% after the hedge was closed due to funding costs.