How To Check Sparklend USDS And Sky USDS For Shared Risk

What You Will Verify

When Sparklend USDS jumps 1.64pp to 5.05% on $954M TVL in the same week Sky STUSDS jumps 5.63pp, you need to determine whether deploying to both venues diversifies your protocol risk or concentrates it. Most yield aggregators treat them as separate positions. The blockchain shows otherwise.

This article walks through the on-chain verification protocol to determine whether SparkLend USDS deposits and Sky Protocol sUSDS or stUSDS holdings share the same underlying surplus buffer, governance mechanism, and collateral pools. You will trace contract dependencies, revenue flows, and governance execution paths. By the end, you will know whether a $200,000 allocation split between both venues represents diversification or single-protocol concentration.

You need basic familiarity with Etherscan and the ability to read governance proposals. You do not need to write code.

Why This Matters For Income

The specific income risk is false diversification. If you deploy $100,000 to SparkLend USDS at 5.05% and $100,000 to Sky sUSDS at 3.80%, you expect $8,850 annually across two independent venues. If both draw from the same Sky Protocol surplus buffer, a single governance vote affecting the Sky Savings Rate will change both rates simultaneously. A single collateral failure will propagate to both positions. You have not diversified protocol risk. You have concentrated it.

The spread between SparkLend USDS borrowing rate (4.27%) and the Sky Savings Rate (3.80%) is 47 basis points. That spread exists because SparkLend funnels approximately 10% of its revenue into the Sky surplus buffer that funds sUSDS yield. You are paying SparkLend's margin on one side and receiving Sky's base rate on the other, while exposing the same capital to identical protocol governance and collateral pools.

On $200,000 deployed, distinguishing genuine diversification from shared-protocol exposure determines whether you survive a governance attack, collateral depeg, or smart contract exploit with 50% of capital intact or 0%.

Step 1: Verify SparkLend Revenue Flows Into Sky Surplus Buffer

Start at the Sky Protocol developer documentation on rate mechanisms. The Sky Savings Rate is funded by protocol surplus, which accumulates from three primary sources: stability fees on CDP-minted USDS, returns on real-world asset collateral, and allocations from Spark Protocol revenue. The Spark allocation comprises approximately 10% of Sky Savings Rate funding.

Navigate to the Sky stUSDS module documentation. The stUSDS rate formula is: stUSDS Rate = Utilization × (SKY Borrow Rate - stUSDS Accessibility Reward) + (1 - Utilization) × Sky Savings Rate. This confirms stUSDS yield depends directly on the Sky Savings Rate when utilization is low, and on SKY-backed borrowing when utilization rises. Both funding sources are internal to Sky Protocol governance.

Cross-reference this with SparkLend's position as Sky's dedicated lending arm. Spark Protocol operates as a fork of Aave V3 and holds approximately $5.29 billion in supplied assets. The Spark Liquidity Layer allocations into SparkLend reached $1.58B at Q3 2026 quarter-end, with USDS allocations rising to $920M. These allocations generate revenue that flows back into the Sky surplus buffer.

The verification is complete when you confirm SparkLend is not an independent protocol. It is a revenue-generating module within the Sky ecosystem, and its USDS yield is set by the same governance mechanism that controls sUSDS and stUSDS rates.

Step 2: Trace Governance Execution Across Both Venues

Sky Protocol governance sets the Sky Savings Rate through Executive Votes. These votes adjust the DSR (now SSR) by modifying the rate accumulator contract. When Sky governance votes to change the SSR from 6.5% to 3.75%, as occurred in early 2025, that change propagates to three places simultaneously: sUSDS redemption value growth, stUSDS base rate (when utilization is below 100%), and SparkLend USDS supply rates.

To verify this on-chain, identify a recent Sky governance proposal that adjusted the SSR. Note the block height and timestamp of execution. Then check SparkLend's USDS supply rate at the same block height. The rate change should appear within the same block or within minutes, depending on when SparkLend's rate oracle updated.

If you see a SparkLend USDS rate jump that occurs within hours of a Sky governance vote execution, you have confirmed shared governance dependency. A single DAO vote affects both venues. A governance attack, quorum failure, or malicious proposal impacts your entire allocation, not half of it.

Step 3: Check Collateral Pool Overlap And Peg Mechanisms

USDS peg stability is backstopped by the PSM (Peg Stability Module) at parity with USDC. This creates secondary risk: if USDC depegs, USDS peg risk propagates instantly to both SparkLend USDS deposits and Sky sUSDS holdings. You cannot isolate exposure by splitting between venues when both rely on the same collateral backstop.

Verify this by locating the USDS token implementation contract and the USDS Join contract, which mints and burns USDS against VAT internal balances. The PSM holds USDC reserves that allow 1:1 redemption. Any USDC depeg event will trigger withdrawal pressure on both SparkLend USDS and sUSDS simultaneously, because both are claims on the same underlying collateral pool.

Additionally, check real-world asset allocations within Sky Protocol. If Sky holds tokenized Treasury bills or corporate debt as collateral, a default or liquidity freeze in those assets reduces the surplus buffer that funds both sUSDS yield and supports SparkLend's rate-setting capacity. Shared collateral means shared failure modes.

Step 4: Analyze Smart Contract Upgrade Paths

The Sky savings module contracts are forks of the original Maker DSR. The USDS migration introduced new code surface, audited by Spearbit and ChainSecurity. Both SparkLend USDS and sUSDS rely on this shared contract infrastructure for minting, burning, and rate accumulation.

A critical bug in the pot contract or rate accumulator affects both venues simultaneously. You can verify this by checking the contract addresses for SparkLend's USDS token integration and comparing them to the sUSDS contract. If they reference the same token implementation and join contracts, they share smart contract risk.

Sky Protocol governance controls upgrade authority for these contracts. A malicious or buggy upgrade proposal that passes governance will deploy to both SparkLend and sUSDS infrastructure at once. You cannot isolate smart contract risk by holding both.

Step 5: Monitor TVL And Utilization Correlation

Track TVL movements across both venues. DefiLlama shows SparkLend USDS at approximately $1.156B TVL with 2.89% APY, while Sky Lending Savings Module holds $3.785B in sUSDS. When Sky Savings Rate changes, you should observe correlated TVL flows between SparkLend USDS and sUSDS within 24-48 hours.

If a governance vote raises the SSR, rational actors will shift capital from lower-yielding venues into sUSDS. If the vote raises SparkLend borrowing rates, capital may flow out of SparkLend USDS into direct sUSDS holdings to capture the higher base rate without paying SparkLend's spread. Correlated TVL movements confirm shared rate dependency.

You can also monitor utilization rate on SparkLend USDS. SparkLend's rate is set by governance, not utilization, but utilization impacts protocol revenue and thus the surplus buffer funding sUSDS. If SparkLend utilization collapses, Spark revenue declines, and the 10% allocation into Sky surplus weakens, reducing sUSDS yield sustainability over time.

Common Failure Modes

The most common mistake is assuming interface separation implies protocol separation. SparkLend and Sky Protocol present different user interfaces, different branding, and different rate displays. The underlying contracts and governance are identical.

Another failure mode is ignoring governance quorum risk. Sky Protocol governance requires quorum for Executive Votes. If quorum drops during a period of low engagement, a small number of MKR holders can pass proposals that affect both SparkLend and sUSDS rates. Your $200,000 allocation is exposed to the same governance attack surface twice, not diversified across two independent DAOs.

Third, users often overlook stUSDS utilization spikes. The stUSDS rate formula shows that when utilization rises, the rate depends on SKY-backed borrowing activity rather than the base SSR. If you hold stUSDS assuming it tracks the SSR, a sudden utilization spike will change your yield source from stable DSR accumulation to volatile borrowing demand. This affects stUSDS but not sUSDS, creating temporary divergence that masks the underlying shared protocol risk.

Finally, many allocators do not monitor Sky surplus buffer health. If Sky's RWA collateral underperforms or CDP liquidation cascades drain the surplus, both SparkLend and sUSDS rates will compress simultaneously. The surplus buffer is the shared funding source. When it shrinks, both venues adjust rates downward within the same governance cycle.

What The Data Shows

SparkLend USDS borrowing rate is 4.27%, while the current Sky Savings Rate on sUSDS is 3.80%. The 47 basis point spread represents SparkLend's operational margin and risk buffer. On $100,000 deployed, that spread costs you $470 annually if you choose SparkLend over direct sUSDS.

However, SparkLend USDS lending rates have shown higher yields than sUSDS in certain market conditions, reaching approximately 4.2% APY on $559.72M TVL while sUSDS held at 3.80%. This occurs when SparkLend's utilization-based incentives or liquidity layer allocations create temporary rate lifts above the base SSR. These lifts are governance-approved and still dependent on the same surplus buffer.

The Q3 2026 data shows Spark Liquidity Layer allocations into SparkLend reached $1.58B, with USDS allocations at $920M. This represents significant capital concentration within a single protocol ecosystem. If you deploy to both SparkLend USDS and sUSDS, you are adding to that concentration, not diversifying away from it.

Practical Verification Checklist

Run through this checklist before treating SparkLend USDS and Sky sUSDS as independent positions:

• Confirm SparkLend revenue allocation to Sky surplus buffer (currently ~10%)
• Identify the most recent Sky governance vote affecting SSR and verify SparkLend rate changed within the same 24-hour window
• Check USDS token implementation contract and verify both SparkLend and sUSDS reference the same minting and join contracts
• Review PSM collateral composition and confirm both venues rely on USDC peg stability
• Monitor Sky surplus buffer balance and compare to combined TVL across SparkLend USDS and sUSDS
• Track governance quorum trends to assess attack surface for rate manipulation

If all six points confirm shared dependencies, you are not diversifying. You are concentrating protocol risk while paying SparkLend's spread on one leg of the position.

How To Decide

The decision framework is straightforward. If your goal is protocol diversification, SparkLend USDS and Sky sUSDS do not qualify as independent venues. Deploy to one or the other based on rate, but do not split capital between them expecting isolated risk.

If your goal is to capture the highest available rate within the Sky ecosystem, compare SparkLend USDS supply rate against sUSDS and stUSDS. When SparkLend offers a premium over sUSDS due to liquidity layer incentives, the premium compensates for slightly higher smart contract surface area (Aave V3 fork plus Sky integration). When sUSDS offers a higher rate, the simplicity of direct DSR exposure may justify the choice.

For stUSDS, the rate formula introduces utilization-based volatility. If you can tolerate rate swings tied to SKY-backed borrowing demand, stUSDS may offer higher yields during high-utilization periods. But that yield is still funded by Sky Protocol surplus and governed by the same DAO votes that control sUSDS and SparkLend rates.

On a $200,000 allocation, the difference between genuine diversification and shared-protocol concentration is the difference between losing $100,000 in a governance exploit and losing $200,000. The on-chain verification takes less than two hours. The cost of skipping it is total capital exposure to a single point of failure.

What To Monitor After Deployment

If you choose to deploy to either SparkLend USDS or Sky sUSDS (or both, accepting shared risk), monitor these on-chain signals:

• Sky governance proposals affecting SSR, with special attention to quorum levels and voting participation
• Sky surplus buffer balance, available via Sky Protocol dashboard or on-chain query
• SparkLend revenue contribution to Sky surplus, which should remain around 10% of total funding
• USDC PSM reserves, which backstop USDS peg stability
• Utilization rate on stUSDS if you hold that token, as utilization above 80% shifts yield dependence from SSR to SKY borrowing demand
• TVL correlation between SparkLend USDS and sUSDS following governance votes, confirming shared rate sensitivity

Set alerts for Sky Executive Votes that propose SSR changes. These votes typically execute within 48 hours of passing, and rate changes propagate to both venues immediately. If you see a vote proposing an SSR reduction from 3.80% to 2.50%, you have less than two days to decide whether to exit before the rate cut applies to your entire position.

Alternative Diversification Options

If genuine protocol diversification is your goal, compare Sky ecosystem yields against independent stablecoin venues. Stablecoin income strategies for 2026 include Aave USDC, Compound USDT, and Curve stablecoin pools, each with independent governance, collateral, and rate-setting mechanisms.

For example, deploying $100,000 to Sky sUSDS at 3.80% and $100,000 to Aave USDC at a competitive rate diversifies protocol risk across two DAOs, two governance attack surfaces, and two collateral systems. A Sky governance exploit affects half your position. An Aave oracle failure affects the other half. You have isolated risk.

Deploying $100,000 to SparkLend USDS at 5.05% and $100,000 to Sky sUSDS at 3.80% exposes both to the same governance votes, the same surplus buffer, and the same USDC PSM backstop. A Sky governance exploit affects 100% of your position. You have not isolated risk.

The rate difference between venues does not compensate for concentration if you are seeking diversification. If you are seeking maximum yield within the Sky ecosystem, accept the shared risk and choose the highest-rate venue. Do not pretend you are doing both.

The Takeaway

SparkLend USDS and Sky sUSDS share the same Sky Protocol governance, the same surplus buffer funding source, the same USDC PSM collateral backstop, and the same smart contract upgrade path. Deploying to both concentrates protocol risk rather than diversifying it. You can verify this in under two hours by tracing revenue flows, governance execution, and contract dependencies on-chain. On $200,000 deployed, the difference between shared-protocol concentration and genuine diversification is the difference between single-point-of-failure exposure and isolated risk. The blockchain shows you which one you have. You just have to look.

Frequently Asked Questions

Do SparkLend USDS and Sky sUSDS share the same protocol risk?

Yes. SparkLend operates as Sky Protocol's dedicated lending arm and contributes approximately 10% of revenue to the Sky surplus buffer that funds sUSDS yield. Both are governed by Sky DAO Executive Votes, rely on the same USDC PSM collateral backstop, and share smart contract infrastructure. A governance attack, collateral failure, or contract exploit affects both venues simultaneously. Deploying to both concentrates rather than diversifies protocol risk.

Why does SparkLend USDS rate differ from Sky sUSDS rate?

SparkLend USDS borrowing rate is set by Sky governance but includes a spread above the base Sky Savings Rate to cover SparkLend's operational costs and risk buffer. Currently, SparkLend USDS borrowing is 4.27% while sUSDS pays 3.80%, a 47 basis point difference. SparkLend supply rates can exceed sUSDS when liquidity layer incentives or governance adjustments create temporary premiums, but both rates respond to the same underlying Sky governance votes.

How do I verify SparkLend and Sky share governance on-chain?

Identify a recent Sky Executive Vote that changed the Sky Savings Rate. Note the block height and timestamp of execution. Then check SparkLend USDS supply rate changes within the same 24-hour window. If SparkLend rates adjust simultaneously with sUSDS following a Sky governance vote, you have confirmed shared governance dependency. Both venues respond to the same DAO proposals, meaning a single vote affects your entire allocation across both.

What happens if USDC depegs while I hold SparkLend USDS and sUSDS?

Both positions are exposed simultaneously. USDS peg stability is backstopped by the PSM at parity with USDC. If USDC depegs, USDS faces immediate peg pressure, triggering withdrawal demand across all USDS venues including SparkLend and sUSDS. Because both rely on the same USDC collateral reserves, you cannot isolate this risk by splitting your allocation. A USDC depeg event affects 100% of your capital, not 50%.

Should I split $200k between SparkLend USDS and Sky sUSDS for diversification?

No, if your goal is protocol diversification. Both share Sky Protocol governance, surplus buffer funding, USDC collateral backstop, and smart contract infrastructure. Splitting between them concentrates single-protocol risk while paying SparkLend's rate spread. For genuine diversification, deploy to independent stablecoin venues like Aave USDC or Compound USDT alongside one Sky ecosystem position. If maximizing Sky ecosystem yield is your goal, choose the highest-rate venue and accept the shared risk.