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 risk stewards propose v3 cap and interest-rate changes
If implemented, the proposal would raise selected supply caps, increase USDe base borrowing rates, move optimal utilization for Core USDC and USDT and Plasma USDT0 from 92% to 94%, and reduce WETH slope-one rates on…
Aave service provider proposes broad stablecoin rate repricing
A concrete Risk Steward execution plan now exists for broad economic changes.
Lombard moves LBTC yield to a Bitwise-managed covered-call strategy
Up to 60% of LBTC backing may enter an actively managed derivatives mandate held through qualified custodians, adding custodian, counterparty, options, and manager dependencies while targeting 2.5% net APY in bitcoin…
Sky proposes reducing Osero's SparkLend USDS capital ratio to 25%
If approved, the instance's required capital buffer would fall by 75 percentage points, permitting greater reliance on Sky-supplied capital relative to Osero capital.
Sky proposes activating its full Treasury Management Function waterfall
If executed, July net revenue would fund security and maintenance, retain capital for Sky reserves, and split remaining capital among USDS staking rewards, SKY buybacks distributed to stakers, and buyback-and-burn…
Sky confirms Prime Agent settlement and oracle-accounting corrections
The reconciliation adds approximately 820,320 USDS of net Prime Agent revenue and 297,559 USDS of net Sky share to later settlement calculations, while replacing or correcting several accounting inputs.
Osero proposes doubling ALLOCATOR-PRYSM-A debt capacity
If executed, the allocator's maximum USDS capacity would rise from 5 million to 10 million and immediately targetable debt would rise from 1 million to 2 million.
Spark proposes USDG and RLUSD liquidity integrations
If executed, Spark would gain new USDG and RLUSD issuer, depeg, pool, and planner-execution exposure under replenishing deposit and swap limits.
Grove proposes lower reserves, higher exposure limits, and new Uniswap capacity
If executed, Grove would gain new Uniswap liquidity and swap capacity, the JTRSY reserve ratio would fall from 100% to 25%, maximum exposure would rise from 2.5 million to 5 million, and ALLOCATOR-GROVE-A maxLine would…
sky.money proposes new Morpho vault markets and sUSDS/USDT migration
The proposed replacement sUSDS/USDT market uses a 96.5% LLTV and caps the USDT oracle leg at $1.00.
Sky risk advisor proposes an 8 bp SSR cut and 100 bp Core Vault fee increases
A concrete rate proposal entered the Sky parameter process and would change both saver yield and borrower costs if executed.
Aave proposes USDai and sUSDai onboarding on Arbitrum
A concrete pathway was proposed for Aave to accept exposure connected to the rejected USD.AI credit product, requiring cross-memo review before any implementation.
Aave proposes syrupUSDC onboarding on Ethereum Core
A concrete governance path was proposed for a rejected private-credit exposure to become collateral within an approved-with-limits Aave deployment.
Rocket Pool proposes a 6 ETH megapool-validator bond
A concrete alternative to the planned lower reduced-bond setting entered governance consideration in response to limited rETH demand and withdrawal-liquidity needs.
Lido proposes a permissionless 0x02 CSM module
A concrete design entered governance discussion with proposed bond, fee, penalty, capacity, queue, and delegated-role parameters.
Aave advances stcUSD onboarding on MegaETH
The approved ARFC specifies a 10 million supply cap and an isolated stablecoin E-Mode with 88% LTV, 90% liquidation threshold, and a 4% liquidation bonus.
Rocket Pool approves RPIP-81 inflation and funding rebalance
The approved policy reduces the pre-Saturn-2 node-operator allocation from 70% to 50%, raises pDAO's share to 47.5%, and calls for 2.5% annual inflation with 95% of rewards to pDAO after Saturn 2.
Lido proposes automated revenue-funded LDO buybacks and liquidity provision
If launched through a later on-chain vote and funded, NEST would add automated daily treasury execution, a $40 million annual revenue baseline, a daily order cap, component-level emergency pauses, and Treasury…
Lido proposes Kelp-specific EarnETH first-loss exception
If approved, EarnETH could apply its first-loss backstop below the normally applicable threshold for this incident, but only after accounting for alternative coverage.
Lido proposes rerouting DVT and APM incentive flows
If implemented, the destination and delegated management of these incentive flows would shift to the Lido Earn treasury and Growth Committee-linked liquidity structure.
Lido approves variable DVT and DVV incentive allocations
For covered Curated Module and Community Staking Module operators, the node-operator share can rise to 50% when modeled DVT costs are high, while the staker share can rise to 85% as costs fall or incentives increase.
Balancer proposes moving Rocket Pool alliance treatment to its v3 liquidity pool
The proposal would remove the v2 rETH/WETH pool and add the v3 rETH/waEthWETH pool to the special Rocket Pool alliance revenue-sharing treatment.
Aave executes mUSD onboarding on Ethereum Core and Linea
mUSD became supplyable, borrowable, and flash-loanable on both markets. Ethereum received 10 million and 8 million supply and borrow caps; Linea received 70 million and 60 million caps.
Aave executes wrsETH onboarding on Avalanche
wrsETH became collateral-enabled with a 5,000-unit supply cap, a capped exchange-rate oracle path, and a wrsETH/WETH E-mode allowing 93% maximum LTV and a 95% liquidation threshold.
Lido opens a vote on Curated Module fee tiers
A concrete governance path opened to set the module-level operator share to 3.50% and pay qualifying operators an additional 0.50% or 1.00% through manual rebates.
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.