DeFi
In-depth research, opinions, and analysis of DeFi trends.
Maya Protocol Hack Halts Network After $1.4M Bitcoin Theft
<p>Maya Protocol globally halted its network on August 19, 2026, after founder AaluxxMyth said the cross-chain protocol had likely been exploited for around 20 BTC, worth roughly $1. 4 million, in an incident that security researchers traced to a six-bug exploit chain.</p>
Maya Protocol Exploit Drains Bitcoin, Pool Value Falls $11M
<p>Maya Protocol suffered an exploit that drained Bitcoin and other assets from its liquidity pools, cutting the protocol’s pool value by roughly $11 million and putting fresh scrutiny on cross-chain DeFi security.</p>
Ether.fi Adds Tokenized Stocks and Portfolio-Backed Loans to DeFi Platform
<p>The dual announcement was reported by Decrypt , which described Ether. fi rolling out tokenized equities and portfolio-backed borrowing on its platform.</p>
Tokenized RWA Deposits Reach $7.4B as DeFi Contracts 15%
<p>Tokenized real-world-asset (RWA) deposits have climbed to $7. 4 billion even as the broader decentralized finance market contracted 15%, according to research from CoinShares, pointing to a defensive rotation of capital toward yield-bearing and lower-volatility onchain products.</p>
Uniswap Launches Earn Feature for USDC, USDT, and ETH Deposits
<p>Uniswap has introduced an Earn feature that lets users deposit USDC, USDT, and ETH, extending the decentralized exchange beyond token swaps into a yield-oriented product built around three of the most widely held assets in DeFi.</p>
Aave to Phase Out 50 Low-Adoption Asset Reserves and Shut Down Six Chain Deployments
<p>The plan centers on two linked actions: deprecating a batch of asset reserves that have seen limited usage, and winding down Aave deployments across six chains. Both are set out in an ARFC on low-adoption asset deprecation for Aave v3 .</p>
Ebisu Front-End Decommission Set for October 30: What Users Need to Know
<p>Stablecoin protocol Ebisu says it will decommission its front-end on October 30, an operational change that will affect how users access the platform. The available materials confirm the front-end shutdown and the date, but do not detail a reason, a migration path, or what happens to underlying protocol functions.</p>
1inch Launches Aqua Shared Liquidity Protocol for Multi-Position DeFi Trading
<p>1inch has launched Aqua, a shared liquidity protocol built to serve multiple DeFi positions from a single pool of capital, according to the project’s official product materials. The release positions the 1inch Aqua shared liquidity protocol as new DeFi infrastructure rather than a token launch.</p>
Across Protocol Attacker-Linked Address Returns 331.8 ETH After Exploit
<p>An address linked to the Across Protocol incident has returned 331. 8 ETH, an on-chain movement that shifts the episode from outright loss toward partial recovery, though it does not confirm that the matter is fully resolved.</p>
TradeXYZ Contributed $215K to $241.8K of Hyperliquid Revenue in 24 Hours
<p>A trading entity identified as TradeXYZ reportedly accounted for $215,000 of Hyperliquid’s roughly $241,800 in protocol revenue over the past 24 hours, concentrating the vast majority of the perpetuals venue’s daily take in a single source.</p>
Hyperliquid Testnet Live With Stars, HIP-3 Whitelist Support
<p>The update surfaces through Hyperliquid’s developer resources and its in-app announcements channel, which together serve as the primary reference path for the testnet changes. The Hyperliquid announcements page is where the protocol publishes changes for testnet users and builders.</p>
Aave Founder Says CLARITY Act Nears Final Stage for DeFi
<p>Aave founder Stani Kulechov has signaled that the CLARITY Act has entered what he describes as a final stage, framing the digital asset market structure bill as a pivotal moment for DeFi regulation in the United States.</p>
Across Protocol Relayer Attack Caused Under $4M in Net Losses, User Funds Unaffected
<p>Across Protocol said a relayer attack resulted in less than $4 million in net losses, and that user funds were not affected by the incident.</p>