Spark

Powering DeFi with billions in liquidity. Earn and borrow with competitive rates, seamless access, & scalable liquidity.

Institutional-grade DeFi for everyone.

[Spark @sparkdotfi]

Inside Spark’s loss absorption & risk frameworks.

Spark’s security architecture is designed around:
• bounded capital movement
• explicit loss absorption layers
• coordinated liquidity management
• multi-layered oracle systems
• constrained automation under governance-defined limits

This deep dive breaks down how Spark structures risk, liquidity, and loss absorption across Spark Savings, SparkLend, and the Spark Liquidity Layer before losses propagate toward user deposits.

Including:
• updated loss absorption waterfall
• Prime Agent risk capital
• Genesis Capital Backstop
• oracle and killswitch architecture
• programmatic liquidity coordination
• constrained allocation design under stress

Security by design.
Resilience by architecture.

See what sits between losses and user deposits: https://t.co/JQrfSxMB4z

[Spark @sparkdotfi]

Spark x Bitgo Podcast | Special Edition https://t.co/zXN72TG4st

[Spark @sparkdotfi]

Reminder: happening today!

[Spark @sparkdotfi]

Podcast: Join Sam @hexonaut and Michael Wei @noweiitsmichael this Friday for a live AMA on Spark's integration with @BitGo.

Learn how institutional capital can move from custody into on-chain credit markets through structured allocation.

Join us this Friday.

[Spark @sparkdotfi]

Holding wstETH? SparkLend may be the most efficient place to put it to work.

SparkLend holds more wstETH than any venue in DeFi.

Most lending markets treat LSTs and restaking assets as a diversified basket. In stress, they're not. They share the same ETH exit path.

SparkLend's wstETH market doesn't average across that basket. Parameters reflect wstETH's behavior specifically, not a blended risk profile across correlated exposures.

What that means for you:

Oracle pricing is fundamental, so short-term spot dislocations don't put your collateral at risk.

Rate conditions below the kink stay predictable as the market scales.

Efficiency mode stays focused, no complexity creep from an expanding collateral set.

Your wstETH can work harder here.

→ Borrow against your wstETH on SparkLend: https://t.co/Utr5mW98Yo

[monetsupply.eth @MonetSupply]

Come join us next week 🙏 should be a great conversation!

[Spark @sparkdotfi]

Spark Prime is built for institutional crypto borrowers like @Anchorage and integrations with @redstone_defi are one of the many vital components that make it work.

[RedStone ♦️ @redstone_defi]

RedStone now provides live LTV feeds for @sparkdotfi's collateral positions inside @Anchorage.

Spark's $BTC collateral sits in a regulated custodian, not onchain. RedStone allows the data from those positions to be tracked in real time.

[Spark @sparkdotfi]

@turtledotxyz ⚡️x 🐢

[Spark @sparkdotfi]

@untanglingweb3 ⚡️

[Spark @sparkdotfi]

https://t.co/xwwoNcET6H

[Spark @sparkdotfi]

Podcast: Join Sam @hexonaut and Michael Wei @noweiitsmichael this Friday for a live AMA on Spark's integration with @BitGo.

Learn how institutional capital can move from custody into on-chain credit markets through structured allocation.

Join us this Friday.

[Spark @sparkdotfi]

Automation creates value only when its range of motion is bounded.

Liquidity orchestration faces exactly this design problem. Capital needs to move quickly across venues, but speed should never become unbounded exposure.

Spark Liquidity Layer handles it through governance-defined constraints.

Approved venues define where capital can move. Allocation limits and rate limits define how much can move, and how quickly. Min/max inventory bands cap how much can sit in any single venue.

The automation layer still monitors, rebalances, and executes, all inside constraints already in force before execution begins.

That is the security property. Even if automation is compromised, capital movement stays bounded.

For institutional liquidity infrastructure, automation is not the trust assumption. The constraint system is.

Read the full security framework here:
https://t.co/vKZpQfxsxg

[Spark @sparkdotfi]

@TheDeFiAngel Overcollateralized lending has earned its place, but the RWA credit stack is where the real infrastructure build is happening. Watch this space closely.

[Spark @sparkdotfi]

Spark Savings is now native inside @Rabby_io ⚡️
️
This is more than an integration.

It’s a glimpse of where wallets are going: from holding assets → helping users put idle capital to work safely, instantly, and without leaving the wallet.

With Spark x Rabby, users can now earn on USDS, USDC, USDT, and ETH directly inside Rabby.

No bridges.
No extra steps.
No fragmented UX.

For Rabby users, this means idle assets can now earn directly from the wallet they already trust.

This trust is now reinforced by the Spark Savings Risk Framework, with its risk absorption layers which means SAFETY FIRST + INSTANT REDEMPTION.

[Spark @sparkdotfi]

@stablewatchHQ @SkyEcosystem @circle @Securitize @aave @ethereum @OndoFinance @ethena @SuperstateInc @maplefinance 🙌

[Spark @sparkdotfi]

One of the hardest problems in credit markets is balancing liquidity and deployment.

Hold too much capital in reserve and returns suffer.
Deploy too much capital and liquidity suffers.

Spark's Liquidity Layer holds $1.11B of USDT across two roles.

$571M sits as plain USDT in the ALM proxy. That's the idle liquidity buffer. Most withdrawals clear instantly against it. Larger exits go through a request flow.

$545M is deployed into SparkLend's USDT pool as spUSDT, earning the benchmark rate.

Same asset, two different jobs. The split is what lets Spark Savings USDT offer real liquidity depth and a competitive return at the same time.

Deposit USDT: https://t.co/gDFdimF53s

[Sam MacPherson @hexonaut]

While Mythos is changing the security threat model in some ways, I am not particularly concerned about exploits being found in blue-chip smart contracts.

If the code base is small and important enough (most SC code is), then traditional methods are sufficient to achieve high confidence in security.

What's changing is the cost of searching for exploits in large codebases. These bugs were always there, but we are compressing the time to discover them.

This is largely what is driving the recent infrastructure compromises affecting everyone. With smart contracts, this can be protected against using rate limits and timelocks, limiting the damage that can be done if an off-chain system is hacked.

Overall, this is a period of understandable apprehension, but I'm confident that by following best practises we can make it to the other side stronger than before.

[Spark @sparkdotfi]

@duonine The flow of institutional capital into yield bearing DeFi just became simple! ⚡️

[Spark @sparkdotfi]

@Narvalgmi ⚡️🐋

[Spark @sparkdotfi]

https://t.co/jAr7MYl8WW

[Spark @sparkdotfi]

@BitGo @Narvalgmi @aave @tesseractcrypto 🤝

[Spark @sparkdotfi]

@BitGo @Narvalgmi @aave @tesseractcrypto Institutional DeFi done right!