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.
ULTRA contract adds a single-key Admin-role holder
The contract’s administrator set gained another holder, changing the key-management and privileged-control surface recorded in the ULTRA diligence file.
Sky proposes new Spark Arbitrum controller, bridge limits, and governance controls
If approved and executed, the package would establish a 5 million USDC per-domain maximum and 50 million USDC/day slope for the new CCTP route;
Sky proposes Osero Morpho-vault onboarding and removal of a penalty-setting timelock
Nothing is operative yet. If adopted and implemented, Osero would gain a new ERC-4626 vault allocation surface and governance could introduce a force-deallocate penalty without the prior seven-day minimum delay.
Sky proposes Osero cBEAM operator activation
If executed and fully authorized, an Osero-specific cBEAM operator would be able to adjust Osero rate limits and invoke preconfigured controller actions without waiting for a separate governance spell.
Spark proposes cancellation-independence exemptions and early queueing
Qualifying arrangements would no longer require separate curator/canceller signers or an additional independent canceller under Spark policy.
Sky proposes Morpho curation requirements and expanded Osero controls
The proposal adds role, market, oracle and timelock requirements for Prime Agent Morpho allocations;
Spark proposes narrower curator-independence requirements for Morpho vault controls
The proposal replaces the blanket prohibition on curator/cancellation-authority overlap with separate signer sets plus at least one fully independent cancellation holder.
Lido proposal would delegate deposit-reserve targeting to CMC Easy Track
The proposal creates a concrete path to delegate recurring control over how buffered ETH is prioritized between new consensus-layer deposits and withdrawal finalization during withdrawal pressure.
Rocket Pool pDAO approves RocketDash signaling platform and emergency replacement process
The recognized off-chain signaling venue and official vote-publishing authority were approved for replacement.
Morpho proposes adding Spearbit and raising the DAO multisig threshold
If approved and implemented, DAO operations would require six approvals, and Spearbit would provide paid trusted-signer services.
Grove proposes granting Sky PAS administrator authority over DPAU controls
If executed, PAS could alter Grove DPAU roles and rate limits without a separate Grove spell for each pre-authorized action.
Aave proposes Governance Emergency Guardian signer rotation
A concrete signer-rotation proposal now exists for the multisig that can cancel malicious, erroneous, or unsafe governance proposals and payloads. No operative owner rotation is established by this record.
Sky proposes delegated Smart Burn Engine parameter control through SBE BEAM
If executed, the operator could jointly change kbump, burn, hop, and rewardsDuration within configured throughput, delay, and cooldown bounds.
Aave proposes 2-of-3 service-provider control for GHO Stewards
The proposal creates a concrete path to lower the GHO Steward signing threshold and replace individual signing addresses with nested service-provider entity Safes. The candidate does not establish approval or execution.
Sky proposes delegated Smart Burn Engine controls and new Uniswap functions
The proposal defines a new no-executive-vote control path for kbump, hop, and burn settings and expands controller capabilities available to Prime Agents.
Spark proposes a 2-of-4 freezer multisig and signer rotation
A concrete control-change proposal entered governance review, supplying new evidence about the freezer role's signer composition and intended approval threshold.
Axelar approves Amplifier contract-admin rotation to a multisig
Governance authorized a new upgrade-control endpoint across gateway, routing, voting, rewards, service-registry, multisig, and Interchain Token Service components.
Axelar approves ITS and Amplifier gateway ownership migration
Governance authorized a broad cross-chain migration of ownership and administrative control to AxelarServiceGovernance.
Axelar rotates permission-control administrators for ITS, Router, and Multisig
The permission-control administrator for the Interchain Token Service, Router, and Multisig moved from axelar1nctnr9x0qexemeld5w7w752rmqdsqqv92dw9am to axelar1kctshqfxw74usjme9mqlvkf0rgdh96ty0mmm6p.
Axelar expands emergency multisig CosmWasm deployment authority
The emergency address axelar14vps3ev03zyp2wmj89etx8rrxdxyltfy4rzl5m gained a fast path for code upload and default instantiation or migration.
Axelar transfers XRPL Amplifier migration authority to 3-of-6 multisig
Migration authority moved from axelar1nctnr9x0qexemeld5w7w752rmqdsqqv92dw9am to the 3-of-6 multisig axelar14vps3ev03zyp2wmj89etx8rrxdxyltfy4rzl5m.
Aave approves faster Risk Steward actions and Umbrella pauser reassignment
The approved design reduces selected Risk Steward minDelay settings from 72 to 36 hours and assigns Umbrella pause and unpause authority to the Aave Protocol Guardian.
Spark approves Avalanche governance-bridge timelock and guardian
The approved design inserts a delay before governance actions become effective and gives a guardian multisig cancellation power during that delay.
Axelar rotates administrators for nine MultisigProver contracts
The Flow, Sui, Stellar, XRPL-EVM, Plume, Hedera, Berachain, Hyperliquid, and Monad MultisigProver contracts were assigned administrator axelar1w2ey0ek9e8q2dfmeznz6ah49zdywpdme0z0kly.
Axelar approves governance-transfer calls for multi-chain Gateway contracts
The approved payloads encode transferGovernance(address) calls directing Gateway governance toward 0x7acbae6cba67d78aaf69e47000884ae00f9b2525.
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.