RIADeFi
RIADeFi

On-chain events

Security incidents, control changes, governance votes, upgrades, launches, and closures, each with its primary sources. Confirmed facts are listed apart from open claims.

348 eventsJSONRSS
  1. · Market stress · Recovery reported

    Base recovered from mainnet transaction delays caused by missed blocks

    For a time, Base mainnet did not include transactions on schedule. Bridge deposits, proofs and other Base transactions could have been delayed, though Ketju identified no delayed bridge transaction.

  2. · Governance · Proposed

    Lido proposes six operator types for CMv2 and gives its committee power to score operators

    If adopted and applied, the rules would set formal operator types. The committee could set the scoring parameters and thresholds for each round, which would affect how Lido treats operators afterward.

  3. · Economic change · Proposed

    Lido proposed NEST, a system that would buy LDO with staking revenue

    If a later on-chain vote launches NEST and the DAO funds it, NEST would trade for the treasury every day.

  4. · Control change · Proposed

    Lido proposed replacing its expiring GateSeals with a permanent CircuitBreaker

    If executed, pausers would keep their authority by sending regular heartbeat transactions.

  5. · Governance · Proposed

    Lido votes on keeping Pier Two as an operator after Bitmine bought it

    An existing node operator now has a new parent company, and Lido governance is deciding whether it should stay.

  6. · Control change · Proposed

    Lido proposes raising its liquidity committee's stETH transfer limit to 8,000 from 6,000

    If a later Aragon vote implements it, the multisig's stETH limit would rise from 6,000 to 8,000 stETH every six months. The multisig would also be able to pay up to $8 million in stablecoins every six months.

  7. · Economic change · Proposed

    Lido Earn proposal would let EarnETH cover Kelp losses below its 1% threshold

    If approved, EarnETH could use its first-loss backstop below the usual threshold for this incident, but only after other coverage is counted.

  8. · Control change · Proposed

    Steakhouse plans to move Morpho BTC and ETH markets to SVR MetaOracles with backup feeds

    The planned design adds SVR prices delivered through a private auction, standard Chainlink fallbacks and backup prices for the exact collateral where they exist.

  9. · Security incident · Confirmed · Critical

    Kelp rsETH bridge exploit led Aave to freeze V3 reserves on several chains

    The Aave Protocol Guardian and Risk Steward froze the rsETH and wrsETH reserves and changed WETH interest rates on the affected deployments.

  10. · Upgrade or migration · Confirmed · Developing

    OP Labs released required op-challenger security update v1.9.1

    A fixed official version is now available for the challenger software, which the fault-proof process needs to secure challenged withdrawals.

  11. · Upgrade or migration · Proposed

    Steakhouse plans to have its Morpho V2 vaults lend to markets directly

    The plan removes one layer of vaults from the lending path. Steakhouse must make many curator changes across its V2 vaults.

  12. · Control change · Confirmed · Developing

    Lombard publishes the design of Bitcoin Smart Accounts that issue BTC.b

    Ketju now has a primary source for how this form of BTC.b works.

  13. · Governance · Proposed

    Aave voters considered listing USSD on its Sonic market

    If governance advances and executes the proposal, Aave Sonic would hold a new stablecoin.

  14. · Control change · Proposed

    Lido proposes a 5-of-9 Curated Module Committee to replace LNOSG

    If approved and set up, a 5-of-9 multisig committee would get limited on-chain permissions for penalties, parameter updates, registry management and operator administration.

  15. · Economic change · Proposed

    Lido proposal would reroute DVT and APM incentives to Lido Earn and a liquidity multisig

    If Lido implements it, the Lido Earn treasury and a liquidity structure linked to the Growth Committee would receive and manage these incentives.

  16. · Control change · Proposed

    Lido proposes a new CSM operator type for four-person DVT clusters

    If it ships with CSM v3, qualifying clusters would get their own bond, reward, priority-queue, strike and monitoring terms. A committee would run their onboarding.

  17. · Control change · Proposed

    Lido proposes version 3.0 of its DAO Ops multisig policy

    If approved, a signer rotation would no longer need to keep a simple majority of the original signers. Static signers would lose their protected status. Lido would remove the seven-day objection period for rotations.

  18. · Control change · Proposed

    Lido Alliance BORG asks to raise its Easy Track transfer limit to $5 million

    If it executes, the limit would rise from $250,000 every three months to $5 million every six months, which greatly raises how much the foundation can draw through Easy Track.

  19. · Launch or access · Live launch

    Aave v4 launched on Ethereum with three Liquidity Hubs

    The launch created a live lending market in which Hubs hold the shared liquidity and Spokes set the collateral, risk-premium and liquidation rules.

  20. · Governance · Proposed

    Aave temperature check proposes adding USSD to Aave v3 on Sonic

    Aave governance is now reviewing USSD and its reserves, minting, redemption, custody and cross-chain systems. Live Aave parameters have not changed.

  21. · Security incident · Postmortem · Critical

    Attackers mint 80 million unbacked USR after taking Resolv's signing key

    Resolv shut down its backend, paused the affected contracts, and revoked and replaced the compromised credentials.

  22. · Security incident · Postmortem · Critical

    Aave CAPO error liquidates 10,938 wstETH from 34 healthy accounts on March 10, 2026

    The faulty update briefly changed the oracle price used for liquidations.

  23. · Launch or access · Live launch

    sky.money launched USDT Savings and USDS Flagship vaults on Morpho

    The launch created new products that advisors could access, which combine Sky savings with Morpho curator and allocator risk.

  24. · Control change · Proposed

    Lido governance considers keeping Stakin as an operator after The Tie bought it

    A Lido node operator now has a new owner and will send rewards to a new address. Governance must decide whether it stays, and a later on-chain registry update would follow.

  25. · Governance · Proposed

    Aave ARFC proposes a new Aave v3 market on X Layer with nine assets

    Aave governance is now formally reviewing an Aave market on X Layer, with its collateral, cross-chain links, oracles, caps and liquidation settings.

Scope

Ketju lists an event here when it can change a Ketju memo, a position a client holds, something that position depends on, or the records an advisor should keep. Each entry names the stage the event has reached: reported, proposed, approved, executed, contained, recovered, or explained in a postmortem.

Corrections

Ketju never edits a published version. A recovery, a postmortem, a corrected loss figure, or a changed reading becomes a new version at the same address, and every earlier version stays in the JSON file.

Educational research for financial professionals. Not investment, legal, tax, or compliance advice. An event here does not mean a product is suitable or approved.