A $91,000 Loss Led to a Much Larger Decision

Full Sail disclosed a security incident on August 29 and paused protocol activity while it investigated. The protocol subsequently announced on September 1 that it would wind down operations on Sui, shifting its focus from operating vaults to repaying affected users. Wind-downs of this kind remain unusual in DeFi, where teams more often patch the vulnerability and relaunch — which makes the size of the loss relative to the decision itself a notable part of this story.

In its official wind-down updates, Full Sail said approximately $91,000 had been removed from three automated vaults. The protocol added that remaining protocol-owned liquidity would go to users and that the team would absorb any shortfall so that community depositors are compensated first.

Direct vault loss: About $91,000 was removed from three automated vaults.

Repayment commitment: Protocol-owned liquidity and team funds have been pledged to community depositors.

Still unknown: The protocol has not disclosed total claims, available repayment liquidity, or claim mechanics.

Full Sail has not published a balance sheet demonstrating that the $91,000 loss alone made a restart impossible. The decision to wind down instead suggests the direct loss was only one part of the problem. The team must also verify the price-data dependency, review the affected vaults, and decide whether rebuilding the protocol safely and credibly still makes sense.

How Unreliable Price Data Makes a Vault Unsafe

An oracle supplies a smart contract with information it cannot obtain on its own, including asset prices. A vault can calculate every transaction correctly against the price it receives and still produce the wrong economic outcome if that price is unreliable. Oracle failures and price-feed manipulation are a long-standing attack class in DeFi, and many protocols mitigate the risk by cross-checking multiple independent feeds — a design question that is directly relevant when a single provider's compromise can propagate across every chain it serves.

Valid Onchain, Unsafe in Reality

A contract does not independently know the market price of an asset. It acts on the feed it has been programmed to accept. If that input becomes unreliable, an automated strategy can treat a transaction as valid onchain while users absorb the economic loss.

Full Sail's suspected oracle issue is technically different from the recent Term vault governance exploit. Both, however, show that DeFi contracts can treat a compromised input as legitimate and still harm users.

Full Sail linked its incident to Switchboard. In its official incident updates, Switchboard said it was investigating a potential compromise of its Move-based implementations and halted affected services on Aptos, Sui, IOTA, and Movement. The breadth of that halt illustrates the structural exposure: a single oracle provider cutting service across four Move-based chains means every downstream protocol on those chains had to reassess its price-data dependency at once. Neither team has published a complete technical postmortem, so the precise exploit path and final responsibility remain unconfirmed.

The App Is Paused; Withdrawal-Only Is the Next Stage

Full Sail's live security notice says deposits and withdrawals remain paused until oracle integrity is restored and verified. Its wind-down updates state that new deposits and liquidity-provider reward claims have been disabled, while regular pools are expected to become withdrawal-only after final security checks.

The app's banner reflects the current safety status. Withdrawal-only mode is the next planned stage, not a live function. Separate withdrawal and claim instructions are still pending. How quickly Switchboard completes its investigation and restores verified services on Sui will shape that timeline for any protocol that depended on it.

What Full Sail Still Needs to Publish

Full Sail has promised to put community depositors first. Users still need five practical answers before they can judge that promise:

1. The amount of protocol-owned liquidity available for repayment.
2. The total value of affected user claims.
3. The date used to calculate eligible balances.
4. The time when withdrawal-only pool access begins.
5. The claim process and the treatment of any shortfall.

Until that reconciliation is published, the $91,000 figure describes the breach — not what affected users will recover.

Sources: Full Sail (wind-down updates, live app), Switchboard (incident updates).