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. · Control change · Approved, not executed

    Lido Snapshot cuts the CSM key-removal charge to 0.02 ETH and lets CSM grow to 3% of stake

    The vote authorized a later cut in the charge for removing queued validator keys. It set conditions under which CSM can receive a larger share of Lido stake.

  2. · Economic change · Approved, not executed

    Aave approves stS collateral terms for Sonic with a 30 million cap

    The proposal moved to the AIP stage with set collateral, liquidation, cap, oracle and E-Mode terms.

  3. · Market stress · Postmortem

    Base cuts block sizes to a third of target for three hours after a batcher backlog

    For about three hours, mainnet capacity fell to about one-third of its target, and users might have had to resubmit dropped transactions.

  4. · Economic change · Executed

    Aave turns on Chainlink SVR for four Ethereum markets

    The four markets now use SVR price feeds, which auction the value that liquidators can take from oracle updates through MEV systems.

  5. · Governance · Proposed · Developing

    Lido opened a vote on recognizing new Starknet wstETH bridge endpoints

    The vote opened a way to restore canonical status after the legacy token migration and an earlier offboarding.

  6. · Governance · Proposed · Developing

    Aave moved its proposed lisUSD listing on BNB Core to ARFC review

    lisUSD entered Aave's formal listing and risk review. The proposal would add a new stablecoin reserve if it later passed the ARFC and on-chain governance.

  7. · Upgrade or migration · Proposed · Developing

    Lido Snapshot backs LIP-27 upgrade for Ethereum's Pectra hardfork

    The plan would raise the consensus versions of Lido's Accounting, Validator Exit Bus and CSM oracles and replace the CS Verifier. A later step would revise the Oracle Report Sanity Checker parameters.

  8. · Control change · Proposed · Developing

    Lido votes to manage its MEV relay list through Easy Track

    Under the design, Easy Track's EVMScriptExecutor would manage the list and the Relay Maintenance Committee would be the trusted caller.

  9. · Governance · Proposed · Developing

    Arbitrum DAO votes on custom USDS and sUSDS gateways in its bridge router

    Governance can now route the two Sky tokens through their own custom gateways in the official interface, in place of the default gateways.

  10. · Upgrade or migration · Proposed · Developing

    Optimism votes on Upgrade 13 with OPCM, fault-proof fixes and a Pause Deputy

    The proposal would change how L1 upgrades run, how withdrawal proofs are checked and how dispute games recover. It would also let a named Pause Deputy trigger the withdrawal pause across the Superchain.

  11. · Launch or access · Proposed

    Aave proposal 257 would launch Aave v3.3 on Sonic with USDC, WETH and wS

    The deployment plan became an executable on-chain proposal. It sets initial collateral, borrowing, caps, liquidation parameters, oracles and the admin roles for the launch period.

  12. · Upgrade or migration · Proposed

    Optimism proposed Upgrade 12 to make OP Stack chains ready for Pectra

    Optimism put a maintenance payload and an upgrade requirement for operators into governance.

  13. · Economic change · Proposed · Critical

    Aave proposes raising AAVE collateral LTV by 3 points on Ethereum and Arbitrum

    The proposal would raise AAVE's LTV on Ethereum Core from 66% to 69% and its liquidation threshold from 73% to 76%. On Arbitrum, it would raise LTV from 63% to 66% and the liquidation threshold from 70% to 73%.

  14. · Control change · Executed

    Aave turned on automated supply and borrow cap changes on Arbitrum

    Chaos Labs Edge recommendations can now pass through a RiskOracle and the AaveStewardCapsInjector to an AGRS contract that holds RiskAdmin authority.

  15. · Upgrade or migration · Executed

    Aave upgraded every active v3 instance to v3.3

    The upgrade replaced the pool, configurator and pool-data-provider implementations.

  16. · Launch or access · Proposed

    Aave TEMP CHECK proposes an Aave v3 market on MegaETH

    MegaETH is now in Aave's formal process for new deployments, so Ketju may need to review it later.

  17. · Control change · Approved, not executed · Developing

    Sky passed an emergency executive that cut its pause delay to 18 hours and loosened LSE-MKR-A

    The approved spell would cut the GSM Pause Delay from 30 hours to 18 hours.

  18. · Upgrade or migration · Approved, not executed

    Axelar approved the v1.2.1 upgrade that burns transaction fees

    The approved software keeps the community-tax share of transaction fees in the community pool and burns the rest. Before, the rest went to token holders.

  19. · Governance · Approved, not executed

    Lido Snapshot vote approves a Cayman Islands Ecosystem BORG Foundation

    The vote authorized an entity to oversee the Rewards Share and Liquidity Observation Lab multisigs.

  20. · Control change · Approved, not executed

    Lido tokenholders approve the Lido Labs BORG Foundation with 56.8 million LDO

    The vote allows Lido to form an entity that would oversee, under law, committees and multisigs including GateSeal, Emergency Brakes, Relay Maintenance, Treasury Management, and the Simple DVT and Community Staking…

  21. · Governance · Approved, not executed

    Lido lets Attestant keep operating validators after Bitwise bought it

    Lido accepted Bitwise as Attestant's new ultimate owner without requiring validator exits or removing the operator.

  22. · Governance · Approved, not executed

    Lido lets Solstice keep running Bridgetower's validators after the purchase

    Lido accepted Solstice as the operator's new corporate owner and planned to rename Curated Module operator number 17.

  23. · Economic change · Proposed

    Aave moved pufETH collateral for Ethereum Core to a Snapshot vote

    If Aave later approves and executes it, Ethereum Core would accept a liquid restaking token as collateral.

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.