RIADeFi
The Ledger

The events that can change an advisor’s diligence file.

Incidents, control changes, governance, upgrades, launches, and closures, from primary evidence. Confirmed facts are kept apart from open claims.

287 eventsJSONRSS
  1. · Control change · Proposed

    Lido proposes replacing GateSeals with a permanent CircuitBreaker

    If executed, pausers could maintain authority through periodic heartbeat transactions, pause assigned contracts independently, and retain authority over other assigned contracts after using one pause.

  2. · Control change · Proposed

    Lido proposes higher Easy Track transfer authority for its liquidity committee

    If implemented through the stated later Aragon vote, the multisig's stETH transfer ceiling would rise from 6,000 to 8,000 stETH per six months and it would gain a stablecoin payment path capped at $8 million per six…

  3. · Control change · Proposed

    Steakhouse announces SVR MetaOracle migration for Morpho markets

    The announced target design adds private-auction SVR delivery, standard Chainlink fallback paths, exact-collateral backup pricing where applicable, a 2% deviation trigger, a two-hour challenge timelock, and an…

  4. · Control change · Confirmed · Developing

    Lombard details Bitcoin Smart Account controls for BTC.b

    The primary diligence record now identifies the pre-signed Bitcoin spending paths, Ethereum Smart Account Registry, Token Operator, TEE-based Arbitration Oracles, unilateral exit route, and liquidation-driven reserve…

  5. · Control change · Proposed

    Lido proposes Curated Module Committee with delegated operating authority

    If approved and implemented, a dedicated 5-of-9 multisig committee would receive bounded on-chain permissions for penalties, parameter updates, registry management, and operator administration.

  6. · Control change · Proposed

    Lido proposes Identified DVT Cluster operator class for CSM

    If implemented with CSM v3, qualifying clusters would receive distinct bond, reward, priority-queue, strike, monitoring, and committee-administered onboarding treatment.

  7. · Control change · Proposed

    Lido proposes DAO Ops Multisigs Policy 3.0

    If approved, signer rotations would no longer have to preserve a simple majority of original signers, static signers would lose protected status, and the existing seven-day rotation objection period would be removed.

  8. · Control change · Proposed

    Lido proposes higher Alliance BORG Easy Track transfer limits

    If executed, the limit would rise from $250,000 per three-month period to $5 million per six-month period, materially increasing the amount accessible through the delegated Easy Track path.

  9. · Control change · Proposed

    Lido considered Stakin's continuation after acquisition by The Tie

    The acquisition introduced new ownership and reward-routing context for a node operator in Lido's curated infrastructure.

  10. · Control change · Approved, not executed

    Lido approves Rewards Share Committee reform

    The approved mandate expands the committee's operational role in allocating approved rebates and executing treasury-funded stVault reward payments within DAO-approved budgets.

  11. · Control change · Proposed · Developing

    Rocket Pool proposes defaulting Smart Node minipools to the latest delegate

    The proposal would increase governance's practical ability to propagate approved minipool logic through the supported Smart Node path and reduce delegate-version fragmentation.

  12. · Control change · Approved, not executed

    Lido approves SEAL Safe Harbor exploit-response framework

    Governance approved a civil safe-harbor path for whitehats responding to active exploits, a 10% bounty capped at $2 million, return of recovered assets to the Aragon Voting contract, and temporary 4-of-5 committee…

  13. · Control change · Proposed · Developing

    Optimism proposes DAB on-chain controls MVP

    A concrete governance proposal now defines a possible on-chain control model in which the Security Council holds the Governor admin role and Token House authority becomes enforceable through an authorizedProposer role.

  14. · Control change · Executed

    Aave executes Slope2 Risk Oracle activation

    The approved risk-oracle and steward path became operative for Slope2 updates. Covered Ethereum assets include WETH, USDC, USDT, and USDe; covered Linea assets include WETH, USDC, and USDT.

  15. · Control change · Approved, not executed

    Spark approves Liquidity Layer relayer and freezer multisig changes

    The approved Core Operator Relayer configuration becomes 2-of-5 across two Amatsu signers, two Spark Assets Foundation signers, and one Phoenix Labs signer.

  16. · Control change · Approved, not executed

    Lido approves bridge-partnership authority framework

    The approved framework delegates partnership execution, establishes a Bridging Security Committee with approval and veto authority, and removes the prior five-day DAO objection period after NEC publication.

  17. · Control change · Approved, not executed

    Lido approves Validator Exits SNOP v3

    The approved standard incorporates triggerable withdrawals, expands applicability to Simple DVT, Community Staking, and future modules, and clarifies node-operator exit, configuration, responsiveness, and reporting…

  18. · Control change · Executed

    Lido activates triggerable withdrawals on Ethereum mainnet

    Lido gained an execution-layer path for initiating validator exits without relying exclusively on a node operator to cooperate, adding permissionless exit enforcement and new validator-exit control components.

  19. · Control change · Approved, not executed

    Lido approves the stVaults Committee and delegated parameter authority

    The DAO approved a delegated control body and defined its intended authority over material stVault economic and risk parameters.

  20. · Control change · Approved, not executed

    Aave approves dynamic CAPO calibration at the ARFC stage

    The approved design would replace infrequent manual calibration with bounded off-chain recommendations and on-chain updates affecting the maximum recognized exchange-rate growth of yield-bearing collateral.

  21. · Control change · Proposed

    Aave proposes automated cap controls on four additional networks

    If executed, whitelisted reserve caps on four additional deployments could be changed through off-chain Edge recommendations, RiskOracle contracts, injector automation, and newly assigned RISK_ADMIN roles.

  22. · Control change · Approved, not executed

    Aave approves expanded automated and manual risk-steward authority

    The approved payload would grant RISK_ADMIN authority to new steward contracts, permit automated discount-rate recommendations through Edge Risk Oracle infrastructure, and allow constrained manual e-mode and Pendle…

  23. · Control change · Approved, not executed

    Lido approves intra-operator DVT rules for Curated Module operators

    Operators may split up to the lesser of 1,000 or 20% of active validator keys after testnet validation, add DVT keys produced through vetted verifiable DKG, and participate under revised provider-incentive allocations.

  24. · Control change · Approved, not executed

    Lido approves replacing Kyber with Caliber in its oracle set

    The approved path changes the entity responsible for one oracle-set position while preserving the seat rather than removing it and adjusting quorum.

  25. · Control change · Executed

    Aave activates nine additional SVR oracles on Ethereum Core

    The affected liquidations now use SVR feeds intended to recapture oracle-extractable value through the existing SVR steward and price-similarity validation process.

How to read this ledger

An event appears here when it can change a Ketju research file, a position a client holds, something that position depends on, or the evidence 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 and developing events

A published version never changes. A recovery, a postmortem, a corrected loss figure, or a changed reading creates a new version at the same address, and every earlier version stays in the JSON ledger.

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