Sky: USDS Cross-Chain Bridging on Solana Resumes After Security Review

On May 11, 2026 (14:01 UTC), Sky Governance executed an on-chain action to unpause the USDS SkyLink / LayerZero OFT route between Ethereum and Solana, restoring cross-chain transfers with updated guardrails. You can verify the execution and parameters directly via the official governance spell details in Sky’s voting portal.

This reopening follows a temporary, preventive pause triggered by the broader ecosystem’s review of the rsETH cross-chain incident—a reminder that, in 2026, interoperability is still one of the highest-leverage risk surfaces in DeFi.

What exactly reopened (and what changed)

The May 11 execution re-enabled USDS bridging on the Ethereum ↔ Solana path and applied new rate-limit settings. The governance spell explicitly sets daily inbound and outbound limits of 5,000,000 USDS for Solana, then unpauses the relevant contracts/programs to resume normal transfers. (Reference: Sky Governance executive proposal “Unpause Solana SkyLink Bridge…”.)

For builders and power users who want the deeper technical scope (including contract addresses, EIDs, and sequencing), Sky’s forum post walks through the full unpause plan and checks. (Reference: “Technical Scope: Unpausing the LayerZero Solana Bridge”.)

• Governance execution details (on-chain): Sky Governance executive proposal — Unpause Solana SkyLink Bridge (Executed May 11, 2026)
• Engineering scope & verification steps: Technical Scope: Unpausing the LayerZero Solana Bridge
• Bridge mechanics overview (developer docs): USDS Ethereum–Solana Bridge (Sky Protocol Docs)

Why the pause happened: the rsETH incident and “bridge-config risk”

The pause wasn’t triggered by a direct compromise of Sky Protocol. Instead, it was a risk-control decision taken while the industry investigated the rsETH-related exploit path and potential contagion channels.

If you missed it: in mid-April 2026, KelpDAO’s rsETH suffered a major exploit linked to its cross-chain setup. Two high-signal reads on the incident are:

• LayerZero’s statement on the incident and its security model assumptions: KelpDAO Incident Statement (LayerZero)
• A transaction- and behavior-level breakdown: Inside the KelpDAO Bridge Exploit (Chainalysis)

For everyday users, the key takeaway is simple: a bridge is not “just a transport layer.” Verification choices, rate limits, pausability, and operational procedures can be as important as the token contract itself—especially for stablecoin liquidity that routinely moves between ecosystems.

If you want background on the standard Sky uses here, LayerZero’s docs explain how an Omnichain Fungible Token (OFT) maintains a unified supply across networks (and what that implies for trust boundaries and delivery). See: OFT technical reference (LayerZero docs).

“Was USDS affected?” Collateralization and on-chain verifiability

During the review window, Sky stated that the core protocol and USDS contracts were not impacted, and that USDS remains aligned with the system’s design assumptions—namely, that backing and key accounting components can be inspected on-chain.

For readers who want a practical overview of how USDS collateral and transparency are commonly described (Vaults, PSM-style mechanisms, and what is / isn’t trust-minimized), this explainer is a helpful starting point: Inside Sky: DAI and USDS Architecture.

What’s the status for Avalanche?

Solana bridging is reopened; however, the unpause scope published by Sky’s engineers explicitly notes that the Avalanche USDS OFT remained paused at the time of the Solana unpause, and the spell design sets the Ethereum → Avalanche outbound rate limit to 0 while that remains the case. See the section describing Avalanche status in the technical scope write-up: Technical Scope: Unpausing the LayerZero Solana Bridge.

In practice, this means users should treat the Avalanche path as not fully reopened until Sky publishes a separate confirmation (and/or governance execution) for that route.

User checklist: bridging USDS more safely after a pause

Whether you’re a DeFi user, a treasury operator, or a Solana-native trader moving stablecoin liquidity, post-pause periods are when mistakes happen. A quick checklist:

1. Verify the official route and status before sending funds
   Use Sky’s official documentation and governance references, not third-party “bridge aggregators” that can surface spoofed assets.

2. Expect parameter changes like rate limits and windows
   Rate limits can affect large transfers, batching, and settlement timing—especially when liquidity is returning after a security review.

3. Start with a small test transfer
   This is still one of the most effective ways to reduce operational risk during restarts.

4. Lock down approvals
   Avoid unlimited allowances where possible, and revoke permissions you no longer need.

Where OneKey fits: self-custody during cross-chain operations

Cross-chain transfers are high-impact transactions: a wrong destination address, a malicious dApp, or a fake token page can turn into irreversible loss. Using a hardware wallet like OneKey helps keep private keys isolated while you verify transaction prompts on a secure device—particularly valuable when users are rushing to move stablecoins right after bridging resumes.

If your workflow includes frequent bridging, consider setting up a dedicated account for cross-chain activity, using strict allowances, and treating every “bridge UI” as untrusted until you’ve confirmed it against the protocol’s official docs and governance records.