What happened?
Switchboard, an oracle provider (a service that supplies DeFi applications with asset prices from the outside world), announced that its contributors have paused deployments on four networks: Aptos, Sui, IOTA, and Movement. According to the company, the reason is reports of a possible compromise of its oracle in implementations written in the Move language. CryptoSlate reported on this.
An oracle is critical infrastructure for lending and derivatives protocols. If it delivers an incorrect or manipulated price, protocols that rely on it may settle positions incorrectly, trigger liquidations, or block withdrawals to prevent further losses.
Which applications are affected?
According to CryptoSlate, at least three applications have reported either losses, frozen funds, or precautionary access restrictions. Switchboard recommended that users temporarily switch to alternative price data sources.
The specific names of all affected protocols, the exact scope of the losses, and the total value locked were not clearly quantified in the available source. We therefore currently treat these figures as unknown.
Does this concern Solana too?
According to CryptoSlate, Switchboard stated that it has so far received no reports of similar problems with its implementation on Solana. However, this does not confirm that Solana is safe; it reflects the state of reports at a given moment, not the outcome of an audit.
What do we not yet know?
This is the point where honesty matters more than speed. As of the time this article was written, according to CryptoSlate, Switchboard had not published:
- the root cause of the incident (that is, exactly how the compromise occurred),
- a timeline for restoring the four deployments on Move chains,
- a complete and verified list of affected applications and the exact amount of damages.
The name of the incident refers to "Move" implementations, which is a layer shared by Aptos, Sui, IOTA, and Movement. Whether it was a bug in the oracle code itself, a compromise of contributor keys, or something else, is not evident from the available source.
Why the type of incident matters more than a one-off event
Charliedesk does not give advice on what to do. We describe what happened and what to watch in similar situations.
With oracle incidents, three things tend to be the decisive indicators: (1) whether the team publishes a verifiable root cause, (2) whether the affected protocols restore withdrawals or remain frozen, and (3) whether it is confirmed to have been an isolated problem of a single implementation or a systemic weakness in a shared layer. The difference between "paused as a precaution" and "funds permanently lost" is fundamental, and at this moment it is not clear for some of the applications.
How to verify this article later
The article keeps its own score. The following points will be verifiable over time based on official statements from Switchboard and the affected protocols:
| Question | Status today |
|---|---|
| Root cause published? | No |
| Deployments restored on Aptos, Sui, IOTA, Movement? | No |
| Confirmed scope of losses? | Unknown |
| Reports on the Solana implementation? | None so far |
As soon as Switchboard or the affected protocols publish a post mortem, we will add the facts and compare them with what was known today.