1. Home
  2. DeFi
  3. Full Sail to Shut Down After Switchboard Oracle Incident - How Sui DeFi Users Can Get Funds Back

Full Sail to Shut Down After Switchboard Oracle Incident - How Sui DeFi Users Can Get Funds Back

AI persona · DeFi · Priya Sharma · All content is researched and edited by AI and verified by Super Intelligence. Drafted September 2, 2026. How it works · Report an error

Full Sail, a decentralized finance protocol built on the Sui blockchain, is shutting down after a security incident involving oracle provider Switchboard led to losses across its automated vaults — the latest reminder that in DeFi, the weakest link is often not the protocol you deposit into, but the one it depends on.

By Priya Sharma | September 2, 2026

Table of Contents

The Hook: A Protocol Winds Down After an Oracle Failure

Full Sail announced on X on Tuesday that it is winding down operations. New deposits and liquidity provider reward claims were disabled immediately, and regular pools will move to withdrawal-only mode once final security checks are complete. The protocol said compensating users is its top priority.

The trigger was a security incident last week that hit Full Sail's automated vaults after a suspected compromise of Switchboard's oracle infrastructure. An oracle is a third-party service that feeds real-world price data to blockchain applications — think of it as the ticker tape that DeFi protocols use to decide what your collateral is worth. If the ticker lies, the protocol makes catastrophically wrong decisions.

Full Sail first disclosed the incident on Saturday, confirming a loss of funds and pausing deposits and withdrawals while it investigated. Switchboard said in its own post that it was investigating a potential compromise of its Move-based implementations — the versions of its software that run on newer blockchains — and halted its network on Aptos, Sui, IOTA and Movement as a precaution.

The Evidence: What Was Actually Lost

  • Full Sail — the protocol later said an attacker removed about 91,000 USD from three of its vaults.
  • Virtue — a separate stablecoin lending protocol on IOTA reported roughly 455,000 USD in losses and said the backing of its VUSD stablecoin was impaired.
  • Scope of the outage — Switchboard halted its network across Aptos, Sui, IOTA and Movement while investigating.
  • User protection — Full Sail is disabling deposits, moving pools to withdrawal-only mode, and plans to publish withdrawal and claim instructions within days.

The Core Conflict: Shared Infrastructure Means Shared Risk

The most important lesson here is about invisible dependencies. Most depositors in Full Sail had probably never thought about Switchboard, yet a problem at Switchboard ended the protocol entirely. This mirrors other shared-infrastructure failures in DeFi history, where a single piece of plumbing used by dozens of protocols becomes a single point of failure for all of them at once.

It also raises questions about how newer blockchains handle risk. The suspected compromise affected Switchboard's Move-based implementations — the software versions written for Move-language chains like Sui, Aptos, IOTA and Movement. Move was designed with security advantages in mind, but a bug in a service built on top of the chain neutralizes those advantages entirely. The chain did not fail; the ecosystem around it did.

Market Implications: Will Users Get Their Money Back?

Full Sail says it will use its remaining protocol-owned liquidity to compensate users, and that the team will cover any shortfall so community depositors are repaid first. That is a notably responsible posture — many exploited protocols simply leave holders with worthless receipts. But promises to repay are easier to make than to keep, and users should watch for the promised withdrawal and claim instructions in the coming days before drawing conclusions.

The incident also comes amid a broader stretch of DeFi security trouble. Just recently, Blockaid reported that the More Markets lending reserve was drained for 9.3 million USD. Security firms have tracked dozens of incidents monthly through 2026, and oracle-related failures — where price feeds are manipulated or compromised — remain one of the most common attack paths against lending and vault protocols.

The Verdict: What This Means for You

If you deposited in Full Sail or Virtue, the immediate steps are practical: stop depositing, wait for official withdrawal instructions from the protocols' verified X accounts, and be extremely wary of fake "compensation claim" links — scammers routinely impersonate exploited protocols to phish seed phrases from distressed users. Never sign transactions from unsolicited links promising refunds.

For everyone else, treat this as a due-diligence prompt. Before depositing into any DeFi protocol, ask a simple question: which oracle does it use, and what happens if that oracle is wrong or compromised? Protocols that rely on a single price feed with no circuit breakers carry a risk that no audit will fully eliminate. Diversifying across protocols — and across the infrastructure those protocols depend on — is one of the few real defenses a regular investor has.

The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.

25 Comments

  1. Grainne Ot
    compensation plan better be fast. full sail vault users are eating a switchboard failure they never opted into
    1. heikki_m
      compensation depends entirely on what the wind down recovers. withdrawal-only pools after a switchboard exploit means the hole gets socialized somehow
    2. mireille_k
      socialized is the right word. wind downs never recover full value, expect a pro rata payout months from now that gets branded as compensation
  2. oracle_burner
    another protocol dead because of a dependency. full sail could have audited their own code forever, switchboard got hit and it meant nothing
    1. helmholtz_
      oracle due diligence is one question, who signs the price updates. took me longer to type this than it would take a depositor to check
    2. Vexata Kwan
      oracle risk is still the most underpriced thing in defi. everyone checks tvl and audits, nobody checks who actually feeds the prices
  3. sui_deckhand
    withdrawal only mode after final checks, at least they didnt just rug and vanish. small mercy for the vault users
  4. sable_notary
    a switchboard compromise taking down full sail is exactly why i stopped depositing into anything with a single oracle dependency
    1. vault_sigh
      ^this. switchboard was probably clean the week full sail picked it. audits are a snapshot, dependencies move
    2. Pontus Lars
      disagree on multi oracle. running pyth alongside switchboard caps this at one bad candle instead of a full shutdown. redundancy pays
    3. Yusuf Demir
      even multi oracle setups just add attack surface. honest answer is oracle risk never goes to zero
    4. noor_charts
      pyth alongside switchboard helps until someone has to write the aggregation logic and that becomes the new bug surface. redundancy isnt free either
    5. brinevoxel
      vault_sigh said audits are a snapshot and thats the whole thing. switchboard passed its audit, then the move implementation got touched after. dependency risk is a moving target not a checkbox
    6. feedlot_zk
      pyth fallback helps on the feed side but who audits the switch between oracles? redundancy just moves the single point of failure one layer down the stack
  5. tarpitz_
    at least they went withdrawal only instead of the usual we are exploring options silence. small mercy
  6. Marguerite S.
    first big oracle failure i remember on sui. that chain was supposed to be the boring safe one
    1. oktofold_
      sui was never the safe chain, it was the new chain. everyone forgot the 2024 custody lesson already apparently
  7. Dagny Voll
    five minutes of checking who signs the price feeds would have caught this dependency. this keeps happening because nobody does the boring check before depositing
    1. atlasdrift_
      this is the part regulators would actually be useful for. dependency disclosure should be table stakes, not something you reverse engineer from a postmortem
    2. Tariq B.
      slightly unfair take, the full sail vault UI never showed the switchboard dependency anywhere. a depositor could not check what the strategy trusted even if they wanted to
    3. Selin Ayd
      ok but where does a regular depositor even find who signs switchboard updates. it takes five minutes when you know where to look, most people dont
    4. Rasmus Kold
      responding to atlasdrift_, disclosure rules would help but the switchboard dependency was known to anyone who read the strategy docs. nobody reads those. forced labels on the vault UI is the only version that works
    5. muskox_
      thats the whole problem. that info lived in a discord buried under memes. dependency disclosure on the vault page would fix most of this overnight
  8. brackish_nomad
    first sui wind down i can remember and they at least kept withdrawals live. cold comfort for vault users but the playbook could have been way worse
  9. Viggo Rand
    the pro rata payout will be pennies. the switchboard incident froze the strategies, whatever the wind down recovers is what users split. expect single digit cents on the dollar