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.
Aave voters cut the Risk Steward delay to 36 hours and moved Umbrella pause power to the Guardian
The approved design cuts the minDelay for some Risk Steward settings from 72 hours to 36 hours. It gives the Aave Protocol Guardian the power to pause and unpause Umbrella.
Lido contributors propose a permissionless CSM for 0x02 validators of up to 2,048 ETH
Lido governance is now discussing a full design, with proposed bond, fee, penalty, capacity, queue and delegated-role parameters.
Optimism Foundation proposes Token House-only voting while the Citizens' House is paused
If approved, the governance process would put all voting in the token-weighted Token House while the Citizens' House is paused. The proposal states that removing provisions needs Token House approval at a 51% threshold.
Base mainnet halted on June 25 and again on June 26
Base suffered an actual chain outage that affected deposits, withdrawals, block production and client software. Node operators had to restart affected nodes to resume syncing, and the halt happened again the next day.
Spark voters approved a three-day timelock and guardian for its Avalanche governance bridge
The approved design adds a delay before governance actions take effect and lets a guardian multisig cancel actions during that delay.
Blockscape reports Lido validator outage after its failover failed
Blockscape restored the cluster with new Vouch and MikroTik instances and paid for missed rewards. It committed to test a Vouch design that runs several instances across providers.
Aave voters backed listing stcUSD on MegaETH at 88% LTV
The approved ARFC sets a 10 million supply cap and an isolated stablecoin E-Mode with an 88% LTV, a 90% liquidation threshold and a 4% liquidation bonus.
Lido tokenholders vote 55.1 million LDO to add Nemo to the Lido Labs board
The community vote moves forward a change in who oversees the foundation that builds and helps maintain Lido.
Lido DAO approves the design of Staking Router v3
The approved design counts validator balances instead of validator numbers and supports validators of up to 2,048 ETH.
Lido DAO approves LIP-33 design for Curated Module v2 and CSM v3
The approved design adds 0x02 withdrawal credentials, large validators, new bond and penalty rules, finer-grained roles and weighted allocation in the Curated Module. It proposes that CSM hold at most 15% of stake.
Lido DAO approves early wind-down of 72 Simple DVT clusters
The plan moves regular-cluster operators to CSM and other ways to keep operating. It authorizes grants paid from an existing allocation.
Lido DAO withdraws recognition from stETH bridges on nine networks
Lido now recognizes fewer networks for stETH and wstETH. The Network Expansion Committee, which already recognized endpoints, can now also withdraw recognition.
OP Labs patches a critical fault-proof bug in kona
A patched client is available, and OP Labs made it required for Upgrade 19. Upgrade 19 is meant to make kona-client the main fault-proof program.
Rocket Pool voters approved RPIP-81, cutting node-operator RPL rewards to 50%
The policy cuts the node-operator share before Saturn 2 from 70% to 50% and raises the pDAO share to 47.5%. After Saturn 2, it calls for 2.5% annual inflation with 95% of rewards going to the pDAO.
Axelar gives one address admin rights over nine MultisigProver contracts
The Flow, Sui, Stellar, XRPL-EVM, Plume, Hedera, Berachain, Hyperliquid and Monad MultisigProver contracts now have administrator axelar1w2ey0ek9e8q2dfmeznz6ah49zdywpdme0z0kly.
Axelar approved the core v1.4.7 upgrade at height 30,135,800
The network has an approved consensus-upgrade plan and references to reproducible Linux and macOS builds.
OP Labs proposes Upgrade 19 with the Karst hardfork and Kona as the main fault proof
If approved and executed, permissionless fault-proof chains would switch the respected game type for withdrawal proofs from CANNON to CANNON_KONA.
Attacker drains about $4.67 million through the Axelar–Secret route with unbacked saTokens
The affected saTokens lost some or all of their backing. Axelar paused the Axelar Secret and Secret-SNIP connections after it found the attack.
Axelar approved governance-transfer calls for Gateway contracts on 17 chains
The approved payloads call transferGovernance(address) to move Gateway governance to 0x7acbae6cba67d78aaf69e47000884ae00f9b2525.
Axelar stopped routing to the legacy Centrifuge chain
Axelar stopped routing transfers and messages to and from the retired legacy Centrifuge chain.
Lido proposed Staking Router v3 for validators of up to 2,048 ETH
If approved and executed, Lido would account for validators by their balances, where it now counts them.
Base restored mainnet withdrawals after a TEE enclave fault halted proposals
Withdrawals through the canonical bridge were delayed for a time, because the state proposals that withdrawals need stopped advancing.
Axelar upgrades VotingVerifier contracts on ten Amplifier chains
The code that verifies messages for the ten named routes is now code ID 64. Each migration message gave the chain-codec address.
Lombard moves LBTC and BTC.b bridging to Chainlink CCIP only
Lombard named the chains in the move. It chose CCIP's Cross-Chain Token burn-and-mint model, CCIP rate limits and an optional attestation by its Security Consortium for future bridging.
Axelar migrates its InterchainTokenService contract to code ID 63
The on-chain InterchainTokenService contract now runs code ID 63. Governance made the change through its migration process.
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.