TeraWulf just resized its bank line. The bitcoin miner filed an 8-K on October 23 that lifts its Morgan Stanley revolver from $250 million to about $400 million, with an uncommitted accordion of about $150 million more. That is a credit story, not a hashrate print. The CFTC, in the October 19 Federal Register, proposed writing event contracts into the swap definition while an interim final rule keeps casino-style sportsbook wagers out. Aave risk stewards posted a fresh V4 cap list. Magicians, Sky, Uniswap, and Ethresear each moved a draft. Kraken spent a Friday afternoon catching up Solana deposits.
Market context from our live snapshot at 2026-10-24T00:24:15+00:00: Bitcoin at $80,759 (about −0.50% over 24 hours), Ethereum at $2,373.64 (−0.51%), Solana at $102.25 (−1.38%). Global market cap sat near $2.73 trillion with bitcoin dominance about 59.5% and 24-hour volume near $67.0 billion. See our Bitcoin history, Ethereum history, and DeFi notes. Related: how to read a crypto market snapshot and the Crypto News hub.
TeraWulf lifts its revolver from $250 million to about $400 million
TeraWulf Inc. said it signed Amendment No. 1 on October 23 to its May 7, 2026 revolving credit agreement with Morgan Stanley Senior Funding as agent. The 8-K, accession 0001628280-26-067100, says total commitments rise from $250 million to about $400 million on the effective date, plus an uncommitted accordion of about $150 million if extra lenders show up. The amendment also drops the old $150 million letter-of-credit sublimit and can release collateral when named conditions hit. The company said the full amended agreement will ride with its 10-Q for the quarter ending September 30, 2026, so this filing is the commitment change, not the complete credit text.
CFTC proposes treating event contracts as swaps, and keeps casinos out
The Federal Register on October 19 published CFTC document 2026-21377, a notice of proposed rulemaking that would further define swap to include event contracts on sports, politics, culture, and weather. Comments close November 18, 2026. The same day, interim final rule 2026-21376 (91 FR 65969) took effect and excludes casino-style gambling products such as sportsbook and casino-game wagers from that swap definition. The pair splits prediction-style event contracts from traditional gambling products, and neither filing is a listing approval for any named venue.
LlamaRisk posts Aave V4 cap and rate tweaks, not an executed vote
LlamaRisk published an October 23 Risk Stewards note for Aave V4 that recommends raising Plus Hub slope1 for USDC and USDT from 4.60% to 4.70%, lifting the Prime Hub Bluechip USDT add cap from 13.125 million to 20 million, and cutting several USDG draw caps, including two Pendle spokes to zero. Avalanche V4 would double the Core Hub WAVAX add cap from 1 million to 2 million. Plus Hub USDC and USDT utilization sat near 89.2% and 91.7% in the post, with the proposed slope1 adding about 0.07 and 0.08 percentage points to supply APY. This is a recommendation thread, not a claim that the parameters already changed onchain.
Magicians draft a policy interface for ERC-7943 permissioned tokens
A Magicians thread opened October 22 as ERC-TBA: uRWA Policy Interface, arguing ERC-7943 standardized canSend, canReceive, frozen balances, and forcedTransfer but left how those answers are computed to each issuer. The draft would put checkSend, checkReceive, and checkTransfer(TransferContext) on an external policy contract, returning bytes32, plus optional afterTransfer hooks. It names movement kinds TRANSFER, EXECUTED, FORCED, MINT, and BURN so a mislabeled escrow return cannot skip a holder cap. Nineteen posts were on the thread when we read it, and the authors still flag open questions for the ERC-7943 editors. This is a draft interface, not a live Ethereum upgrade.
Sky Oct. 26 Atlas edit funds Skybase and widens a Morpho vault cap
Core GovOps posted the Atlas Edit Weekly Cycle for the week of October 26, 2026. The package would authorize a 900,000 USDS grant from Skybase SubProxy to the Skybase Foundation for operating costs through year-end, add Spark Diamond PAU Liquidity Layer contracts on Base, and raise Osero Gauntlet USDC Prime Morpho Vault V2 maximum exposure from 5 million to 10 million USDC while cutting its capital ratio requirement from 100% to 25%. It also requires a maintaining team to approve code changes before audit. The text lives as GitHub PR 365 on sky-ecosystem/next-gen-atlas and is a proposal, not a finished spell.
Kraken delayed Solana deposits for about four hours on October 23
Kraken opened an incident at 15:00 UTC on October 23 for delays processing Solana deposits and withdrawals. A monitoring note at 18:09 UTC said a fix was in, and the venue marked the incident resolved at 18:54 UTC, about four hours after the first post. Impact was listed as minor. The status page did not name a Solana chain outage or a lost-funds event, and Kraken separately posted SUI delays the same day that also resolved.
Ethresear.ch sketches heterogeneous recursion for EIP-8288 aggregation
An October 22 Ethresear.ch post titled Paranoid EIP-8288 argues recursive proof aggregation should support more than one approved proof size, not a single protocol-level verification key. The author describes a finite authenticated bank of verifier classes, each with its own relation and commitment geometry, and an accumulator lane per class so deferred matrix claims survive when the next proof uses a different class. The write-up points at an implementation called Parano1d that already runs small and large recursive proofs on a public mainnet. This is research toward an EIP-8288 backend, not a scheduled hard fork.
Uniswap opens URC-5 so tokens can declare preferred v4 pools
Uniswap governance thread 26307, posted October 21, opens URC-5: Token Venue Policy. Tokens whose mechanics depend on a Uniswap v4 hook, including names such as INDEX, STANDARD, and FWA, often want routers to hit a canonical pool, and the post says STANDARD and FWA already lost volume to restricted routes. URC-5 would define IVenuePolicy, Preferred versus Enforced policies, and directional permissions for other venues, while leaving transfer-time enforcement to each token. It is a community discussion, not a passed vote.
