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.
Chainlink launches CCIP 2.0 with configurable verification and finality
Integrators and token issuers can opt into additional verifiers and execution controls or permit transfers before full source-chain finality.
Optimism Upgrade 20 changes fault proofs to super roots while retaining output-root withdrawal proofs
Fault-proof games now use super-root claims and timestamp-based sequence numbers.
Required OP batcher release adds L1 transition compatibility
The released software changes L1 submission gas limits, permits configurable AltDA input limits, and removes the l2_network startup-log field.
Optimism proposes Super Root fault proofs and OPCM v8 upgrade
New dispute games would use Super Roots. Permissionless chains would switch to game type 9;
Kona discloses fault-proof soundness fixes and requires operator upgrade
The available release fixes proof soundness and execution behavior. Operators using kona-client fault proofs are instructed to upgrade, and the changed state transition requires a new absolute prestate.
Axelar governance approves UNV migration authorization on Polygon
The migration authorization passed governance; its message targets a Polygon contract through a cross-chain call.
Optimism challenger release requires explicit configuration to retain Cannon coverage
Upgrading operators must explicitly retain Cannon when required; otherwise their challenger stops playing those games.
Lido Oracle 8.0.6 caps VEBO exit requests per report
The oracle iterator stops after 500 requests and carries remaining demand into subsequent approximately five-hour reporting frames.
Axelar governance approves axelar-core v1.5.3 upgrade
The v1.5.3 network upgrade is governance-approved. The associated official release describes a Cosmos SDK, IBC-Go and Wasmd migration plus vote-handling, queue-ordering, fee-policy and hardening changes.
BitGo selects Chainlink CCIP for a planned WBTC cross-chain migration
CCIP became BitGo's selected interoperability standard for the planned WBTC migration, materially expanding the prospective use of this watched dependency and introducing a unified CCT model with issuer-managed risk…
Lido approves Staking Router v3 architecture
The approved design replaces validator-count accounting with balance-based accounting, supports validators up to 2,048 ETH, adds governed consolidation-based module migration, updates exit oracles, and reserves…
Lido approves CMv2 and CSMv3 architecture and rollout plan
The approved design adds 0x02 withdrawal-credential support, large validators, new bonding and penalty mechanics, more granular roles, weighted Curated Module allocation, and a proposed 15% CSM stake-share upper bound.
Axelar approves core v1.4.7 upgrade at height 30,135,800
The network obtained an approved consensus-upgrade plan and reproducible binary references for Linux and macOS builds.
Optimism proposes Upgrade 19 and the Karst hardfork
If approved and executed, permissionless fault-proof chains would change their respected game type from CANNON to CANNON_KONA for withdrawal proving;
Lido proposes Staking Router v3 accounting and deposit architecture
If approved and executed, Lido would replace count-based consensus-layer accounting with balance-based accounting, add proof-gated validator top-ups, introduce a consolidation pipeline, reserve buffered ETH for…
Axelar executes VotingVerifier migrations across ten Amplifier chains
The VotingVerifier implementation governing verification for the ten named integrations moved to code ID 64, with chain-codec addresses supplied in each migration message.
Lombard commits BTC.b and LBTC to an exclusive Chainlink CCIP migration
Lombard established a concrete migration perimeter and selected CCIP's Cross-Chain Token burn-and-mint model, rate limits, and optional Security Consortium attestation as its future cross-chain architecture.
Axelar executes an InterchainTokenService contract migration
The on-chain InterchainTokenService contract implementation changed to code ID 63 under the governance-administered migration path.
Optimism publishes required op-challenger security release v1.9.1
A fixed official challenger version became available for a direct dependency of the fault-proof process that secures challenged withdrawals.
Steakhouse plans direct-market migration for Morpho Vault V2 allocations
The planned migration removes a nested vault layer from the allocation path and requires numerous curator operations across Steakhouse V2 vaults.
Aave approves v3.7 candidate scope ahead of final activation vote
The approved candidate scope advanced changes to eMode isolation, removal of legacy isolation and siloed-borrowing configurations, removal of L2 sequencer-uptime gating, append-only reserve lists, and…
Rocket Pool executes the Saturn 1 mainnet upgrade
New megapool validators could use 4 ETH bonds;
Axelar publishes CometBFT security-patch release v1.3.8
A patched official validator build became available, creating a concrete infrastructure-version diligence requirement for the watched Axelar dependency.
Optimism publishes essential op-node security release v1.16.5
A security-relevant official node version became available and was designated essential, creating an infrastructure-version review requirement for OP Mainnet dependencies.
Axelar validators apply a security patch addressing node-crash risk
A patched Axelar Core version became available, and Axelar reported majority-validator adoption intended to prevent validator nodes from crashing.
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.