Sui DeFi protocol Full Sail winds down after Switchboard-linked oracle incident drains ~$91K
Switchboard halted its Move-based network on Aptos, Sui, IOTA and Movement while investigating a potential compromise.
Full Sail said it is winding down after a Switchboard-linked oracle security incident led to about $91,000 being removed from three automated vaults. The protocol has disabled new deposits and LP reward claims and says it will prioritize user repayment using remaining protocol-owned liquidity, with the team covering any shortfall.
Key Takeaways
- Full Sail said it is winding down operations after a security incident tied to oracle provider Switchboard resulted in user losses on Sui.
- About $91,000 was removed from three automated vaults, and the protocol has already disabled new deposits and LP reward claims.
- Switchboard halted its Move-based network on Aptos, Sui, IOTA and Movement while investigating a “potential compromise” of its Move implementations.
- Full Sail said it will use remaining protocol-owned liquidity to compensate users and cover any shortfall so “community depositors are repaid first,” with withdrawal and claim instructions expected “within the coming days.”
Full Sail Starts Wind-Down After Switchboard-Linked Oracle Incident Drains ~$91K
Full Sail, a DeFi protocol on Sui, said it is shutting down after a security incident involving oracle provider Switchboard led to user losses. The team framed the decision as a wind-down rather than a pause, a meaningful escalation from standard incident response.
The confirmed loss was about $91,000, removed from three of Full Sail’s vaults, the protocol said. Those vaults were described as automated vaults, meaning user deposits were managed by smart contracts running predefined strategies that can depend on external price inputs.
Full Sail linked the event to a “suspected compromise” of Switchboard’s oracle infrastructure. An oracle is the data feed layer that supplies off-chain or external inputs, like prices, to on-chain contracts. When that layer is questioned, the failure mode is not just one bad trade. It is contracts executing on bad assumptions.
The protocol said it first disclosed the incident on Saturday, when it confirmed a loss of funds and paused deposits and withdrawals while investigating. On Tuesday, Full Sail said it would wind down and made user repayment the priority, calling “compensating users the protocol’s top priority.”
What Users Can Do Now: Deposits Off, LP Rewards Frozen, Pools Headed to Withdrawal-Only
The operational posture is now defensive. Full Sail said it immediately disabled new deposits and liquidity provider reward claims.
That matters for anyone still exposed through vault positions or liquidity pools. LP reward claims are the mechanism for collecting incentives or fees earned for providing liquidity. Turning claims off is effectively a freeze on the “carry” that keeps many LP positions tolerable during uncertainty.
Full Sail also said regular pools will move to withdrawal-only mode after “final security checks.” Withdrawal-only is the tell that the protocol is prioritizing orderly exits over growth. It also implies the team wants to reduce state changes and strategy churn while it validates what is safe to reopen.
The missing piece is the exact process. Full Sail said it expects to publish withdrawal and claim instructions “within the coming days,” but it has not yet specified whether there will be snapshots, per-user limits, staged windows, or any claim contract mechanics. Until those details land, users are operating with a timeline but not a playbook.
Full Sail’s compensation plan is explicit but not quantified. The protocol said it will use remaining protocol-owned liquidity to compensate users, and the team will cover any shortfall so “community depositors are repaid first.” Protocol-owned liquidity is treasury-controlled liquidity rather than outside user funds. The commitment is real. The size of the backstop is still unknown.
Switchboard Halts Move-Based Network Across Aptos, Sui, IOTA and Movement
Switchboard said it was investigating a “potential compromise” of its Move-based implementations and halted its network on Aptos, Sui, IOTA and Movement. The language matters. “Potential” is not confirmation, and no exploit path has been publicly pinned down in the provided material.
Still, the response was broad. Halting across multiple Move-based chains is a blunt instrument, and it signals Switchboard treated the issue as shared-infrastructure risk rather than an isolated app bug. Move-based implementations refer to oracle components built using the Move programming language used by ecosystems like Sui and Aptos. If the same implementation pattern is deployed across chains, the threat model is correlated.
The second-order effect is downstream uncertainty. When an oracle network halts, protocols that depend on it can lose the ability to safely price collateral, rebalance vaults, or execute automated strategies. Some apps will fail “closed” by pausing. Others can fail “open” if assumptions were coded poorly.
One downstream disclosure is already on the tape. Virtue, a stablecoin lending protocol based on IOTA, separately reported about $455,000 in losses and said the backing of its VUSD stablecoin had been impaired. That is a different category of damage than a vault PnL hit. It touches collateral and redemption assumptions.
The Risk Map for Move-Ecosystem DeFi After an Oracle Disruption
Near term, the most actionable risk is access control. Full Sail has deposits disabled and LP reward claims frozen, and it has telegraphed a move to withdrawal-only after final checks. That combination limits user agency in two directions at once: capital can’t rotate in, and yield can’t be harvested out.
The broader Move-ecosystem read-through is counterparty concentration. Switchboard’s halt across Aptos, Sui, IOTA and Movement raises the probability of additional protocol updates, even if losses are not universal. The market does not need a dozen hacks to reprice oracle risk. It needs one shared dependency to be questioned.
The stablecoin angle is the part traders tend to underweight early. Virtue’s reported VUSD backing impairment suggests oracle-linked disruptions can leak into how protocols mark collateral and maintain backing. If more disclosures look like that, the risk shifts from “one protocol got hit” to “assumptions across lending and stablecoin stacks need re-auditing.”
The timeline catalyst is simple but binary. Full Sail said withdrawal and claim instructions are coming “within the coming days,” and Switchboard has not provided a restoration timeline in the provided material. Until both are clarified, the ecosystem is trading on incomplete information.
My Take: Why This Looks Like an Oracle Counterparty Shock, Not a Single-Protocol Blowup
The threshold that matters is not the ~$91,000. It is the decision to wind down. When a team moves from pausing to shutting down, it is usually because the trust and operational costs of continuing exceed the expected value of rebuilding.
The real test is whether the backstop is measurable. Full Sail has promised protocol-owned liquidity plus team coverage so “community depositors are repaid first,” but the market still lacks the key variable: remaining liquidity versus total claims once withdrawals and claims are defined. If those instructions land cleanly and the pool state flips to withdrawal-only without more surprises, this becomes a contained oracle counterparty shock rather than a cascading Move-ecosystem unwind.
