@Jonasoeth

This is Strategy's way of freeing itself from one of its biggest constraints and defusing the risk the market has always worried about. Instead of relying mainly on issuing new securities when mNAV is above 1, it now has multiple capital levers: USD reserves, buybacks, dividend management, and limited BTC monetization. More importantly, it signals that Strategy sees Digital Credit as a long-term asset class, backed by a full capital framework: • Liquidity management • Reserve policy • Dividend policy • Buybacks • Capital allocation If it works: STRC stays near par → lower cost of capital → cheaper funding to buy more BTC → a stronger self-reinforcing flywheel. Meanwhile, sUSDat is already offering juicy yields.

Over the past few years, multi-chain has become the default growth strategy for DeFi. Protocols expand to new blockchains to reach more users, lower transaction costs, and improve accessibility. But scaling across more chains has also introduced a "Structural Problem" Every new deployment typically comes with another vault, another liquidity pool, another accounting system, and another protocol state. The result is familiar → Liquidity becomes fragmented. Instead of one large pool serving every user, the same product is split across multiple isolated deployments. Each chain gradually develops its own TVL, liquidity profile, and sometimes even different yields. In other words, DeFi has solved distribution. It hasn't fully solved liquidity. ⤷ That raises an interesting question: Does multi-chain really require multiple vaults? Or can multiple chains simply access the same vault? ------------------------------ The newly proposed sGHO cross-chain architecture by TokenLogic explores exactly that idea. Instead of deploying independent ERC-4626 vaults across every Layer 2, the proposal keeps a single canonical vault on Ethereum. This vault remains the protocol's only source of truth. It holds the assets, calculates exchange rates, generates the Aave Savings Rate, and maintains the accounting for every sGHO position regardless of where the user enters the system. Layer 2s no longer operate separate savings vaults. Instead, they become entry points into the same vault. That architectural decision changes how liquidity is organized. From a user's perspective, the experience becomes significantly simpler. ------------------------------ Imagine holding GHO on Arbitrum. Previously, using sGHO required bridging assets to Ethereum, depositing into the vault, minting sGHO, and often bridging the receipt token back again. Every step added friction. Under the new design, users simply deposit GHO directly on Arbitrum. If Fast Path liquidity is available, they receive sGHO almost immediately without ever touching Ethereum. Everything feels native to the Layer 2. Behind the scenes, however, settlement still happens through Ethereum. Deposited GHO is periodically bridged to the canonical ERC-4626 vault via CCIP. The vault mints new sGHO, and fresh liquidity is bridged back to the Layer 2 to replenish the Fast Path inventory. Users experience instant execution. The protocol maintains unified accounting. If Fast Path liquidity is temporarily exhausted, deposits automatically follow the Slow Path. Assets are bridged directly to Ethereum, settled through the canonical vault, new sGHO is minted, and the resulting tokens are returned to the destination chain. Settlement takes longer, but the architectural principle never changes. Every deposit is ultimately backed by the same vault. This is why the proposal repeatedly emphasizes two ideas: One Source of Truth and No Fragmentation. There isn't one savings rate for Ethereum and another for Arbitrum. There isn't separate accounting for every deployment. Regardless of which Layer 2 users interact with, every position ultimately shares the same liquidity pool and the same Aave Savings Rate because every asset settles through the same underlying vault. ------------------------------ To me, that's the real innovation. The proposal isn't simply making sGHO available on more chains. It's demonstrating that multi-chain products no longer need to replicate their liquidity infrastructure on every chain. User interactions can be distributed and Liquidity doesn't have to be. If this architecture proves successful, it could represent a broader direction for DeFi. The next phase of multi-chain may not be defined by more deployments. It may be defined by more access points connected to the same underlying liquidity.

aggregation > replication

https://t.co/HkTnJw0uvY

One of the most interesting trends in BTCFi today is reducing reliance on custodians when bringing Bitcoin into DeFi. Instead of handing BTC over to a custodian, new primitives use cryptography to lock native BTC directly on the Bitcoin network and rely on mathematical proofs to create collateral on other chains. For many institutions, this model is attractive because it significantly reduces custodial risk and fits better with internal asset-management requirements. Some frameworks are also starting to offer potential legal and tax advantages. In other words, institutions are willing to accept a more complex user experience in exchange for maximum security and transparency. A few examples of projects building infrastructure around this idea: 1. @Stacks + Zest Protocol Using BitVM-based self-custodial vaults. BTC remains on Bitcoin L1 while users can borrow stablecoins on Stacks or EVM chains. 2. @SuiNetwork Hashi Uses a combination of 2-of-2 multisig and Threshold MPC to maximize security. BTC remains on Bitcoin L1 while collateral rights are represented and managed through smart contracts on Sui. 3. @babylonlabs_io Trustless Bitcoin Vaults + Aave V4 BTC is locked inside self-managed Taproot scripts. Users can mint restricted vaultBTC and use it as collateral on Aave without wrapping BTC or relying on a custodian. ------------------ The common theme across these projects is that they need strong institutional support from the very beginning, even during the devnet and testnet stages. Only institutions can provide the capital, credibility, compliance expertise, and infrastructure required for a native, trust-minimized Bitcoin model to work at scale. Sui Hashi may currently be one of the strongest examples of this approach. In a recent announcement, the project launched with more than 20 major partners, including Cumberland, Fluid, and SwissBorg. > Sui also benefits from a legal opinion provided by Fenwick & West stating that locking BTC in exchange for a receipt token is not considered a taxable event. My view is that Hashi is particularly well suited for institutions and builders looking to create complex financial products with strong compliance requirements. > Babylon also has institutional backing, although most of it has so far been focused on the Bitcoin staking side rather than the Bitcoin Vault product itself. That said, Babylon's biggest advantage today is its management of more than $5 billion worth of BTC staking, making it attractive for funds that want deep liquidity and access to Aave V4's unified liquidity model.