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.
Aave v3 Ethereum GHO Prime deposits fall 44% between checks
Observed pool liquidity declined by approximately $4.56 million, materially reducing the pool's reported deposit base.
Aave v3 GHO Umbrella deposits fall 38% between monitor checks
Observed pool deposits declined by 38%, materially reducing the pool’s monitored scale and firing the quantitative TVL-exodus alert.
DeFi Saver tracked TVL declines 27% between observations
The aggregate value attributed to positions with active DeFi Saver automation subscriptions decreased by approximately $83.7 million between monitor observations.
Aave v3 GHO Prime Instance deposits fall 40% between checks
Observed venue deposits fell 40%, reducing the liquidity base and warranting an immediate check of exit depth and the cause of the outflow.
Base recovers from consecutive mainnet chain stalls
The incident established a realized chain-availability failure affecting deposits, withdrawals, block production, and client software.
Base restores mainnet withdrawals after a TEE enclave issue halted proposals
The canonical exit path experienced a temporary operational delay because state proposals needed for withdrawal progression stopped advancing.
Base recovers from mainnet transaction delays caused by missed blocks
Timely mainnet transaction inclusion was temporarily impaired, creating operational delay risk for bridge initiation, proof, and other Base transactions even though no bridge-specific transaction was identified.
Base publishes postmortem on severe transaction drops and inclusion delays
Base rolled back the transaction-propagation configuration change identified as the immediate cause and committed to mempool-pipeline, alerting, and change-monitoring improvements.
Base recovers from periodically delayed block building
Transaction inclusion on the chain supporting the watched canonical bridge was temporarily less reliable, adding a confirmed operational incident to the bridge diligence record.
Base recovers from missed-block transaction delays
The incident added a confirmed transaction-inclusion disruption to Base's operating history, followed by recovery and preparation of a mitigation for recurrence.
Base recovers from elevated RPC and transaction-inclusion latency
For approximately two hours, transaction submission and state access were less reliable, degrading an operational dependency used by Base canonical-bridge workflows and monitoring.
Base recovers from AWS-related capacity and batch-submission disruption
Base Mainnet's production capacity and submission of L2 batches to Ethereum were temporarily degraded, exposing cloud-infrastructure availability as a dependency for timely canonical-bridge settlement and monitoring.
Base recovers from congestion-related transaction-inclusion delays
Transactions could remain pending longer during congestion, and Base changed mempool capacity to improve inclusion speed. This temporarily degraded execution reliability for canonical-bridge-related transactions.
Base recovers from a transaction-volume-driven safe-head delay
Safe-state progression slowed, users could experience delayed inclusion or dropped transactions, and node clients could fall behind.
Base recovers from a 33-minute mainnet block-production halt
The incident established a realized sequencer failover and provisioning failure capable of interrupting Base mainnet block production, deposits, and withdrawals.
Base recovers from a batching-related safe-head delay
Safe-head progression and timely L1-backed confirmation were impaired from 14:40 UTC until resolution at 18:09 UTC.
Base recovers from mainnet transaction delays caused by a batcher backlog
For approximately three hours, effective mainnet transaction capacity fell to roughly one-third of its target and users could need to resubmit dropped transactions.
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.