<![CDATA[News - DAO Times]]> We are the voice of the rising decentralized world https://daotimes.com/ https://daotimes.com/favicon.png News - DAO Times https://daotimes.com/ Ghost 6.64 Sun, 20 Sep 2026 14:13:30 GMT 60 <![CDATA[Global Gold DAO Brings Physical Gold Tokenization To BNB Chain]]> Global Gold DAO launches GGT, GGU and GGD on BNB Chain, tokenizing physical gold against a $5.5 billion market led by Tether Gold and PAX Gold. https://daotimes.com/global-gold-dao-brings-physical-gold-tokenization-to-bnb-chain/ 6aafb7145281b4000164cb2a News Jamie Larson Sun, 20 Sep 2026 10:37:38 GMT <img src="https://daotimes.com/content/images/2026/09/gold-price-2026.png" alt="Global Gold DAO Brings Physical Gold Tokenization To BNB Chain"><p>Global Gold DAO launched a tokenized physical gold ecosystem on BNB Chain on September 20, 2026. The protocol, branded GGD, uses a three-token structure to connect gold-referenced value with on-chain staking, minting and governance. It calls itself the first decentralized on-chain physical gold ecosystem DAO.</p><h3 id="what-ggd-actually-built">What GGD Actually Built</h3><p>The system separates gold exposure into three assets. GGT is the core token, each unit representing 0.001 troy ounces of gold. Its value currently tracks the CSOP Gold ETF, a Hong Kong-listed fund holding physical gold against the LBMA benchmark. A later phase is meant to add directly held gold bars alongside the ETF backing.</p><p>GGU works as a volatility buffer, a synthetic dollar unit pairing &#x24;1 of gold exposure with a short gold position. The goal is to hold GGU near &#x24;1 regardless of gold price swings. The white paper is direct about a weak point here: full hedging may not work early on if reserves run short, leaving GGU exposed to price moves it was designed to cushion.</p><p>GGD is the governance token, capped at one billion units. Holders vote on protocol parameters and receive rewards funded by buybacks tied to protocol revenue. Staking GGT or GGU through protocol nodes earns GGD, with a minimum stake of 10 GGT.</p><p>Legal structuring places GGT issuance under RWAfi DAO LLC &#x2013; Series 2, a Marshall Islands entity, while GGD DAO governance controls protocol parameters and smart contracts. Redemption for physical gold requires a minimum of 50,000 GGT, or 50 troy ounces, at a 2.5% fee. Cash redemption into USDC or USDT costs 3.5%.</p><h3 id="why-gold-tokenization-is-having-a-moment">Why Gold Tokenization Is Having A Moment</h3><p>Gold has climbed hard through 2026. Spot prices moved from around &#x24;2,750 an ounce in January past &#x24;4,500 by August, driven by central bank buying, rate-cut expectations and a weaker dollar. That rally pulled capital into gold-backed tokens as well as physical bullion.</p><p>The tokenized gold market sits near &#x24;5.5 billion in market cap as of September 2026, according to CoinGecko data. Two tokens dominate it: Tether Gold and PAX Gold together hold roughly 85% to 90% of that value, each above &#x24;2 billion. Smaller players like Kinesis Gold and Matrixdock Gold trail far behind, in the tens to low hundreds of millions.</p><p>That concentration is the market GGD is entering. Nearly every existing tokenized gold product runs on Ethereum. GGD&apos;s choice of BNB Chain is a bet on lower fees and a different user base rather than head-on competition with the incumbents on their own rails.</p><p>Tokenized gold sits inside a broader real-world asset trend. Total on-chain RWA value, excluding stablecoins, is estimated between &#x24;22 billion and &#x24;35 billion in 2026, up sharply from roughly &#x24;8 billion at the start of 2024. Tokenized Treasuries lead that category, with gold and commodities as the second-largest segment. BlackRock, Franklin Templeton and other traditional asset managers have entered the space, lending it institutional weight it lacked two years ago.</p><h3 id="the-case-for-tokenized-gold">The Case For Tokenized Gold</h3><p>Physical gold ownership carries friction: storage costs, insurance, limited divisibility and slow cross-border settlement. It also cannot easily serve as collateral in digital finance. Tokenization addresses each of these by making gold exposure transferable on-chain, divisible into small units and usable in lending or liquidity protocols around the clock.</p><p>GGD adds a governance layer on top of this, aiming to let token holders influence protocol rules rather than leaving all control with a single issuer. The buyback mechanism, funded by protocol revenue, is designed to tie GGD&apos;s value to actual platform usage rather than speculation alone.</p><h3 id="the-risks-worth-weighing">The Risks Worth Weighing</h3><p>The white paper itself lists gold-price risk, GGT tracking error, GGU hedging failure, smart-contract vulnerabilities, liquidity constraints, governance concentration and regulatory uncertainty. GGT holders do not own ETF shares or gold bars directly; they hold a contractual claim structured through Marshall Islands entities, a jurisdiction chosen for flexibility rather than regulatory rigor.</p><p>Access is also restricted. Users must qualify as professional or accredited investors and pass Know Your Transaction and Know Your Address screening. People in the United States, mainland China, or UN-sanctioned jurisdictions cannot use the official interface at all, which narrows the addressable market considerably.</p><p>GGD is starting from zero market cap in a segment where two incumbents already hold roughly &#x24;5 billion combined. Whether governance-driven incentives and a BNB Chain listing are enough to carve out share will depend on adoption data that does not yet exist.</p> <![CDATA[Concrete Launches A Foundation And Governance Token As Onchain Yield Infrastructure Matures]]> Concrete launches CT governance token and a Cayman Islands foundation after reaching $1.2 billion in deposits and $23 billion in cumulative volume. https://daotimes.com/concrete-launches-a-foundation-and-governance-token-as-onchain-yield-infrastructure-matures/ 6aad84e75281b4000164cb1d News Jamie Larson Fri, 18 Sep 2026 18:42:02 GMT <img src="https://daotimes.com/content/images/2026/09/concrete-funding-rounds.png" alt="Concrete Launches A Foundation And Governance Token As Onchain Yield Infrastructure Matures"><p>Concrete introduced the Concrete Foundation on September 17, alongside CT, its native governance token. The move hands protocol decisions to a Cayman Islands entity and a fixed-supply token. It comes as the yield vault system reports &#x24;1.2 billion in deposits and 54,000 depositors.</p><p>Concrete started as Blueprint Finance, raising &#x24;7.5 million in February 2024 from Hashed and Tribe Capital. A second round followed in June 2025, adding &#x24;9.5 million from Polychain Capital, YZi Labs, VanEck, and eighteen other backers. Total funding reached &#x24;17 million across two rounds and 36 investors.</p><p>The protocol runs automated vaults that route deposits into lending, restaking, and structured credit markets. Depositors receive ct[asset] tokens as receipts, which they can then reuse as collateral elsewhere in DeFi. Concrete calls this loop its vault flywheel, since each integration pulls more liquidity into partner protocols.</p><p>That model built real scale before any token existed. Concrete reports &#x24;23 billion in cumulative volume and current total value locked near &#x24;970 million, based on DeFiLlama data. Partnerships spanned Renzo, Berachain, Ethena, Movement, and Morph, giving the protocol reach across several ecosystems rather than one chain.</p><p>CT changes the governance layer without changing the vault mechanics. The token is ERC-20, capped at one billion units, with no inflation mechanism. Holders who lock or stake CT gain a say in strategy approvals, collateral categorization, fee structures, and treasury policy.</p><p>Staking also lets holders adjust certain protocol-side fees tied to their own module interactions, a design that ties governance activity to direct usage. The Concrete Foundation, based in the Cayman Islands, holds and manages the CT treasury. It funds development, security audits, ecosystem integrations, and administrative costs going forward.</p><p>No token generation event date has been set. Concrete says there are no claims, presales, or early access programs active, and that Concrete Network, Ltd. is separately pursuing listing access for CT. That separation between the Foundation and the issuing entity is a structure now common among onchain protocols moving into formal governance.</p><p>This is part of a broader shift. DAO-style foundations increasingly form only after a protocol has already proven usage, rather than before. Points campaigns and unlaunched tokens carried Concrete through most of 2025, with the project running &quot;Bags&quot; quests ahead of any formal governance structure.</p><p>The timing lines up with a heavier regulatory week in the United States. On the same day, the SEC issued temporary exemptive relief letting tokenized securities venues trade tokenized NMS stocks through permissioned AMMs. The CFTC cleared software developers to build tools linking users to registered futures firms without broker registration.</p><p>Neither ruling touches Concrete directly, since it is a DeFi yield protocol rather than a securities venue. But both point to regulators giving onchain financial infrastructure more room to operate under defined conditions. Governance tokens tied to real treasuries sit inside that same conversation about accountability.</p><p>The design carries real tradeoffs for CT holders. A fixed, non-inflationary supply avoids the dilution that hurts many governance tokens over time. But locking or staking is required to participate, which reduces liquidity for holders who want influence without giving up flexibility.</p><p>Concentration is the harder question. Two funding rounds brought in 36 institutional investors, including Polychain, VanEck, and YZi Labs. If a meaningful share of CT ends up with these early backers, governance could lean toward funds rather than the depositors who built the &#x24;1.2 billion in deposits.</p><p>Concrete&apos;s approach mirrors a pattern seen at ENS DAO and other mature protocols, where large holders can swing votes on core decisions. A foundation structure adds legal clarity and treasury discipline. It does not by itself guarantee that governance power matches who actually uses the protocol day to day.</p><p>For now, Concrete has usage numbers most unlaunched tokens do not carry into a foundation launch. Whether CT distribution spreads that governance power broadly, or concentrates it further, depends on details the project has not yet published.</p> <![CDATA[One Wallet Almost Pulled 98% Of Ampleforth's USDC Before A Last-Minute Cancellation]]> One wallet used delegated FORTH to request 98% of Ampleforth's USDC treasury before the proposal was canceled with zero votes cast. Here's what happened. https://daotimes.com/one-wallet-almost-pulled-98-of-ampleforths-usdc-before-a-last-minute-cancellation/ 6aa988e6f2704a000101de0e News Jamie Larson Tue, 15 Sep 2026 18:07:44 GMT <img src="https://daotimes.com/content/images/2026/09/ampleforth-treasury-breakdown.png" alt="One Wallet Almost Pulled 98% Of Ampleforth&apos;s USDC Before A Last-Minute Cancellation"><p>A proposal asking for 2.5 million USDC from Ampleforth&apos;s treasury got canceled on-chain on September 14, 2026, hours before its voting window would have opened. The request equaled about 98.5% of the treasury&apos;s visible USDC balance. No funds moved. But the sequence of transactions behind it now raises questions about how easily Ampleforth&apos;s governance system can be pointed at its own treasury.</p><p><strong>What happened</strong></p><p>Proposal 54 appeared on Ampleforth&apos;s Tally governance page asking to send 2.5 million USDC to a single wallet, 0x730C&#x2026;dd82. The proposal described the payment as a retrospective grant for Observatory for SPOT, an open-source analytics tool for the AMPL and SPOT ecosystem. The proposal called the tool complete, independent, and unofficial.</p><p>A Tally treasury snapshot from September 15 showed the DAO held about 2.54 million USDC and &#x24;3.56 million in total treasury value. That made the request roughly 70.2% of the entire treasury and nearly all of its stablecoin reserves.</p><p><strong>The FORTH that made it possible</strong></p><p>Ampleforth&apos;s governor contract requires a minimum amount of delegated voting power to submit a proposal. About 19 minutes before Proposal 54 went live, a separate address, 0x38cA&#x2026;24D8, delegated 87,238.5461 FORTH to the wallet that then created the proposal. That delegation cleared the submission threshold. The proposal itself listed 0x38cA&#x2026;24D8 as an address the grantee might use to vote or that might delegate power to it. Who controls that address is not established in the proposal or in the onchain record.</p><p><strong>Then it unwound just as fast</strong></p><p>On September 14, the same delegating address transferred all 87,238.5461 FORTH back out. About 14 minutes later, someone called <code>cancel(54)</code> on the governor contract. Ampleforth&apos;s governor code includes a function that lets a proposal be canceled if the proposer&apos;s voting power, measured at a prior block, drops below the proposal threshold. The transaction order matches that mechanism, though the public record does not confirm it was the exact path used, or who triggered it.</p><p>Tally shows zero votes were ever cast on Proposal 54, and the cancellation block came before the scheduled start of voting. The 2.5 million USDC never left the treasury.</p><p><strong>Why the gap matters</strong></p><p>Ampleforth&apos;s own governance documentation lays out a multi-stage process: open discussion, formal proposal drafting, targeted community discussion, optional offchain signaling, and technical review, all before a binding onchain vote. The smart contract itself does not enforce any of those steps. It only checks whether the proposer holds enough delegated voting power at the moment of submission.</p><p>That gap between documented process and contract logic is what let Proposal 54 reach the binding voting system without any visible community discussion beforehand. Borrowed or temporarily concentrated voting power was enough to clear the bar. Nothing in the code distinguishes a wallet that earned support over months from one that received a large delegation minutes earlier.</p><p>GoPlus Security flagged the proposal on social media while it was still pending, describing it as an attack. That is the security firm&apos;s characterization, not a conclusion drawn from the onchain record itself. The verified facts show a canceled proposal, zero votes, and no executed transfer. Intent remains unproven either way.</p><p><strong>The market noticed</strong></p><p>FORTH was up 21.15% over 24 hours as of the article&apos;s publication, with 7-day gains of 37.28% and 30-day gains of 97.67%. Governance controversies at small-cap DAOs often move the underlying token, since attention itself can attract speculative buying regardless of whether the proposal in question was legitimate or not.</p><p><strong>What this leaves unresolved</strong></p><p>The proposal&apos;s cancellation is a point in Ampleforth&apos;s favor: the governor contract&apos;s safeguard worked as designed, and the treasury kept its funds. But the episode also shows that a proposal worth nearly three-quarters of total treasury value can reach the binding voting stage without a public vote testing it first. For a DAO managing a shared treasury, the design question is not whether cancellation is possible. It is whether submission should require more than borrowed voting power in the first place.</p><p>Ampleforth has not published a public response addressing whether it plans to change the proposal threshold, add a mandatory discussion period enforced onchain, or review delegation patterns tied to large treasury requests. Until it does, the same mechanism that allowed Proposal 54 to reach the ballot remains available to the next wallet that gathers enough delegated FORTH, however briefly.</p> <![CDATA[Core DAO Turns A Validator Exploit Into A Case For Its Buyback Plan]]> Core DAO burned 150 million CORE after a validator exploit forced an emergency hard fork. Here's what happened and what it means for the token's recovery. https://daotimes.com/core-dao-turns-a-validator-exploit-into-a-case-for-its-buyback-plan/ 6aa54574f2704a000101dde3 News Jamie Larson Sat, 12 Sep 2026 12:30:52 GMT <img src="https://daotimes.com/content/images/2026/09/core-dao-exchange-response.png" alt="Core DAO Turns A Validator Exploit Into A Case For Its Buyback Plan"><p>Core DAO spent early September patching a validator exploit that let a small group of operators claim block rewards above schedule. The fix was an emergency hard fork that burned over 150 million CORE. Staking resumed within 48 hours, and trading volume jumped more than 170%.</p><p>The token, still down close to 99% from its February 2023 high of &#x24;6.14, trades around &#x24;0.02 today. That is a recovery of roughly 40% from July&apos;s all-time low, but the base it is recovering from is extreme.</p><h3 id="what-happened-on-chain">What Happened On Chain</h3><p>Core runs on Satoshi Plus, a hybrid consensus system mixing Bitcoin mining power, Bitcoin staking, and CORE staking. Validators are ranked each round by a scoring formula, and up to 90% of new CORE goes to whoever scores highest.</p><p>On September 1, Core DAO disclosed that a handful of validators had found a flaw in that scoring formula. They claimed rewards beyond what the 81-year emission schedule allowed. The team called the behavior malicious, said user funds were untouched, and froze further exploitation while it built a fix.</p><p>Two days later, Core shipped hard fork v1.0.26. It was forward-only: no rollback, no reversed transactions. Instead, the protocol burned the excess tokens directly, removing more than 150 million CORE from total supply. Staking rewards, paused during the incident, resumed normal operation within 48 hours.</p><p>Core has not disclosed exactly how long the exploit ran or whether any of the extra tokens reached the open market before the burn. A promised technical postmortem has not yet been published in full detail.</p><h3 id="exchanges-reacted-before-the-fix-landed">Exchanges Reacted Before The Fix Landed</h3><p>The uncertainty during those two days was enough for several exchanges to pull back. Coinbase paused CORE sends and receives on-chain. Bithumb and Coinone suspended deposits and withdrawals, citing security concerns. Bitget cited wallet maintenance, and LBank pointed to project-side requirements.</p><p>None of these exchanges reported user losses. The pattern instead shows how fast centralized platforms move to limit exposure when a base layer&apos;s consensus mechanism is in question, even before a root cause is confirmed. Restrictions lifted within days, once the fork went live.</p><h3 id="why-the-timing-matters-for-tokenomics">Why The Timing Matters For Tokenomics</h3><p>The exploit landed in the middle of a bigger shift in how CORE&apos;s economics are supposed to work. Under the 2026 roadmap, Core DAO wants to stop relying on transaction-fee burns and instead fund open-market CORE buybacks using revenue from Bitcoin DeFi products, including staking yield and a payments product called SatPay.</p><p>That model depends on the network actually generating revenue at scale, which has not yet been proven. The September burn was not part of that buyback mechanism. It was a one-off correction to a bug, not recurring demand-side pressure. But it did shrink total supply by roughly 7%, which tightens the denominator any future buyback plan is measured against.</p><h3 id="the-numbers-behind-the-recovery">The Numbers Behind The Recovery</h3><p>CORE&apos;s circulating supply sits near 1.24 billion out of a 2.1 billion cap, with about 705 million still locked and gradually unlocking. Market cap is in the &#x24;24-30 million range depending on the day, a fraction of what it was during 2023&apos;s launch enthusiasm.</p><p>The 40% bounce off July&apos;s low coincides with the resolved exploit and renewed staking activity, not with any confirmed revenue from BTCFi products. Analysts covering the token describe the mood as cautiously improving rather than confident. Long-term holders point to Core&apos;s position as Bitcoin-secured infrastructure; skeptics point to a drawdown that erased nearly all of the token&apos;s value over three years.</p><h3 id="what-this-means-going-forward">What This Means Going Forward</h3><p>Core DAO&apos;s response to the exploit was fast and transparent by crypto standards: public disclosure, a forward-only fix, no fund losses, and staking restored within two days. That is a legitimate point in its favor for a chain built around validator trust.</p><p>The open question is separate from the exploit itself. Core&apos;s entire 2026 pitch rests on BTCFi products generating enough real revenue to power systematic buybacks. Hardware wallet staking integration and a native stablecoin are both still pending for H2 2025 timelines that have already slipped into 2026. Until SatPay and related products show actual revenue numbers, the buyback thesis remains a plan rather than a track record.</p> <![CDATA[TRON Opens MetaMask Access To Four More DAO-Linked Applications]]> TRON adds MetaMask wallet support to B.AI, SUN.io, JustLend DAO and BitTorrent, giving users direct access to TRON DeFi apps without switching wallets. https://daotimes.com/tron-opens-metamask-access-to-four-more-dao-linked-applications/ 6aa2dd9d0423bc0001ac5024 News Jamie Larson Thu, 10 Sep 2026 16:42:54 GMT <img src="https://daotimes.com/content/images/2026/09/tron-metamask-metrics-doughnut-chart.png" alt="TRON Opens MetaMask Access To Four More DAO-Linked Applications"><p>TRON DAO has expanded MetaMask wallet connectivity to four more applications in its ecosystem: B.AI, SUN.io, JustLend DAO, and BitTorrent. The announcement came from Geneva on September 10, 2026. Users can now link MetaMask directly to these dApps instead of relying on TRON-native wallets.</p><p>This builds on a longer integration process. MetaMask and TRON DAO signed a partnership in August 2025. Native TRON support went live across MetaMask&apos;s mobile and browser extension in January 2026. That step let users hold TRX, send USDT, and swap assets between TRON, Ethereum, Solana, and Bitcoin inside one wallet. The September update pushes that base integration further, into the applications people actually use TRON for.</p><h3 id="what-each-platform-adds">What Each Platform Adds</h3><p>JustLend DAO is TRON&apos;s lending protocol, carrying more than &#x24;7 billion in total value locked. It supports borrowing, lending, and staking. MetaMask users can now reach these functions without switching wallets, using self-custody credentials they already manage.</p><p>SUN.io is TRON&apos;s largest decentralized platform, with over &#x24;650 million in TVL. It runs SunSwap V4, an automated market maker and decentralized exchange. MetaMask connectivity gives outside users a direct path into TRON&apos;s DeFi trading layer.</p><p>B.AI takes a different angle. It builds financial infrastructure for AI agents, giving them independent identities so they can transact and execute on-chain without human intervention at each step. This ties MetaMask into the agent-economy trend that has drawn attention across the industry through 2026.</p><p>BitTorrent rounds out the group. It offers cross-chain interoperability through BitTorrent Chain and decentralized storage through the BitTorrent File System. Both plug into MetaMask&apos;s cross-chain swap capability, which already spans TRON, EVM chains, Solana, and Bitcoin.</p><h3 id="why-tron-keeps-courting-metamask-users">Why TRON Keeps Courting MetaMask Users</h3><p>TRON&apos;s pitch centers on scale. The network says it processes more than &#x24;23 billion in average daily stablecoin transfer volume and hosts over &#x24;94 billion in circulating USDT, the largest supply of any chain. Total value locked across TRON sits above &#x24;27 billion, and TRONSCAN puts total accounts past 402 million.</p><p>MetaMask brings a different kind of scale: distribution. It remains one of the most used self-custody wallets in crypto, with a user base built mostly around Ethereum and EVM chains. Native TRON support, once limited to asset management, now extends into application-level interaction. That closes a real gap &#x2014; a wallet with reach, meeting a network with settlement volume.</p><p>Sam Elfarra, TRON DAO&apos;s community spokesperson, framed the expansion as giving users more ways to reach TRON &quot;through a wallet they already know and use.&quot; MetaMask&apos;s Dan Rosario echoed that self-custody stays intact even as application access grows.</p><h3 id="reading-the-announcement-honestly">Reading The Announcement Honestly</h3><p>The gains are real but bounded. Connectivity is not usage. Making JustLend DAO and SUN.io reachable through MetaMask lowers friction, but it does not guarantee new deposits or trading volume will follow. TVL on both protocols has moved sharply in both directions before, driven by TRON-linked capital flows rather than steady organic growth.</p><p>There&apos;s also a concentration question worth naming. TRON&apos;s DeFi TVL has historically leaned heavily on JustLend alone, at times holding the large majority of total deposits. Broader wallet access does not on its own change that structure &#x2014; it just adds a new front door to protocols that were already there.</p><p>For BitTorrent and B.AI, the news matters more as a signal than as a numbers story. Neither publishes TVL figures comparable to lending or DEX protocols, so their inclusion reads as ecosystem breadth rather than a liquidity event. B.AI in particular is a bet on a market &#x2014; autonomous agent payments &#x2014; that is still forming, not one with established transaction volume to point to.</p><p>The expansion is one more step in a rollout that started over a year ago, not a standalone launch. Each addition &#x2014; the August 2025 agreement, the January 2026 native rollout, and now this application-level expansion &#x2014; has been incremental. That pattern likely continues, since TRON DAO has stated more applications will add MetaMask connectivity going forward.</p> <![CDATA[Arbitrum's Watchdog Sets Sept. 10 Deadline For Three DeFi Projects Facing DAO Bans]]> Arbitrum's Watchdog Committee gives Good Entry, Limitless and APX Finance until Sept. 10 to respond or face DAO votes on permanent program bans. https://daotimes.com/arbitrums-watchdog-sets-sept-10-deadline-for-three-defi-projects-facing-dao-bans/ 6aa02b82c8c43900013ab55f News Jamie Larson Tue, 08 Sep 2026 15:37:51 GMT <img src="https://daotimes.com/content/images/2026/09/chart3_hbar--2-.png" alt="Arbitrum&apos;s Watchdog Sets Sept. 10 Deadline For Three DeFi Projects Facing DAO Bans"><p>Arbitrum&apos;s Watchdog Committee has given three DeFi projects one week to explain themselves or face votes on permanent exclusion from the DAO. Good Entry, Limitless, and APX Finance (formerly ApolloX) are named in a proposal published September 3 on the Arbitrum governance forum. The committee wants funds returned or answers delivered by September 10.</p><p>As of September 5, none of the three projects had replied on the thread.</p><h3 id="what-the-committee-found">What The Committee Found</h3><p>Each case stems from Arbitrum&apos;s legacy incentive programs, STIP and LTIPP, which distributed ARB grants in 2023 and 2024 to bootstrap DeFi activity on the network. The Watchdog Program, a bounty system for reporting grant misuse, flagged all three after reviewing on-chain activity.</p><p>Good Entry received a 200,000 ARB grant under STIP Round 1. The committee says 142,839 ARB went to 1,032 ineligible users during and after the incentive period, with evidence of self-farming by wallets linked to team addresses. When contacted, Good Entry declined to cooperate. The project has been inactive since STIP ended.</p><p>Limitless requested 75,000 ARB through LTIPP for liquidity incentives. The committee says the full amount was swapped into USDC and moved to Base, taking the funds off Arbitrum entirely. No team members could be reached afterward.</p><p>APX Finance requested 525,000 ARB through LTIPP. The committee ties 239,714 ARB to a mix of problems: funds left sitting in treasury wallets instead of reaching distributor contracts, late transfers, and a Sybil cluster allegedly connected to team addresses. That figure is not broken down by issue, so it reflects several overlapping findings rather than one clean number.</p><p>Combined, the three cases cite 457,553 ARB. That total spans distributions to outside users, an alleged theft, and unspent treasury funds, so it should not be read as one recoverable balance owed to the DAO.</p><h3 id="how-a-ban-would-work">How A Ban Would Work</h3><p>If the committee is unsatisfied with a project&apos;s response, it will bring a separate Snapshot vote for each. Delegates would choose whether to permanently ban the project, its founders, and its affiliated contributors from future Arbitrum DAO programs. For projects no longer operating, the ban would apply only to founders.</p><p>This is a social-consensus vote, not an on-chain transaction. It carries no ability to freeze wallets or claw back funds directly. What it does is block banned individuals and teams from qualifying for future DAO grants, retroactive rewards, or paid roles.</p><p>Arbitrum has used this mechanism once before. In August 2024, delegates voted to ban Furucombo after a similar dispute over misused STIP funds, following months of what the DAO described as insufficient cooperation. That case became the template for the enforcement now applied to Good Entry, Limitless, and APX Finance, down to the same three-option Snapshot format and the same appeal path through a future forum proposal.</p><h3 id="the-program-behind-the-cases">The Program Behind The Cases</h3><p>The Watchdog Program launched in mid-2025 as a bounty system open to any community member who could document fund misuse. Reports go to a reviewing committee made up of the Arbitrum Foundation, Entropy Advisors, and SeedGov, with payouts of up to 5% of recovered funds.</p><p>By late March 2026, a retrospective from Entropy Advisors showed the program had logged 78 reports, with 32 confirmed as valid misuse out of 51 completed reviews, a validation rate near 63%. Every confirmed case up to that point traced back to the DAO&apos;s legacy incentive rounds: STIP, STIP Bridge, and LTIPP.</p><p>That pattern led the committee to narrow the program&apos;s scope in May 2026, cutting off new reports tied to programs launched before January 1, 2025. The stated reasoning was that older cases take disproportionate time to investigate, show falling odds of fund recovery, and depend on Arbitrum Foundation relationships that a planned operational successor, OpCo, does not yet have.</p><p>As of September 2, the program had received 90 reports total, recovered roughly 532,000 ARB for the DAO, and paid out about 268,000 ARB in bounties to reporters. The three new cases would add to that count if the bans proceed.</p><h3 id="what-comes-next">What Comes Next</h3><p>The September 10 date is described by the committee as tentative. Two outcomes are possible before then: a project responds with an explanation the committee accepts, or funds get returned within the window, either of which would head off a vote.</p><p>Absent that, the committee moves to publish three separate Snapshot proposals the same day. Delegates would then decide project by project, following the same FOR, AGAINST, and ABSTAIN structure used in the Furucombo case.</p><p>The proposal does not address whether any of the three projects still has operational funds available to return, given that Good Entry and Limitless both appear inactive. That leaves the practical weight of the process resting on reputational consequence rather than fund recovery, a limitation the DAO has already lived with once before.</p> <![CDATA[DAO Governance Rules Keep Rebuilding The Power They Were Meant To Remove]]> Compound's Proposal 289 nearly moved $24 million in COMP votes. New research on 48 Ethereum DAOs shows why governance safeguards concentrate power. https://daotimes.com/dao-governance-rules-keep-rebuilding-the-power-they-were-meant-to-remove/ 6a9d5943c8c43900013ab54c News Jamie Larson Sun, 06 Sep 2026 12:17:30 GMT <img src="https://daotimes.com/content/images/2026/09/dao-locking-service-concentration.png" alt="DAO Governance Rules Keep Rebuilding The Power They Were Meant To Remove"><p>Compound&apos;s near-miss with a &#x24;24 million treasury transfer has become the reference case for a wider problem in DAO governance. New research from the Max Planck Institute for Software Systems and Vrije Universiteit Amsterdam shows that the very rules protecting DAOs from attacks tend to concentrate control in a small group of holders, delegates, and custodians.</p><h3 id="what-happened-at-compound">What Happened At Compound</h3><p>In July 2024, Compound&apos;s Proposal 289 asked the DAO to move 499,000 COMP, worth about &#x24;24 million, into a yield vehicle controlled by a group called the Golden Boys, led by a delegate known as Humpy. Two earlier versions of the same request had failed.</p><p>The third attempt looked headed for defeat too, until the final 34 minutes. Supporting wallets cast 563,591 votes in that window, 82% of all support the proposal received. The last large block arrived eight minutes before the deadline. The measure passed 682,191 to 633,636.</p><p>Researchers traced 563,790 of the tokens behind the campaign through four centralized exchanges, plus another 118,089 borrowed directly from Compound. The addresses involved had held only 853 COMP before the buildup began, with no prior history in the protocol&apos;s governance.</p><p>Nothing in the code broke. Compound had no emergency authority able to pause execution once a valid vote crossed the threshold. The DAO settled by canceling the transfer and later added a veto role, trading pure automatic rule for a human checkpoint.</p><h3 id="why-this-keeps-happening">Why This Keeps Happening</h3><p>Two 2026 papers examined 48 large Ethereum DAOs to find out how common this pattern is. One paper mapped how registration, staking, and delegation shape who actually gets to vote. The other classified governance attacks that used entirely valid rules.</p><p>Casting a vote in most DAOs takes more than holding a token. A holder may need to register a wallet, lock tokens for a period, delegate to someone else, or pay gas fees before their balance counts. Each requirement solves a real problem and each one favors a different type of participant.</p><p>Among the 48 DAOs studied, 36 required registration before a token could vote. Only four of those had registered more than half of their supply. The average across all 36 was 21%, meaning most of each DAO&apos;s tokens sat outside the active electorate.</p><p>Centralized exchanges held over 10% of outstanding tokens on average, and DeFi protocols held another 3.5%. In 14 of the registration-based DAOs, these intermediary wallets held more tokens combined than the entire registered voting base.</p><p>Staking works differently, aiming to make a fast attack expensive by locking tokens for a fixed period. Fifteen DAOs in the sample required it, with a median lock rate of 27.4% of supply. Curve, Angle, and Frax reward locks running up to four years with stronger voting weight.</p><p>That reward structure created an opening for specialized services. Convex holds 53% of Curve&apos;s voting power and 46% of Frax&apos;s. StakeDAO holds 57% of Angle&apos;s. Aura holds 65% of Balancer&apos;s. Each service lets users keep liquidity while it retains the underlying vote, turning long-term lockups into concentrated blocs controlled by a handful of platforms.</p><p>Delegation adds a third layer. Most token holders skip governance debates and hand their votes to someone who follows the details. Across the 48 DAOs, the ten largest holders controlled more than half of voting power in 39 of them, and delegated power was typically more concentrated than direct voting power.</p><h3 id="when-a-legal-vote-becomes-a-raid">When A Legal Vote Becomes A Raid</h3><p>The second paper defines a governance attack as any case where someone uses the DAO&apos;s own authorized process to produce an outcome that damages the wider organization. Looking at 28 real incidents, researchers found 16 fit that pattern and could have been stopped by a different design choice. Six involved contract bugs. Ten depended on buying or borrowing enough tokens to swing a result.</p><p>Compound&apos;s case became the clearest example of the second category. Researchers noted that in the 2024 governance configurations they reviewed, seven other protocols carried similar exposure to fast-accumulated voting power and late-vote surges: Uniswap, Radicle, Gitcoin, Silo, Ampleforth, Hop, and Cryptex. Governance evolves, so this list reflects conditions at that time rather than current risk.</p><p>Every fix available to Compound would have shifted power somewhere else. A longer vote window rewards patient accumulators. Mandatory staking rewards committed holders. A pause mechanism rewards whoever holds the veto. Compound picked the veto, and COMP has since traded around &#x24;21, up roughly 25% over the past 90 days as the market absorbed the episode&apos;s resolution.</p><h3 id="what-a-fair-comparison-would-need">What A Fair Comparison Would Need</h3><p>Token distribution alone does not describe how decentralized a DAO actually is. A useful governance report would show what fraction of supply can vote, how much power sits with top delegates, which platforms hold locked tokens on users&apos; behalf, and who holds override authority.</p><p>Smart contract audits already check whether governance code matches its written specification. A parallel review focused on where that specification sends authority would catch the risk Compound faced: a DAO can spread token ownership across thousands of wallets and still run on the decisions of a few dozen professionals, custodians, and large holders, with software that never once malfunctions.</p> <![CDATA[Curve DAO Hands Risk Oversight To Resupply's Own Developers]]> Curve DAO approved yRisk, led by Resupply's own developers, as its new risk provider for crvUSD and Llamalend after a near-unanimous $250,000 vote. https://daotimes.com/curve-dao-hands-risk-oversight-to-resupplys-own-developers/ 6a9ac6cbc8c43900013ab533 News Jamie Larson Fri, 04 Sep 2026 13:26:30 GMT <img src="https://daotimes.com/content/images/2026/09/chart2_timeline_line.png" alt="Curve DAO Hands Risk Oversight To Resupply&apos;s Own Developers"><p>Curve DAO approved yRisk as its new risk-management provider on September 2. The team will monitor crvUSD and Llamalend for the next twelve months. Its two contributors are also the primary developers behind Resupply, a protocol that lost &#x24;9.6 million to a donation attack in June 2025.</p><p>The onchain vote closed decisively. Roughly 621.2 million veCRV supported the proposal, against 5.33 veCRV opposed. Curve executed the mandate about 87 minutes after voting ended.</p><h3 id="what-yrisk-was-hired-to-do">What yRisk Was Hired To Do</h3><p>yRisk will review collateral, liquidity, oracle design, concentration and governance risk across crvUSD mint markets and Llamalend&apos;s isolated lending markets. It will recommend debt ceilings, market parameters and PegKeeper limits. Curve governance and the emergency DAO keep final say over execution.</p><p>The team, known by the handles Wavey and Dudesahn, plans to build public dashboards, alerts and automated code-analysis tools. Curve&apos;s proposal states that work funded under the mandate will generally carry an open-source license, so other protocols could reuse it.</p><p>Payment comes through two revocable one-year vesting streams: 125,000 frxUSD and 568,181 CRV, worth close to &#x24;250,000 combined at approval-date prices. Curve can halt the remaining vesting at any point if yRisk underperforms.</p><h3 id="the-resupply-connection">The Resupply Connection</h3><p>Both yRisk contributors are core developers at Yearn and at Resupply, and the proposal names them as Resupply&apos;s primary developers. Resupply is a stablecoin lending protocol that suffered a donation attack in June 2025.</p><p>An attacker donated assets into a nearly empty vault, forcing an exchange-rate calculation to round toward zero. That let the attacker borrow against collateral that appeared far larger than it was. QuillAudits attributed the roughly &#x24;9.6 million loss to this exchange-rate manipulation.</p><p>Neither yRisk&apos;s proposal nor Curve&apos;s comparative assessment mentioned the Resupply exploit by name. Both documents discussed the team&apos;s Resupply experience without referencing the incident that cost users millions. Curve&apos;s call for proposals asked for relevant experience and methodology but did not explicitly require disclosure of past incidents tied to a contributor&apos;s other projects. So the omission is not a clear breach of process, even though it leaves a gap in what voters saw before casting ballots.</p><h3 id="reviewers-flagged-capacity-not-the-exploit">Reviewers Flagged Capacity, Not The Exploit</h3><p>Swiss Stake reviewed nine competing applications ahead of Curve&apos;s preference vote. Its assessment credited yRisk with practical knowledge of Curve, Llamalend, Yearn and Resupply, and it did not raise the 2025 exploit as a concern.</p><p>The review&apos;s main worry was staffing. Swiss Stake questioned whether two contributors with other obligations could monitor a growing set of markets and still deliver adequate incident coverage. It recommended a limited initial mandate with a public checkpoint, a suggestion Curve did not build into the final terms.</p><p>In the nonbinding preference vote, yRisk drew about 536.97 million veCRV in favor and zero against, from 47 voters. That represented close to 69% of voting supply at the snapshot block, a margin that carried into the binding vote two weeks later.</p><h3 id="why-curve-needed-a-replacement-at-all">Why Curve Needed A Replacement At All</h3><p>LlamaRisk had renewed its Curve mandate in April 2026, with plans running through April 2027. It reversed course on May 29, announcing an early exit, and stopped active work on June 30. LlamaRisk returned about 270,247 crvUSD in unvested funding to Curve&apos;s treasury and described the departure as a resourcing decision, not a criticism of the DAO.</p><p>Curve opened its replacement search on July 7. The timing overlapped with an active expansion of Llamalend, which introduced isolated lending markets on Optimism ahead of a planned Ethereum deployment. More markets typically mean more surface area for a risk provider to cover.</p><p>Risk management has been a recurring theme at Curve this year, not a one-off issue. In March, an improperly configured oracle let an attacker extract about &#x24;240,000 from a Llamalend market. That incident, smaller than the Resupply exploit but from the same category of failure, shows why the DAO treats this role as more than a formality.</p><h3 id="what-comes-next">What Comes Next</h3><p>yRisk now inherits LlamaRisk&apos;s reports, models and dashboards and must decide what to keep, rebuild or retire. Its proposal commits to monthly progress reports plus continuous monitoring and incident support.</p><p>The revocable structure gives Curve leverage: it can stop future vesting if yRisk falls short. A public review would let veCRV holders judge whether monitoring, reporting and response commitments were met, though Curve has not set a date for that checkpoint.</p><p>The arrangement puts people who built and ran a protocol that got exploited in charge of catching similar risks elsewhere. That could cut either way. Direct exposure to how a donation attack actually works may sharpen what yRisk looks for. It may also test whether governance under pressure, and near-unanimous votes, leave enough room to ask harder questions before funds move.</p> <![CDATA[Arbitrum DAO Approves New Ecosystem Incentive Proposal]]> Arbitrum DAO approved a new ecosystem incentive proposal. See what it funds, how past ARB grant programs performed, and what it means for treasury spending. https://daotimes.com/arbitrum-dao-approves-new-ecosystem-incentive-proposal/ 6a982defc8c43900013ab51f News Jamie Larson Wed, 02 Sep 2026 14:10:47 GMT <img src="https://daotimes.com/content/images/2026/09/chart3_incentive_programs.png" alt="Arbitrum DAO Approves New Ecosystem Incentive Proposal"><p>Arbitrum DAO voters approved a governance proposal on Snapshot directing treasury resources toward ecosystem incentive programs. The vote gives the community another round of funding to support builders, liquidity providers, and new apps on the network.</p><p>The proposal itself is procedural. It sets direction rather than releasing funds outright. Distribution will likely follow the staged structure Arbitrum has used before, with milestones, reporting requirements, and oversight before tokens move.</p><h3 id="a-familiar-playbook">A Familiar Playbook</h3><p>Arbitrum has run this experiment multiple times. The Short-Term Incentive Program launched in October 2023, distributing 50 million ARB to 29 projects. GMX took the largest grant, and Camelot won the most community votes. Demand outpaced the budget almost immediately.</p><p>A backfund vote followed in December 2023, adding 21.1 million ARB for 26 projects that missed the first cut. That pushed STIP&apos;s total past 71 million ARB. In January 2024, the DAO approved the Long-Term Incentives Pilot Program, worth 45.8 million ARB, with a five-member council added to screen applicants after STIP&apos;s rougher rollout.</p><p>By 2026, incentive spending had scaled further. The Arbitrum Expansion Program now includes a &#x24;215 million gaming catalyst fund, part of a broader push to bring app-specific chains onto Arbitrum&apos;s Orbit stack.</p><h3 id="why-the-dao-keeps-doing-this">Why The DAO Keeps Doing This</h3><p>Layer-2 competition has not slowed. Base, Optimism, Polygon, and a growing list of Orbit and Superchain networks all compete for the same builders and liquidity. Base alone now holds a larger share of L2 DeFi TVL than Arbitrum, according to recent DefiLlama-based estimates, even though Arbitrum still leads on raw TVL among single L2 chains in several trackers.</p><p>Incentives are one of the few tools a DAO can pull quickly. Grants can seed new protocols, deepen liquidity pools, and pull developers away from rival chains. Arbitrum&apos;s DAO treasury holds 42.78% of the total 10 billion ARB supply, giving it more firepower than most competing ecosystems.</p><p>That size is also the risk. A treasury this large invites scrutiny over how it gets spent.</p><h3 id="the-retention-problem">The Retention Problem</h3><p>Grant programs from 2023 and 2024 did not age well. Consulting firm Pink Brains reviewed Arbitrum&apos;s incentive history in April 2025 and found a pattern: activity spiked while rewards flowed, then dropped once programs ended. A survey the firm cited found only 21% of funded protocols tracked their own customer acquisition cost. None tracked user lifetime value.</p><p>Arbitrum&apos;s TVL data reflects the swings. Protocol TVL rose from &#x24;980 million to &#x24;1.42 billion between October 2023 and January 2024 during the STIP push, a 44.8% increase. It later peaked near &#x24;3.45 billion in December 2024 before falling to about &#x24;2.42 billion by April 2025.</p><p>The DAO has since pushed for stronger reporting requirements in newer programs, but the core question remains open: does subsidized activity survive once the subsidy ends.</p><h3 id="what-changed-since-then">What Changed Since Then</h3><p>Arbitrum&apos;s fee model has shifted in ways that matter for how future incentives get funded. Under the Arbitrum Expansion Program, Orbit chains that settle to a parent chain other than Arbitrum One send 8% of their revenue to the DAO treasury and 2% to a developer guild.</p><p>Robinhood Chain, an Orbit chain, generated &#x24;1.92 million in revenue and &#x24;1.462 billion in DEX volume in a single 24-hour period in late August 2026. The DAO treasury collected &#x24;175,612 from that chain in one day, and &#x24;531,641 over the trailing 30 days. That is a new, recurring revenue channel rather than a one-time token grant.</p><p>ARB reacted to the news directly. The token jumped roughly 30% around September 1, 2026, touching near &#x24;0.12 before pulling back toward &#x24;0.096 to &#x24;0.11, still up sharply from its 2026 low near &#x24;0.0702 in June.</p><h3 id="governance-participation-remains-thin">Governance Participation Remains Thin</h3><p>Arbitrum&apos;s DAO is large by treasury size, but voter turnout tells a different story. Industry-wide, the median governance proposal on Snapshot draws votes from just 2% to 4% of eligible token holders. A turnout above 10% is generally treated as strong in DAO governance broadly.</p><p>That leaves outcomes concentrated among a smaller group of delegates and large holders. Arbitrum has tried to address this with a governance participation program paying out ARB monthly to active voters, though the underlying apathy problem is common across most token-voting DAOs, not unique to Arbitrum.</p><h3 id="the-balance-ahead">The Balance Ahead</h3><p>Approval of this proposal does not guarantee good outcomes. It means the DAO chose to keep funding ecosystem growth through direct incentives, a tool it has used since 2023 with mixed retention results but improving revenue support behind it.</p><p>For ARB holders, the signal cuts two ways. Active governance shows the DAO still competes for builders and liquidity. But treasury spending only helps the token if funded projects generate activity that lasts past the reward period. The Orbit revenue share gives Arbitrum a funding source less dependent on emptying the treasury for every new push, which may ease that tension going forward.</p><p>The vote passed. What happens with the money now decides whether it mattered.</p> <![CDATA[Coinbase Will Suspend Badger DAO And Storj Trading On September 28]]> Coinbase suspends BADGER and STORJ trading on September 28, 2026. See what happens to balances, withdrawals, and why the delisting review stayed private. https://daotimes.com/coinbase-will-suspend-badger-dao-and-storj-trading-on-september-28/ 6a9412925a942b00016044a7 News Jamie Larson Sun, 30 Aug 2026 11:25:09 GMT <img src="https://daotimes.com/content/images/2026/08/chart1_badger_price_history.png" alt="Coinbase Will Suspend Badger DAO And Storj Trading On September 28"><p>Coinbase will halt trading for BADGER and STORJ on September 28, 2026, around 2 p.m. ET. The suspension covers Coinbase.com Simple and Advanced Trade, Coinbase Exchange, and Coinbase Prime. Customers keep their balances and can still withdraw both tokens after trading stops.</p><p>Coinbase announced the decision on August 28 through its Coinbase Markets account on X. The exchange said it regularly reviews listed assets against its internal standards. It gave no public detail on which technical, legal, or compliance factor triggered the review for either token.</p><h3 id="what-changes-before-september-28">What Changes Before September 28</h3><p>Both order books already sit in limit-only mode. Customers can place and cancel limit orders, and trades can still fill when a matching order appears. Market orders are off the table, which gives traders more control over price but no guarantee of execution.</p><p>The limit-only restriction applies across Coinbase&apos;s retail, professional, and institutional services. After the deadline, buying or selling BADGER and STORJ through Coinbase platforms stops entirely. Coinbase has not announced any automatic conversion program for leftover balances, unlike its earlier handling of the DAI stablecoin delisting, where eligible balances converted into USDS.</p><p>Withdrawals continue with no announced cutoff date. Customers can hold their tokens on Coinbase or move them to an external wallet that supports the underlying blockchain. Anyone transferring funds should confirm the receiving address and network before sending, since blockchain transactions cannot be reversed.</p><h3 id="two-very-different-dao-stories-behind-the-tokens">Two Very Different DAO Stories Behind The Tokens</h3><p>BADGER is the governance token of Badger DAO, a protocol built to bring Bitcoin-linked assets into DeFi through yield vaults called Setts. The DAO launched its mainnet in December 2020 without a traditional venture round, distributing tokens through retroactive airdrops instead.</p><p>Badger DAO&apos;s reputation never fully recovered from December 2021. An attacker compromised a Cloudflare API key and injected malicious code into the protocol&apos;s front end, tricking around 500 wallets into granting unlimited spending approvals. The theft totaled roughly &#x24;120 million in BTC and ETH, one of the largest DeFi hacks on record. The Badger team froze contract functions to stop further losses and later pursued a multi-stage governance plan to claw back and redistribute funds, a process that tested how far DAO voting can stretch under crisis conditions.</p><p>BADGER never returned to its February 2021 peak of &#x24;89.08. The token now trades near &#x24;0.35, a decline of more than 99% from that high, with a market capitalization around &#x24;6.9 million. It touched an all-time low near &#x24;0.31 to &#x24;0.34 in the weeks before the Coinbase announcement.</p><p>Storj tells a separate story. STORJ powers a decentralized cloud storage network where users pay to distribute encrypted file shards across independent nodes worldwide. Storj Labs raised &#x24;20 million in a 2017 ICO, and the current V3 platform has run since 2019.</p><p>Storj has kept building through the downturn. The project added GPU compute and a media production cloud, won a NAB Product of the Year award in 2025, and pushed its total value locked past &#x24;100 million. A July 2025 tokenomics update introduced buybacks and staking. None of that has moved the price. STORJ trades near &#x24;0.037 to &#x24;0.074 depending on the reporting window, down from a March 2021 high of about &#x24;3.86, a decline of roughly 97% to 99%. Its market cap sits between &#x24;16 million and &#x24;40 million against a peak near &#x24;1.6 billion.</p><h3 id="part-of-a-broader-cleanup">Part Of A Broader Cleanup</h3><p>BADGER and STORJ are not isolated cases this cycle. Coinbase already suspended five tokens in August: IDEX, LRC, OMNI, PIRATE, and FIS, with withdrawals left open in each case. IoTeX is scheduled to stop trading on September 23, days ahead of BADGER and STORJ.</p><p>Eight tokens have now been pulled from active trading across a roughly six-week window. Coinbase frames each case as a routine listing review, citing onchain and offchain signals under its published monitoring policy. The exchange has not disclosed volume or liquidity data showing how much of each token&apos;s global market it represents.</p><p>That omission matters for anyone judging the real effect of a delisting. A large exchange removing a market can widen spreads and reduce liquidity for the token&apos;s remaining venues. Without Coinbase&apos;s own numbers, outside observers can only see that BADGER and STORJ still trade on other centralized and decentralized platforms, subject to each venue&apos;s own rules.</p><h3 id="what-this-means-going-forward">What This Means Going Forward</h3><p>Coinbase has not announced an appeal process or a further review window for either token. The confirmed timeline runs through the September 23 IoTeX suspension and the September 28 cutoff for BADGER and STORJ. After that, withdrawals are expected to continue unless Coinbase issues a separate update.</p><p>For Badger DAO, the delisting adds to a five-year decline that started with the 2021 hack and never reversed. For Storj, it lands despite genuine product progress, a reminder that exchange listing decisions do not always track a project&apos;s operational momentum.</p> <![CDATA[Term Finance Shuts Down Meta Vaults For Good After $8.5 Million Governance Attack]]> Term Finance shut down its Meta Vaults for good after a $951 governance takeover drained $8.5 million in ETH and USDC from strategy vaults. https://daotimes.com/term-finance-shuts-down-meta-vaults-for-good-after-8-5-million-governance-attack/ 6a91c92c5a942b000160449a News Jamie Larson Fri, 28 Aug 2026 17:48:15 GMT <img src="https://daotimes.com/content/images/2026/08/dao-governance-attacks-2026.png" alt="Term Finance Shuts Down Meta Vaults For Good After &#x24;8.5 Million Governance Attack"><p>Term Labs has permanently closed every Term Meta Vault and stripped their DAO governance roles. The move follows an attack that drained roughly &#x24;8.5 million from the protocol&apos;s strategy vaults on August 23, 2026.</p><p>The shutdown cannot be undone. New deposits are blocked forever, though existing users can still withdraw. Term Labs has not said how much money is left, who gets paid back, or when.</p><h4 id="what-actually-happened">What Actually Happened</h4><p>An attacker spent about &#x24;951 to buy a controlling share of Term Labs&apos; governance tokens. That was enough to control four USDC strategy vaults and roughly 91% of the Ethereum Meta Vault. The attacker then submitted and voted through proposals that ordered the vaults to send funds to a wallet the attacker controlled.</p><p>Blockchain security firm PeckShield traced the haul to 2,843 ETH, worth about &#x24;6.87 million, plus 1.68 million USDC, later swapped for DAI. The attacker&apos;s starting capital, just 2 ETH, came through Tornado Cash. Term&apos;s vaults held about &#x24;12.45 million before the attack, meaning close to 68% of deposited funds left the protocol.</p><p>No smart contract bug caused this. Every transaction was a legitimate governance action approved by the address the protocol recognized as its own authority. The attacker simply became that authority for under &#x24;1,000.</p><h4 id="yearn-draws-a-line">Yearn Draws A Line</h4><p>Term&apos;s vaults ran on Yearn V3 infrastructure, but Yearn said the exploit hit a custom governance wrapper that Term Labs built on top, not Yearn&apos;s standard vault code. Yearn&apos;s own vault designs include strategist multisigs and guardian addresses that can pull a strategy in an emergency. Term&apos;s governance layer replaced those protections with token-weighted voting, and the token was thin enough that control cost less than a used bicycle.</p><p>Term Labs said its core lending business, the fixed-rate auction markets where borrowers and lenders match directly, was not touched. That business kept running through the incident.</p><h4 id="this-is-not-an-isolated-case">This Is Not An Isolated Case</h4><p>DefiLlama has classified five incidents in 2026 as governance attacks, adding up to &#x24;25.1 million in losses. The largest came in July, when an attacker spent about &#x24;4 million buying BONK tokens and passed a proposal draining roughly &#x24;20 million from BonkDAO&apos;s treasury. Only seven addresses voted.</p><p>Binance stopped a smaller attempt on August 18, catching a malicious proposal threatening &#x24;1.2 million at an unnamed DAO with two days to spare before execution.</p><p>The common thread across these cases is a governance token that has lost value while the protocol still holds real money. When buying 51% of the vote costs less than the treasury it controls, the protocol is exposed by math, not by a coding mistake. Term Labs&apos; token was thinly traded relative to a &#x24;12.45 million vault. BonkDAO&apos;s token had fallen from its highs while the treasury still held &#x24;20 million.</p><h4 id="fixes-that-existed-but-werent-used">Fixes That Existed But Weren&apos;t Used</h4><p>Time locks, which delay a passed proposal from executing for 24 to 48 hours, would have given the community a window to notice and react. Multi-signature requirements for large transfers would have added a second check beyond the vote itself. Minimum quorum rules would have made a takeover proportionally more expensive. Conviction voting, used by projects like Gardens and 1Hive, requires tokens to be staked for a period before gaining full voting weight, which blunts a buy-and-vote attack outright.</p><p>None of these were part of Term&apos;s custom governance wrapper. All are documented and available as open-source code.</p><h4 id="what-comes-next">What Comes Next</h4><p>Term Labs has not published a technical postmortem, named the security firms assisting with recovery, or set a date for either. No U.S. regulator has announced an investigation into the incident, and the SEC&apos;s existing DAO guidance predates this case by nearly a decade.</p><p>The bigger question sits with every other DAO running token-weighted governance over real treasury funds. The ratio between governance token value and protocol assets is rarely monitored, and nothing suggests Term Labs or BonkDAO were unique. August alone has produced over &#x24;27 million in DeFi losses across multiple attack types, and the gap between what these systems secure and how they&apos;re protected keeps widening.</p> <![CDATA[Solana Puts Its First Constitution And Money Supply To A Vote]]> Solana validators vote on a constitution, doubling disinflation to 30%, and a fee burn overhaul. See what SGP-0001, SGP-0002 and SGP-0003 mean for SOL supply. https://daotimes.com/solana-puts-its-first-constitution-and-money-supply-to-a-vote/ 6a8ddd320611310001c12478 News Jamie Larson Tue, 25 Aug 2026 18:23:23 GMT <img src="https://daotimes.com/content/images/2026/08/chart2_hbar.png" alt="Solana Puts Its First Constitution And Money Supply To A Vote"><p>Solana validators are casting the network&apos;s first onchain governance vote this week. Three proposals are on the ballot, and the outcome will decide how Solana sets rules, issues tokens, and prices transactions going forward.</p><p>Voting opened August 22 and runs through the end of epoch 1023, expected to close around 15:30 UTC on August 27. This is the first time Solana has run a formal, stake-weighted vote of this kind. The result will show whether the network&apos;s governance system actually works before it gets used again.</p><h3 id="three-proposals-one-ballot">Three Proposals, One Ballot</h3><p>The vote bundles three separate items, known as Solana Governance Proposals, or SGPs. Each is voted on independently, so one can pass while the others fail.</p><p>SGP-0001 is the Solana Constitution. It sets up a formal governance framework where voting power follows economic stake. Token holders can override the validators managing their delegated SOL, so a vote posted by a validator does not bind the underlying owner.</p><p>SGP-0002 would double Solana&apos;s annual disinflation rate from 15% to 30%. This does not cut inflation overnight. It speeds up how fast inflation falls toward the network&apos;s fixed terminal rate of 1.5%. Under the current schedule, Solana reaches that floor in roughly 5.7 years. Under SGP-0002, it would arrive in about 2.8 years, cutting projected issuance by an estimated 18.9 million SOL over six years.</p><p>SGP-0003 reworks how transaction fees are collected and burned. Today&apos;s flat 5,000-lamport fee splits between a burn and a payment to the block leader. The proposal replaces this with a smaller 2,500-lamport inclusion fee paid entirely to leaders, plus a separate usage-based resource fee that gets burned in full.</p><h3 id="why-these-proposals-reached-a-vote">Why These Proposals Reached A Vote</h3><p>Getting SGP-0002 and SGP-0003 onto the ballot required clearing a 15% staked-SOL signaling threshold first. Two validators did most of that work. Helius, which co-authored both proposals, backed them with roughly 16 million SOL. Jupiter added about 12.47 million SOL. Combined, that is more than the entire threshold on its own.</p><p>The fee proposal&apos;s stakes are visible in current burn data. Solana burns roughly 648 SOL a day under the existing structure. Once SGP-0003 reaches its terminal rate and network activity picks up, daily burns could climb to between 7,500 and 9,000 SOL. That is more than ten times today&apos;s rate.</p><h3 id="solana-company-votes-for-the-constitution-against-the-rest">Solana Company Votes For The Constitution, Against The Rest</h3><p>Not every institutional holder agrees with the pace of change. Solana Company, a Nasdaq-listed SOL treasury and staking firm trading as HSDT, published its voting positions on August 21. It backs SGP-0001 and opposes both SGP-0002 and SGP-0003.</p><p>Chairman and CEO Joseph Chee framed the objection around timing, not substance. He said institutions need consistent, predictable economic structures they can model over multi-year horizons. Reopening the inflation and fee schedule during governance&apos;s first cycle, in his view, works against that goal. Solana Company&apos;s own statement called both proposals reasonable in their long-term aims, lower issuance and fees that better track network resource use, while arguing the network needs more track record before changing them.</p><p>That split matters for how the vote reads once results land. A validator can support the governance system itself while rejecting the specific policy changes moving through it first.</p><h3 id="what-happens-if-the-proposals-pass">What Happens If The Proposals Pass</h3><p>Approval does not flip a switch. These are stake-weighted signaling votes. A pass establishes a mandate to proceed, but the inflation and fee changes still require separate technical implementation through the Solana Improvement Document process before taking effect on mainnet. Passing SGP-0001 alone will not change anything about issuance or fees.</p><p>To pass, a proposal needs participation from about one-third of active stake and support from two-thirds of the votes actually cast. Rejection of SGP-0002 or SGP-0003 leaves current inflation and fee rules untouched and does not affect SGP-0001&apos;s outcome either way.</p><p>Bitcoin.com News has reported separately that combining slower issuance with heavier fee burns could push Solana&apos;s annual supply growth from about 3.695% today toward roughly 1.1% by 2031, a rate below gold&apos;s approximate 1.8% annual supply growth. Most of that shift comes from SGP-0002 alone; the fee burn&apos;s contribution stays modest unless network activity, and the fees it generates, grows substantially first.</p><h3 id="what-this-means-for-governance-design">What This Means For Governance Design</h3><p>For anyone watching how DAOs and onchain governance systems mature, this vote is a working test case. Solana is running a constitution ratification and two economic policy changes through the same stake-weighted mechanism at once, with a built-in override for token holders against their validators.</p><p>The design has clear strengths: independent voting per proposal avoids forcing an all-or-nothing choice, and the holder-override rule limits the risk of validators voting against their delegators&apos; wishes. The weakness is concentration. Two validators supplied nearly all the stake needed to force a vote, which raises the question of how much signaling power sits with a handful of large operators versus the broader token holder base.</p> <![CDATA[Gnosis Chain Votes To Give Up Its Own Validators For Ethereum Security]]> GnosisDAO approved GIP-153, moving Gnosis Chain from its own validator set to an Ethereum rollup secured by the Ethereum Economic Zone framework. https://daotimes.com/gnosis-chain-votes-to-give-up-its-own-validators-for-ethereum-security/ 6a8b4e060611310001c1246a News Jamie Larson Sun, 23 Aug 2026 19:47:07 GMT <img src="https://daotimes.com/content/images/2026/08/chart2_l2_fragmentation.png" alt="Gnosis Chain Votes To Give Up Its Own Validators For Ethereum Security"><p>GnosisDAO approved GIP-153 on August 19, authorizing Gnosis Chain to move from a standalone layer one network into a ZK proven Ethereum rollup. The vote result was decisive: 123,158 GNO in favor, 115 against, 151 abstaining, from 54 voters. Total turnout reached 123,425 GNO, nearly 65% above the required quorum of 75,000 GNO.</p><p>The approval does not switch the network over immediately. It gives Gnosis developers a mandate to design the transition. The first version targets late 2026 or early 2027, depending on whether the required technology is ready by then.</p><h3 id="what-changes-under-the-proposal">What Changes Under The Proposal</h3><p>Gnosis Chain currently runs its own proof of stake system, with an independent validator set securing the network. After the shift, the chain will publish proofs and settle transactions on Ethereum instead, relying on Ethereum validators for economic security.</p><p>The existing Gnosis validator set will eventually retire. That also ends the staking subsidy the GnosisDAO treasury currently pays out. GIP-153 states that network fees would take over as the base of the system&apos;s economics.</p><p>The proposal&apos;s authors describe the current setup as hard to sustain. They say fee revenue covers only a small share of the chain&apos;s security costs, while GNO issuance dilutes non-stakers by about 2.3% a year. Those figures come from the proposal itself and are not independently verified. Still, the vote shows GNO holders accepted the direction and greenlit further work on it.</p><h3 id="the-problem-the-ethereum-economic-zone-is-meant-to-fix">The Problem The Ethereum Economic Zone Is Meant To Fix</h3><p>The Ethereum Economic Zone, or EEZ, is a rollup framework built by Gnosis and ZisK with Ethereum Foundation funding. It launched on March 29 at EthCC in Cannes. Gnosis cofounder Friederike Ernst framed the motivation bluntly at the time: Ethereum&apos;s issue isn&apos;t scaling, it&apos;s fragmentation, since every new L2 creates its own isolated liquidity pool and bridge setup.</p><p>That fragmentation is measurable. Ethereum now hosts more than 20 active L2 networks securing roughly &#x24;40 billion combined, and a new one has launched roughly every 19 days in recent years. Each operates its own liquidity, deployments and bridge infrastructure, leaving users to shuttle assets between disconnected environments.</p><p>EEZ aims to remove that friction by letting participating networks access Ethereum contracts and liquidity synchronously, without a conventional bridge for every interaction. Under the design, a contract on Gnosis could call an Ethereum contract and use the result within a single transaction. Early backers of the framework include Aave, Centrifuge and a Swiss based EEZ Alliance.</p><p>Gnosis Chain is set to become the first production instance of this framework. Developers expect applications, account balances, contract addresses and the chain identifier to stay the same, so users would not need to migrate anywhere. RPC endpoints may change, and the treatment of the network&apos;s dollar pegged gas token still needs a final decision.</p><h3 id="the-first-version-will-still-rely-on-a-centralized-sequencer">The First Version Will Still Rely On A Centralized Sequencer</h3><p>The initial rollout will not include every feature in the long term design. Ernst said the first network will use a centralized sequencer because of current technical limits. A forced inclusion system, which would let users submit transactions through Ethereum if a sequencer censors or stalls, will also be missing at launch.</p><p>&quot;In the first version, there will be no forced inclusion, but this will be added asap,&quot; Ernst said during the governance discussion. That is a stated intention, not a delivered safeguard. No specification, delivery date or fallback period for forced transactions has been finalized yet.</p><p>This matters because a centralized sequencer creates a single point of censorship or downtime risk, a limitation shared across much of Ethereum&apos;s current rollup ecosystem. So the transition swaps Gnosis Chain&apos;s own validator model for a design that inherits Ethereum settlement, while initially keeping centralized control over transaction ordering. Its real security profile will depend on the eventual proof design, upgrade controls and escape hatch.</p><h3 id="timeline-still-depends-on-unfinished-technology">Timeline Still Depends On Unfinished Technology</h3><p>The first EEZ version targets genesis around the end of 2026 or start of 2027. GIP-153 estimates this release would deliver about 80% of the intended synchronous composability, while needing 40% to 50% of the total engineering work. A complete EEZ specification is expected sometime in 2027, though both dates remain targets rather than commitments.</p><p>Before deployment, developers still need to finalize the proving system, fee token design, settlement contracts and operational structure. The planned network would run on two second blocks, against Ethereum&apos;s roughly 12 second slots, and only blocks aligned to an Ethereum slot could interact synchronously with mainnet. Gnosis would also have to follow Ethereum through any chain reorganization, tying its finality to Ethereum&apos;s own.</p><p>GIP-153 requested no DAO funding for this phase. Additional proposals may be needed later if implementation requires treasury money or protocol parameter changes. Until technical specifications, test deployments and a concrete launch plan appear, GIP-153 represents approval of a direction, not a finished transition.</p> <![CDATA[Binance Catches A DAO Governance Attack Before It Could Execute]]> Binance stopped a $1.2 million DAO governance attack before it could execute, after BonkDAO lost $20 million to the same tactic in July. https://daotimes.com/binance-catches-a-dao-governance-attack-before-it-could-execute/ 6a8725ab0611310001c12457 News Jamie Larson Thu, 20 Aug 2026 16:06:26 GMT <img src="https://daotimes.com/content/images/2026/08/dao-times-chart-treasury-incidents.png" alt="Binance Catches A DAO Governance Attack Before It Could Execute"><p>Binance said on Aug. 18 that its security team stopped a malicious governance proposal aimed at a DAO before any funds moved. The proposal targeted about &#x24;1.2 million in treasury tokens. Binance found the issue before any outside security firm flagged it.</p><p>Less than 48 hours remained before the proposal could take effect. Binance did not name the project or the token. Once its team found the threat, it contacted the project directly and asked other exchanges listing the token to pause deposits.</p><p>The project&apos;s community then voted the proposal down. That vote closed the window before the attacker could move any funds. No user or treasury losses were reported in this case.</p><h3 id="how-the-attack-was-built">How The Attack Was Built</h3><p>DAOs let token holders vote on treasury spending, upgrades, and other decisions. That system depends on one assumption: no outside party can cheaply gather more voting power than the people who show up to vote against them.</p><p>The attacker in this case used a weak point in the DAO&apos;s voting rules rather than a code flaw. Binance security chief Jimmy Su said many attacks now target people and access instead of smart contracts. He said the response shows security work now reaches past the exchange&apos;s own walls, into the projects that list on it.</p><p>Governance attacks do not need a hack. They need cheap voting power, low turnout from honest holders, and a proposal written to pass without close reading. When those three line up, the treasury moves through rules that worked exactly as designed.</p><h3 id="the-bonkdao-precedent">The BonkDAO Precedent</h3><p>This case follows a near-identical attack on BonkDAO in July, which was not stopped in time. On July 6, an attacker spent about &#x24;4.4 million buying BONK tokens on exchanges including Bybit and Binance.</p><p>That purchase gave the attacker enough tokens to meet BonkDAO&apos;s 1% quorum threshold. Only seven wallets voted on the resulting proposal, Bonk Improvement Proposal #76. The attacker&apos;s wallets held about 99.9% of votes cast.</p><p>The proposal passed and authorized a transfer of roughly 4.4 trillion BONK, worth about &#x24;20 million, straight to the attacker&apos;s wallet. BONK&apos;s price fell more than 9% within hours. Upbit and Kraken paused deposits and withdrawals of the token.</p><p>BonkDAO had no timelock separating approval from execution, and no multisig backstop on large transfers. Security firm Halborn said any one of those controls could have broken the attack. Their absence together meant &#x24;4.4 million was enough to take close to &#x24;20 million.</p><h3 id="a-third-pattern-the-bridge-hack">A Third Pattern: The Bridge Hack</h3><p>A separate case at KelpDAO shows a different route into the same problem. Chainalysis reported hackers took about &#x24;292 million from KelpDAO&apos;s bridge, not through a governance vote but through a bridge exploit.</p><p>Quick action after that theft blocked another &#x24;95 million and froze thousands of ETH tied to the attacker. The KelpDAO case shows DAOs face both governance risk and infrastructure risk, and that fast coordination after an incident can still recover much of what would otherwise be lost.</p><h3 id="the-compliance-machine-behind-the-catch">The Compliance Machine Behind The Catch</h3><p>Binance said it spends close to &#x24;300 million a year on compliance work, with almost 1,500 staff in related roles. The exchange said its checks caught &#x24;10.53 billion in fraud or unusual activity from 2025 into early 2026.</p><p>That scale extends past Binance&apos;s own platform. The FBI&apos;s Operation Level Up told more than 8,000 people they may be crypto fraud victims by December 2025, most of whom did not know they were targeted. The agency said its tips likely stopped about &#x24;511.5 million in losses.</p><h3 id="what-this-means-for-daos">What This Means For DAOs</h3><p>The pattern across BonkDAO, KelpDAO, and this latest case is the same: token-weighted governance is only as safe as the cost of buying a temporary majority. When a token is liquid and voter turnout is low, that cost can fall below the treasury it protects.</p><p>Exchange-side detection worked this time because Binance moved before the vote closed and coordinated with other platforms to freeze the attacker&apos;s exit routes. That is a real backstop, but it depends on an exchange spotting the threat first, which did not happen with BonkDAO.</p><p>DAOs that want to avoid becoming the next case need their own defenses: quorum floors that scale with treasury size, timelocks between approval and execution, and multisig control over large transfers. Relying on an exchange to catch what a DAO&apos;s own rules should have stopped is not a strategy. It is a fallback that worked once.</p> <![CDATA[Aave Liquidity Stays Deep In A Hole Four Months After KelpDAO]]> Aave TVL has fallen 43% since the KelpDAO hack in April 2026. Here's what happened, why deposits haven't returned, and how Aave compares to Morpho and Spark today. https://daotimes.com/aave-liquidity-stays-deep-in-a-hole-four-months-after-kelpdao/ 6a84cf14a9a270000146a0b5 News Jamie Larson Tue, 18 Aug 2026 21:32:57 GMT <img src="https://daotimes.com/content/images/2026/08/defi-lending-rankings.png" alt="Aave Liquidity Stays Deep In A Hole Four Months After KelpDAO"><p>Aave&apos;s total value locked sits at &#x24;14.9 billion today, down 43% from the day North Korean hackers drained KelpDAO in April. The protocol never rebuilt the deposits it lost, even after fixing the technical damage within weeks.</p><p>The number tells a simple story. Users pulled billions out of Aave and most have not come back. TVL now sits 67% below its 52-week high of &#x24;45.9 billion, reached in October 2025.</p><h4 id="what-happened-at-kelpdao">What Happened At KelpDAO</h4><p>KelpDAO is a liquid restaking service. Users deposit ETH, KelpDAO stakes it on Ethereum, and depositors get a tradeable receipt token called rsETH in return. Aave accepted rsETH as loan collateral.</p><p>In mid-April, hackers linked to North Korea broke KelpDAO&apos;s cross-chain bridge and stole roughly &#x24;290 million. LayerZero, the bridge&apos;s software provider, blamed North Korea within 48 hours. Outside investigators, including Chainalysis, later confirmed the attribution to a cluster known as TraderTraitor, tied to the Lazarus Group.</p><p>The attackers took the stolen rsETH straight to Aave. They deposited it as collateral and borrowed real ETH against it. Because rsETH&apos;s backing was compromised, the collateral was worth far less than the loans it secured. Aave and Compound were left holding roughly &#x24;246 million in combined bad debt, with Aave absorbing about &#x24;200 million of that figure.</p><p>Aave&apos;s own contracts were never breached. Its report on the incident states that oracles, liquidations and lending logic worked as designed. The damage came entirely through its acceptance of a bridge-dependent asset that turned out to be exploitable elsewhere.</p><h4 id="the-response-was-fast-the-confidence-loss-was-not">The Response Was Fast, The Confidence Loss Was Not</h4><p>Aave acted quickly once the theft was confirmed. It force-liquidated the attacker&apos;s positions on Ethereum and Arbitrum by May 6. A coalition called DeFi United pledged enough ETH to restore rsETH&apos;s backing, with replacement collateral flowing in through tranches into late May. By late May, Aave declared every market back to normal.</p><p>The balance sheet fix worked. The trust problem did not follow the same timeline.</p><p>Within two days of the hack, Aave&apos;s deposits fell by more than &#x24;8 billion. Stablecoin pools hit 100% utilization, freezing billions in crypto dollars with no room for other users to withdraw. That liquidity crunch, more than the bad debt itself, appears to be what pushed depositors toward the exits.</p><p>TVL kept draining through May and into June, bottoming near &#x24;11.9 billion before a partial recovery began. Aave has clawed back to &#x24;14.9 billion since, a 5.6% gain over the past 30 days, but that remains far short of pre-hack levels.</p><p>The AAVE token followed a similar path. It fell about 20% the day after the theft, from roughly &#x24;115 to below &#x24;92. It trades near &#x24;89 today, still below where it stood before the hack.</p><h4 id="why-tvl-matters-beyond-a-headline-number">Why TVL Matters Beyond A Headline Number</h4><p>TVL is not an abstract scoreboard for a lending protocol. It represents the actual dollar value of deposits available for borrowers to draw against. A pool worth 43% less has that much less capacity to lend, and what remains moves with more volatility.</p><p>Aave ended 2025 with &#x24;55 billion in TVL, more than half of the entire DeFi lending sector at the time. Losing tens of billions in deposits does not just shrink one protocol. It shrinks the liquidity base the wider lending market depends on.</p><p>Despite the drop, Aave still leads DeFi lending by a wide margin. Morpho, the next-largest lending protocol, holds about &#x24;8.1 billion, roughly half of Aave&apos;s current total. Spark, Maple, and Compound trail further behind. The KelpDAO fallout pushed some users toward these smaller platforms, viewed as carrying less bridge-related risk, but none has come close to matching Aave&apos;s scale.</p><h4 id="an-unresolved-legal-tail">An Unresolved Legal Tail</h4><p>The hack also produced a dispute that has nothing to do with code. Protos has reported that Aave dismissed a restraining notice tied to rescued funds, and on-chain analysts have flagged possible links between the KelpDAO attackers and prior hacks at Bybit and BTC Turk. A related court battle over roughly &#x24;71 million was still active as of early June, months after the exchanges and collateral positions were technically resolved.</p><h4 id="the-honest-read">The Honest Read</h4><p>Aave passed the stress test that matters most for a lending protocol. Its liquidation engine worked, no user with healthy collateral lost funds, and the bad debt was covered without a token bailout or a protocol pause. That is a real point in its favor.</p><p>What it could not do is stop depositors from leaving once trust cracked. Four months on, the gap between Aave&apos;s engineering response and its capital recovery is the actual story here, not the hack itself.</p>