Menu
MCAP $2.92T ▼-1.95%
BTC $86,069 ▲+0.88%
ETH $2,716 ▲+0.47%
BNB $789.47 ▲+0.04%
XRP $1.520 ▲+1.21%
SOL $120.68 ▼-0.58%
DOGE $0.0963 ▲+3.10%
ADA $0.274 ▲+11.90%
TRX $0.3364 ▲+0.28%
LINK $14.17 ▲+0.32%
AVAX $11.02 ▲+0.07%
HYPE $92.89 ▲+2.54%
DOT $1.220 ▲+2.15%

Ethereum news, analysis and interviews

Ethereum is the settlement layer for most of what institutions call tokenization, stablecoins and DeFi, and its own economics changed when it moved to proof of stake. Coverage here tracks the network upgrades, the Layer 2 ecosystem that carries most of its activity, staking yield and the ETFs and treasury companies now holding ether.

Guide: What is an Ethereum Layer 2?Guide: What is staking? How proof-of-stake yieldETH price and chartETH to USD converterETHA stockBMNR stockSBET stockNewsletter
Ethereum (ETH)$2,713.50+0.39% 24hReference rate via CoinGecko · All prices
From the interview archive
Related: DeFiReal World AssetsStablecoins
Lido sets 32 ETH bond for Community Staking Module, 13 times higher than default route
DeFi

Lido sets 32 ETH bond for Community Staking Module, 13 times higher than default route

, , , , , , ,

DeFiCrypto Coin Show News Team·October 4, 2026·3 min read

Lido contributors have set a 32 ETH entry bond for the protocol’s proposed Community Staking Module 0x02, more than 13 times the 2.4 ETH required under the existing default route. For institutions evaluating Ethereum staking infrastructure, the gap determines how much capital an operator must lock before larger, compounding validators become more fee-efficient than today’s standard model.

  • CSM 0x02’s first validator key requires a 32 ETH bond, with 30 ETH required for each additional key.
  • The module supports validators holding up to 2,048 ETH of effective stake under Ethereum’s EIP-7251 upgrade.
  • Operators would keep the full 2% module fee, while the Lido treasury takes 8%, pending a separate Staking Router vote.
  • 32 ETH first-key bond under CSM 0x02 versus 2.4 ETH on the existing route
  • 2,048 ETH maximum effective validator balance allowed, up from a 32 ETH ceiling today
  • 747 ETH stake level where CryptoSlate’s model found fee parity with one existing default key

Lido contributors said in an October 1 deployment plan posted to the protocol’s governance forum that they are preparing to bring Community Staking Module 0x02 to Ethereum mainnet. The module is a permissionless validator route built exclusively for 0x02 withdrawal credentials, which let a single validator compound rewards instead of capping out at 32 ETH.

GM! Lido contributors are getting ready to deploy CSM 0x02 on mainnet.

madlabman, Lido contributor, in the governance forum post

The module stays on Ethereum’s Hoodi testnet for now. Mainnet activation is expected in the fourth quarter of 2026, following the DAO’s July 20 approval of the launch proposal and a September 1 testnet announcement.

Lido Caps the Module at 2% of Total Stake

The deployment plan sets CSM 0x02’s stake share at 2% of all Lido-staked ETH, with that allocation sitting alongside the existing CSM 0x01 module under a proposed 20% combined ceiling. Operators who post the bond receive the module’s entire 2% reward share, while 8% goes to the Lido treasury, a split carried over from the original 0x02 CSM Landscape proposal rather than a new negotiation.

Ethereum’s EIP-7251, part of last year’s Pectra upgrade, is what makes the larger validators possible by raising the maximum effective balance to 2,048 ETH while keeping 32 ETH as the minimum to activate. Lido’s bond curve follows the number of keys an operator runs rather than the stake behind them, so an existing 0x02 key needs no extra collateral as its balance grows toward the ceiling.

Unlike CSM 0x01, the new module has no verified operator tiers such as Independent Community Stakers or distributed validator clusters. It offers one bond schedule to all permissionless entrants.

CryptoSlate’s Model Puts Fee Parity Near 747 ETH

Modeling published by CryptoSlate found that, holding yield and performance equal, a CSM 0x02 validator’s fees per ETH bonded match a single existing default key once the new validator reaches roughly 747 ETH of effective stake. That threshold measures fees per unit of collateral posted, not total profit, and assumes both validators are fully funded and reward-eligible for the same period.

The comparison shifts once an operator’s full budget enters the picture. Spreading a 32 ETH allowance across 23 existing default keys covers 736 ETH of delegated stake and raises the crossover to roughly 1,330 ETH, because the smaller keys use only 31 of the 32 ETH available. Lido’s operator economics table shows verified profiles push the threshold further still: a 24-key Independent Community Staker portfolio needs about 2,022 ETH for parity, while a 62-key distributed validator cluster would need roughly 3,472 ETH, above the 2,048 ETH ceiling entirely.

In practice, the new route offers a conditional advantage to unverified, default-tier operators running at scale. Verified ICS and IDVTC participants already hold cheaper, more reward-rich terms under CSM 0x01, which continues to operate in parallel rather than being replaced.

A 16-Position Queue Could Delay the Payoff

The deployment plan specifies that a new 0x02 key is seeded with 32 ETH through the standard deposit queue, then enters a separate 16-position top-up queue that fills in 2 ETH increments as stake becomes available.

A partially funded key stays at the front of that queue until it is topped up, which means an operator’s realized balance, not its theoretical 2,048 ETH ceiling, drives actual fee income over any given period.

Performance risk sits alongside funding risk. At a full 2,048 ETH balance, the proposed parameters impose a 16.512 ETH penalty for bad-performance ejection and a 6.4 ETH charge for a delayed exit, measured over a 28-day frame with 3% performance leeway and a three-strike threshold.

The CCS read. This is a capital-efficiency bet, not a yield upgrade: Lido is testing whether larger operators will accept slower funding and bigger penalty exposure in exchange for eventually running cheaper validators. For institutional allocators already tracking Ethereum’s staking supply through products discussed in our coverage of corporate ETH accumulation, the module’s 2% stake cap matters more than its headline bond size, since it limits how much

Get this in your inboxThe Crypto Coin Show newsletter covers the policy and market moves institutional crypto investors are pricing in.

Subscribe

Ethereum Layer 2 Blast shuts down with $51 million in user funds locked by five keyholders
DeFi

Ethereum Layer 2 Blast shuts down with $51 million in user funds locked by five keyholders

, , , , , , , ,

DeFiCrypto Coin Show News Team·October 2, 2026·3 min read

Blast, an Ethereum Layer 2 network that once held $2.24 billion in deposits, is shutting down due to unsustainable operating costs, leaving $51 million in user funds locked in contracts controlled by a five-person security council. The closure exposes a structural vulnerability in early-stage Layer 2 economics and raises questions about custody and withdrawal timelines as the network winds down.

  • $51 million in user funds remain bridged to Ethereum, with $46.6 million staked as ETH through Lido.
  • Blast’s fraud-proof system never fully activated, allowing a malicious state proposer to finalize invalid records and cause losses.
  • Five keyholders control the shutdown contracts; any three can instantly pause withdrawals or alter contract code with no delay.
  • $110 Daily chain revenue, down from $2.24 billion peak deposit value in June 2024.
  • 99% Collapse in total value locked, from peak to $32.3 million as of announcement date.
  • October 26 Final deadline for users to withdraw via Blast’s standard interface before direct contract interaction required.

According to reporting on the shutdown, Blast announced on Friday (October 2, 2026) that it will cease operations after determining operating costs exceed revenue with no path to viability. The network, an EVM-compatible Optimistic Rollup built by Blur marketplace founder Tieshun Roquerre (known as Pacman), invested user deposits into DeFi protocols to generate yield, a model that worked initially but became economically unsustainable.

Blast’s fraud-proof system design creates potential vulnerability with $51 million at risk

According to L2BEAT’s safety assessment, Blast’s fraud-proof infrastructure, designed to allow independent verification of state transitions, never fully activated. The chain relies on a single proposer to submit state roots to Ethereum; if that entity is malicious, it can finalize an invalid state without detection, creating direct loss-of-funds risk.

This design failure becomes critical at shutdown. The $51 million trapped in Blast’s contracts sit in a system with no working challenge mechanism. Users cannot independently prove that a withdrawal request is being blocked by malice rather than legitimate technical constraints.

The bulk of locked capital, $46.6 million, is staked ETH held with Lido, an interest-bearing staking service. Blast must unstake this position first, a process that takes approximately one week before bridge liquidity becomes available for withdrawal.

Five-person security council can pause withdrawals with no delay or timelocks

L2BEAT’s audit flagged that five keyholders collectively control the upgrade and withdrawal functions on Blast’s main bridge contract. A supermajority of three can instantly execute code changes or halt withdrawals without any delay (noted as CRITICAL risk in the assessment).

This stands in contrast to better-governed Layer 2s that impose timelocks, mandatory waiting periods before sensitive upgrades take effect, giving users time to exit if they disagree with a change.

Blast’s design places no such protection between a council decision and execution.

October 26 deadline forces users to interact directly with Ethereum contracts

Blast has set October 26 as the final date users can withdraw through the standard Blast application interface. After that date, users must interact directly with Blast’s smart contracts on Ethereum, a process requiring more technical knowledge and exposing users to the risk of signing unverified transaction data.

The week-long Lido unstaking period means the earliest bridge liquidity will arrive around October 9, after which the 24-hour standard Ethereum exit wait applies. Users who miss the October 26 deadline will still be able to withdraw, but only through manual contract interaction.

Blast joins a growing list of failed Layer 2 launches in 2026, including Lisk’s blockchain shutdown and the Bitcoin Layer 2 Botanix, both of which onboarded users rapidly before collapsing.

The CCS read. Blast’s shutdown underscores that venture-backed Layer 2s betting on yield generation without durable fee revenue lack a sustainable model. The custody risk during wind-down, unvetted fraud proofs and no timelocks on security council actions, reveals why institutional investors should demand governance safeguards similar to Arbitrum’s timelocked upgrades before depositing capital into early-stage rollups.

The key question unresolved: whether Blast’s five keyholders will publish full transparency on the withdrawal process as Lido’s unstaking completes. Standard practice would include cryptographic proof that funds remain unpaused and that no unauthorized state root finalization occurred during the unstaking window. Watch for this documentation by October 10; its absence would signal elevated risk for the $51 million still in the system.

Get this in your inboxThe Crypto Coin Show newsletter covers the policy and market moves institutional crypto investors are pricing in.

Subscribe

Ethereum Foundation launches zkAPI for anonymous AI service payments
AI News

Ethereum Foundation launches zkAPI for anonymous AI service payments

, , , , , , , , ,

AI NewsCrypto Coin Show News Team·October 2, 2026·4 min read

The Ethereum Foundation says its new zkAPI system lets users pay for AI model access and metered APIs without ever linking that payment to their identity or prompt history. Built with the Open Anonymity Project, the tool matters to institutional investors because it ties Ethereum’s core value proposition, privacy-preserving settlement, directly to the fastest-growing category of machine-to-machine commerce.

  • zkAPI was developed jointly by the Ethereum Foundation and the Open Anonymity Project.
  • Users deposit ETH or USDC once into a vault contract, then authorize spending with zero-knowledge proofs instead of API keys.
  • Ethereum targets a gas limit above 100 million in 2026, up from 60 million reached in 2025 after the Pectra and Fusaka upgrades.
  • 100M+ 2026 gas limit target versus 60M reached in 2025
  • 8x theoretical blob capacity gain delivered by Fusaka’s PeerDAS
  • 2029 target year for full quantum-resistant Ethereum execution and consensus layers

The Ethereum Foundation said in a blog post published Thursday (October 1) that zkAPI separates payment from identity for AI inference and other metered services. Today, it wrote, “your API key points to an account, the account to a payment method, and every prompt you send joins the record attached to both,” letting providers reconstruct a persistent profile from billing data alone.

Ethereum Foundation Ships Vault Contract and Zero-Knowledge Proof Client

Under zkAPI, a user makes a single onchain transaction, depositing ETH or USDC into a vault contract on Ethereum. That balance becomes a private cryptographic note, spendable only by the depositor and untraceable to the deposit itself.

To authorize spending, a client running locally on the user’s device generates a zero-knowledge proof. The proof confirms a funded note covers the request without revealing which note, deposit, or person is behind it.

The Ethereum Foundation said one proof can authorize either a single API call or an entire session, with a zkAPI server minting a short-lived, dollar-capped API key that lives only in the device’s memory. Double-spending is blocked by a nullifier, a one-way serial number derived from the note’s secret; a repeat nullifier exposes an attempted double spend without revealing any other information. The system runs on Groth16 proofs over the BN254 curve, Poseidon hashing, and a Merkle tree 32 levels deep, with the vault contract verifying proofs onchain at deposit, close, and withdrawal so users can exit even if every zkAPI server disappears. Default local endpoints for OpenAI and Ollama mean existing chat clients and editors can plug in via localhost without redesign, a pattern similar to how AI agent payment tools like Daski are trying to let software pay for services without a persistent account.

Ken Liu, a Stanford computer science PhD candidate working on the Open Anonymity Project, described the design’s lineage within the project’s broader inference work.

It’s like a generalization of OA unlinkable inference that also abstracts payments away.

Ken Liu, Open Anonymity Project

zkAPI Hides Payment, Not Your IP Address or Prompt Content

The Ethereum Foundation’s own documentation is explicit about what zkAPI does not solve. A provider still sees the content of every prompt and the requester’s network metadata, including IP address, and can attempt to correlate sessions by timing even when billing is anonymous.

The foundation recommends routing requests through Tor with a fresh circuit per session for stronger network anonymity. On the content side, reused personal details, writing style, or project documents can re-link sessions as a fingerprint, a tradeoff the foundation calls inherent to balancing privacy against useful context.

One mitigation floated in the documentation is using local or trusted-execution-environment models to generate requests from shared memory rather than having users retype context by hand, an approach that echoes how projects such as XYO’s work with Autonomys try to verify machine-generated data without exposing its origin. For institutional compliance teams, the open question is whether regulators treat a privacy-shielded billing layer differently from the unlinkable inference layer it sits on top of, since zkAPI explicitly separates the two.

Glamsterdam Upgrade Lands in October as Gas Limit Push Continues

The Ethereum Foundation’s 2026 protocol priorities update, published February 18, organizes work into three tracks: Scale, led by Ansgar Dietrichs, Marius van der Wijden, and Raúl Kripalani; Improve UX, led by Barnabé and Matt; and Harden the L1, led by Fredrik, Pari, and Thomas. The gas limit rose from 30 million to 60 million in 2025 through the Pectra upgrade in May, which added EIP-7702 account abstraction and raised the maximum validator balance to 2,048 ETH, and the Fusaka upgrade in December, which brought PeerDAS and an 8x increase in theoretical blob capacity.

For 2026, the foundation’s roadmap targets a gas limit above 100 million, supported by Block-level Access Lists under EIP-7928. Ethereum educator Anthony Sassano has said 180 million is the year’s ideal outcome, though not the guaranteed one.

October is set to bring Glamsterdam, a dual-layer upgrade pairing the Amsterdam update on the execution layer with Gloas on the consensus layer, widely described as the network’s biggest step since the Merge in 2022. Amsterdam introduces parallel transaction processing on the execution layer, while the Harden-L1 track has already begun implementing quantum-resistant cryptographic algorithms, with full quantum resistance targeted for 2029, a parallel effort to initiatives such as the post-quantum upgrade proposed for Lightning’s offchain layers.

The CCS read. zkAPI is less a product launch than an infrastructure bet: if AI agents start transacting at scale, the entity that owns the anonymous settlement layer owns a toll booth on machine commerce. For ETH holders, that reframes gas demand from speculative trading to recurring, metered inference payments, a stickier revenue base than most L2 fee flows institutions currently model.

The Open Anonymity Project’s GitHub repository and the ZkApiVault contract are already live on mainnet for developers to test, while the harder test comes in October when Glamsterdam ships alongside the push past 100 million gas, the point at which network throughput and zkAPI’s proof-generation costs will be measured under real load.

Get this in your inboxThe Crypto Coin Show newsletter covers the policy and market moves institutional crypto investors are pricing in.

Subscribe

Ethereum Foundation deploys Glamsterdam upgrade to test optional 200 million gas limit on Sepolia
Blockchain

Ethereum Foundation deploys Glamsterdam upgrade to test optional 200 million gas limit on Sepolia

, , , , , , ,

BlockchainCrypto Coin Show News Team·October 1, 2026·4 min read

The Ethereum Foundation has scheduled the Glamsterdam upgrade to activate on the Sepolia testnet on Tuesday, October 6 at 13:53:36 UTC, introducing an optional gas-limit schedule that targets 200 million gas per block, more than three times the network’s current 60 million default. The test matters for institutional crypto infrastructure because it is the first live trial of how Ethereum coordinates a major capacity increase without forcing it through a hard consensus rule.

  • Glamsterdam activates on Sepolia on Oct. 6 at 13:53:36 UTC, combining the Amsterdam execution upgrade with the Gloas consensus upgrade.
  • EIP-8261 sets an optional 200 million gas schedule, but Prysm 7.2.0 and Teku 26.9.1 both default to 60 million unless validators manually reconfigure.
  • Ethereum’s gas limit has already risen from 30 million in February 2025 to 60 million under Fusaka, and Hoodi and mainnet Glamsterdam dates remain undecided.
  • 200M optional gas target Glamsterdam schedules, over 3x the 60M default
  • 60M gas limit clients still ship with unless validators opt in manually
  • Oct. 6 Sepolia activation date, set roughly eight months after Fusaka’s 60M rollout

The Ethereum Foundation said in its testnet announcement that node operators must update both their execution and consensus layer clients before the Sepolia fork, and that stakers must also upgrade their beacon node and validator software. The announcement makes clear that simply installing compatible software will not move Sepolia toward the 200 million gas figure on its own. Glamsterdam’s headline features are enshrined proposer-builder separation and block-level access lists, changes the Foundation says are designed to support greater Layer 1 throughput while keeping block validation manageable for node operators.

Glamsterdam Bundles ePBS and Access Lists Into One Sepolia Fork

Glamsterdam merges the Amsterdam execution-layer upgrade with the Gloas consensus-layer upgrade into a single coordinated fork. Its two headline changes are proposer-builder separation, brought directly into Ethereum’s consensus protocol rather than relying on trusted middleware, and block-level access lists, which let clients read state and validate transactions in parallel.

The Foundation frames both as groundwork for higher execution capacity without making block validation impractical for ordinary node operators.

Hoodi and mainnet activation dates have not been set; Tuesday’s fork covers Sepolia only, with no action required from mainnet users or ETH holders.

EIP-8261 Makes 200 Million a Recommendation, Not a Rule

The 200 million figure comes from EIP-8261, which lets consensus-layer clients source their gas-limit preference from an epoch-based schedule instead of hardcoded, release-scoped defaults. The proposal does not change Ethereum’s consensus-validity rules: EIP-1559’s existing elasticity mechanism remains the only gas-limit rule, and blocks above or below the scheduled value stay valid either way.

That design solves a coordination problem the proposal spells out directly. If clients ship a new higher default ahead of a planned activation epoch, early-updating nodes start voting the limit up before the network has agreed the value is safe; if the default ships only after activation, adoption is slow and operationally awkward.

EIP-8261 mirrors the epoch-based blob schedule format introduced in a separate configuration standard and generalizes an approach already tested through a prior gas-limit coordination, giving Ethereum a single machine-readable place to record “the gas limit the network should run at” rather than requiring every client team to hardcode a new number.

In practice, this turns Sepolia into a coordination test that was first reported by CryptoSlate: the realized gas limit will move only as far as validators choose to push it, not jump to 200 million automatically. The open question the document leaves unresolved is how quickly validator operators will actually adopt the higher preference once Glamsterdam goes live, since the schedule only warns clients when a configured value exceeds the recommendation rather than clamping it.

Validators Must Flip a Setting or Stay at 60 Million

Prysm 7.2.0 and Teku 26.9.1 both support the Sepolia fork, but the Foundation confirmed both continue defaulting to 60 million gas after activation unless an operator explicitly reconfigures. Prysm validators must use version 2 proposer settings or the keymanager API, since the older suggested-gas-limit flag has no effect after Gloas.

Teku validators can override the default through their validator configuration.

That manual step is the whole experiment. Sepolia’s gas limit rises only as fast as validators choose to configure it.

Fusaka already introduced a 16.7 million gas cap on any single transaction, a safeguard that stays in place regardless of how high the overall block limit climbs. That means a higher block limit mainly creates room for more aggregate activity, such as decentralized exchanges and other high-demand DeFi protocols like those reviewed in Aave governance’s recent proposal, rather than letting any individual smart-contract call expand without limit. Client teams such as Geth, which recently shipped history-pruning options in its v1.17.7 release, will need comparable Sepolia-ready builds before the test can draw conclusions across the full client set.

The CCS read. We read this as Ethereum testing its appetite for throughput before committing capital-intensive infrastructure to it. Staking providers and validator operators now carry an operational decision that doubles as a vote on scaling speed, and their default inaction, since 60 million requires no configuration change, could understate real demand for 200 million until mainnet forces the question.

Hoodi and mainnet activation dates remain undecided, and the Ethereum Foundation says those will be announced separately once client teams agree on timing. Validator participation in the 200 million preference on Sepolia is the signal developers will watch before deciding how far, and how fast, to push the same change toward mainnet.

Get this in your inboxThe Crypto Coin Show newsletter covers the policy and market moves institutional crypto investors are pricing in.

Subscribe

MetaMask exits staking validators after detecting security incident, wallet funds unaffected
Blockchain

MetaMask exits staking validators after detecting security incident, wallet funds unaffected

, , , , , , , ,

BlockchainCrypto Coin Show News Team·October 1, 2026·3 min read

MetaMask has shut down part of the Ethereum staking infrastructure it inherited from Consensys after detecting a security incident on its systems, though the wallet provider says it has found no immediate threat to user funds. The move affects validators run through Lido, the staking protocol that issues stETH tokens, and will unwind over roughly six weeks even as MetaMask insists everyday wallet holders face no action item today.

  • MetaMask is exiting affected validators within its non-custodial staking operations as a precaution, with no wallet threat identified so far.
  • The last validators should stop running by the end of October 7, 2026, according to Lido, with ETH restaking over a roughly 45-day process.
  • Lido holds a reserve fund of more than 6,750 stETH to absorb any disruption, and stETH holders need take no action.
  • 6,750+ stETH reserve Lido says can absorb the validator exit
  • 45 days estimated timeline for ETH to restake after leaving Lido
  • Oct. 7 deadline for MetaMask’s last affected validators to exit

MetaMask disclosed Wednesday, September 30, 2026 (yesterday) that it was responding to a security incident affecting part of its infrastructure, according to a report from BeInCrypto. The company said it had identified no immediate threat to MetaMask wallets but was proactively exiting affected validators within its non-custodial staking operations as a precaution, in a post on X.

MetaMask has not disclosed which specific systems the incident touched, and it has not asked users to move funds or change wallet settings. The company says it is working with outside partners and security advisors while its investigation continues, with further details promised as the review progresses.

MetaMask Idles Validators Inherited From Consensys Staking

The validators in question sit inside MetaMask Staking, the unit formerly known as Consensys Staking that MetaMask absorbed when it split from Consensys this September. These are the computers that lock up ETH to help secure Ethereum and earn staking rewards, and a portion of them operate through Lido, the protocol that lets users stake ETH and receive the liquid token stETH in exchange.

Because of the infrastructure compromise, MetaMask is now winding down the validators tied to Lido rather than continuing to run them while the investigation is open. Lido confirmed the exit in its own post on X, framing it as a precautionary step by MetaMask to protect client assets tied to the validators it operates.

Lido Sets a 45-Day Unwind and a 6,750-stETH Buffer

Lido says the last of the affected validators should stop running by the end of October 7, 2026, a little over a week from the disclosure. The ETH they free up will flow back into Lido and get restaked gradually rather than all at once, a process the protocol estimates will take about 45 days.

stETH holders keep their tokens throughout that window and do not need to take any action, Lido said. The protocol’s reserve fund, holding more than 6,750 stETH, exists specifically to cushion situations like this one.

The staged unwind mirrors how other platforms have handled breaches without freezing user assets outright.

July’s Hidden North Korean Developer Case Reopens Questions

This is not MetaMask’s first security headline of 2026. In July, Consensys disclosed it had found a hidden North Korean developer working on MetaMask’s codebase.

MetaMask has not said whether Wednesday’s infrastructure incident connects to that earlier finding, and the company has given no timeline for when its investigation will conclude.

Until more detail emerges, the firm is advising users to treat unsolicited messages asking for recovery phrases as phishing attempts, since a single signed transaction can drain a wallet regardless of the underlying infrastructure issue.

The CCS read. The real test here is operational, not reputational: a 45-day unwind through a reserve fund rather than a frozen withdrawal page is the kind of incident response institutional custodians will study. If MetaMask’s investigation traces the breach back to the July developer infiltration, expect staking counterparties to start demanding code-provenance audits before allocating to non-custodial validator operators at all.

MetaMask has not yet disclosed which systems were compromised or whether the incident ties to the North Korean developer case Consensys flagged in July, leaving both questions open as the company’s investigation continues past the October 7 validator exit deadline.

Get this in your inboxThe Crypto Coin Show newsletter covers the policy and market moves institutional crypto investors are pricing in.

Subscribe

Uniswap’s StablePair hook pools hold 82% less TVL than comparable v3 stablecoin pairs
DeFi

Uniswap’s StablePair hook pools hold 82% less TVL than comparable v3 stablecoin pairs

, , , , , , ,

DeFiCrypto Coin Show News Team·October 1, 2026·4 min read

Uniswap Labs has launched StablePair Hook, a Uniswap v4 hook (a smart contract module that changes how a liquidity pool prices and charges swaps) that replaces flat trading fees with a rate that moves block by block around a fixed reference price. The design aims to let liquidity providers keep more of the value created when a stablecoin pool drifts and gets corrected, but a review of the mechanism shows three structural gaps that can still erode LP returns.

  • The hook’s fee logic compares a cached pool price against a stored reference rate, never consulting an external market feed.
  • On Sept. 30, 2026, the USDC/USDT StablePair pool held about $6.1 million in TVL versus $34.2 million in a comparable legacy v3 pool.
  • $200B total H1 2026 stable-pair DEX volume, about 4% of crypto spot trading
  • $6.1M StablePair pool TVL versus $34.2M in the older v3 pool

Uniswap Labs announced the two Ethereum pools, USDC/USDT and USDC/USDG, on Sept. 10, 2026. A CryptoSlate analysis of the hook’s documentation found that the mechanism’s benefit to LPs depends entirely on a configured reference rate holding, not on any live market check.

Uniswap Replaces a Flat Fee With a Block-by-Block Spread

Under a static fee, both sides of a trade pay the same rate, handing most of the value from a price correction to arbitrage bots, according to Uniswap’s Sept. 16 explanation. StablePair Hook instead measures, on every swap, how far the pool’s price sits from a reference rate set at pool creation, which for USDC/USDT is exactly 1:1 per the hook’s deployment documentation.

Inside a narrow band around that reference, both directions pay a fee calibrated to hold a fixed bid and ask. Outside the band, swaps that push the price further away pay zero fee, while swaps correcting it face a fee that decays like a Dutch auction until someone takes it.

Uniswap says the design captures the “vast majority” of rebalancing profit for LPs rather than ceding it to bots.

CryptoSlate Finds the Reference Rate Has No Market Check

CryptoSlate’s review identifies the first structural gap: the fee rule compares the cached pool price only against the stored reference, never an external oracle. The hook’s block-price caching mechanism takes the first swap in each block to set the price used for that block’s fee calculations, which removes a same-block fee exploit but leaves later trades exposed to stale inputs if the live price crosses the reference mid-block.

The second gap is economic rather than technical. If an issuer shock cuts one stablecoin’s external value below its reference, a sale of the weakening coin can read to the hook as moving the pool “away” from parity and earn zero fee, even though it reflects genuine price discovery rather than a temporary imbalance the hook is meant to correct.

The third gap concerns governance. Uniswap’s documented role model gives governance control over live fee configurations and implementation upgrades, meaning the reference benchmark itself can change. The fee rules that split trades by direction can shield LPs from bot-driven spread capture, but they cannot verify issuer solvency or restore a token’s redemption value once it depegs.

Early Volume Data Leaves the Return Claim Untested

CryptoSlate pulled Uniswap interface stats on Sept. 30, 2026, showing the USDC/USDT StablePair pool at roughly $6.1 million in TVL with $117.9 million in 24-hour volume around 15:59 UTC, and the USDC/USDG pool at about $2.6 million in TVL with $8.7 million in volume around 15:57 UTC. A comparable Ethereum USDC/USDT v3 pool charging a flat 0.01% showed about $34.2 million in TVL, $15 million in 24-hour volume, and $1,100 in 24-hour fees around 16:02 UTC, more than five times the StablePair pool’s locked value despite lower turnover.

The observations were not synchronized and the StablePair panels supplied no comparable absolute fee total or realized position-level return. Testing Uniswap’s claim that the hook captures the “vast majority” of rebalancing profit would require matching periods, active liquidity ranges, fee income, and inventory valuation across both pool types.

Uniswap says OpenZeppelin reviewed a non-upgradeable predecessor’s core fee mechanism from Feb. 9 to 13, 2026, and resolved the same-block fee-splitting issue through block caching, but the later upgradeability and governance role model fell outside that review.

The hook’s permanent address permissions exclude remove-liquidity callbacks and custom accounting deltas, so upgrades cannot block LP withdrawals or alter swap amounts to skim extra fees, though withdrawal rights say nothing about the market value of what an LP ultimately holds.

The CCS read. We read this less as a flaw in Uniswap’s code and more as a reminder that dynamic-fee hooks shift risk rather than eliminate it. LPs who ported liquidity into StablePair pools are now underwriting reference-rate integrity rather than bot-driven spread capture, a trade-off that only pays off if governance keeps the benchmark accurate and no pegged asset loses value faster than fees accrue.

Uniswap has not published a timeline for extending StablePair Hook beyond its two Ethereum pools or for governance to revisit the reference-rate update process, leaving open whether future upgrades will add an external price check the current design lacks. Integrators are directed to the deployment documentation to monitor configuration changes directly, since governance retains the sole authority to alter the benchmark LPs are now priced against.

Get this in your inboxThe Crypto Coin Show newsletter covers the policy and market moves institutional crypto investors are pricing in.

Subscribe

Institutional crypto funds absorb $3.55 billion after Fed rate hike
Bitcoin

Institutional crypto funds absorb $3.55 billion after Fed rate hike

, , , , , , , , ,

BitcoinCrypto Coin Show News Team·September 30, 2026·3 min read

Global crypto investment products absorbed $3.55 billion in the week after the Federal Reserve’s September 16, 2026 rate increase, the largest weekly haul of 2026 and a sign institutional buyers treated the hike as a catalyst rather than a deterrent. The rebound came just one day after a Senate crypto bill failed and Bitcoin fell below $75,000, underscoring how quickly institutional conviction can return once a source of policy uncertainty clears.

  • Bitcoin funds absorbed $2.52 billion of the total, Ethereum products added $702 million, and Solana and XRP funds pulled in $193 million and $92.3 million.
  • US-listed spot Bitcoin ETFs recorded inflows on all five trading days that week, helping push US products to $3.43 billion of the $3.55 billion global total.
  • Strategy, formerly MicroStrategy, bought 1,666 more Bitcoin for $143 million, funding part of the purchase by issuing new MSTR shares.
  • $3.55B weekly crypto fund inflow, the best week of 2026
  • 49-50 Senate vote count that blocked the CLARITY Act
  • $84,236 Bitcoin price after falling below $75,000

Global crypto investment products took in $3.55 billion in the week after the Federal Reserve’s rate increase, the largest weekly inflow tracked so far in 2026, according to data from asset manager CoinShares and first reported by BeInCrypto. The Fed lifted its benchmark rate a quarter point on September 16, 2026, to a range of 3.75% to 4.00%, a move markets had already priced in for weeks. Higher rates typically favor yield-bearing assets such as Treasuries over crypto, which pays no interest at all, yet institutional buyers moved the other way.

CoinShares Ties the Rebound to the End of Policy Uncertainty

CoinShares, the asset manager that tracks weekly flows across Bitcoin, Ethereum and other crypto funds, said the buying pattern reflected investors stepping back in once the rate decision had removed the ambiguity that kept them on the sidelines. It wrote in its report that “the scale and breadth of the week’s demand suggest institutional conviction returned once the policy decision removed a key source of uncertainty, a pattern consistent with buying the fact after weeks of caution.” CoinShares also markets its own crypto investment products, giving it a direct stake in the flows it reports.

The rebound followed a rough stretch. On September 15, 2026, the CLARITY Act, a Senate bill meant to set federal rules for crypto market structure, failed a Senate vote 49 to 50, and Bitcoin fell below $75,000 in the aftermath.

Bitcoin has since recovered to trade near $84,236, up 1.37% in 24 hours according to BeInCrypto data, a swing of roughly $9,000 from its post-vote low. Lawmakers are now drafting replacement legislation, CoinShares noted in the same report.

Bitcoin Funds Capture $2.52 Billion of the Week’s Inflows

Bitcoin products led the rebound, taking in $2.52 billion of the week’s $3.55 billion total, more than triple the $702 million that flowed into Ethereum funds. Solana and XRP products added $193 million and $92.3 million respectively, rounding out demand across the largest tokens.

US-domiciled products accounted for $3.43 billion of the global figure, with spot Bitcoin ETFs posting inflows on all five trading days, a sharp reversal from late May 2026, when crypto funds shed $1.67 billion in a single week.

Strategy, which now holds 847,666 BTC, added 1,666 more coins for $143 million during the week, funding part of the purchase through a new MSTR share issuance. CoinShares flagged that the stock sale dilutes existing shareholders even as it expands the firm’s bitcoin treasury.

Traders See Under 40% Odds of an October Hike

Futures markets now price a less than 40% probability that the Fed raises rates again at its October meeting, even as the 10-year Treasury yield holds near 5.28%, a level tracked on TradingView’s chart of the benchmark. US PCE inflation, the Fed’s preferred gauge, cooled to 3.4% in August, data released Wednesday, September 30, 2026 showed.

The next test arrives Friday, October 2, 2026, when the September jobs report lands. It is the first major data point that could reshape rate expectations before the Fed’s next meeting.

The CCS read. Strategy funding its latest bitcoin purchase partly through fresh share sales, rather than debt, shows the company prioritizing balance sheet flexibility over avoiding dilution. For institutional allocators, two separate corporate playbooks for holding crypto reserves are now running side by side, not converging into one.

Friday’s jobs report, due October 2, 2026, will be the next major signal for traders weighing whether the Fed holds rates steady or resumes tightening at its next meeting, a decision that will test whether institutional buyers keep rotating into bitcoin funds at the pace CoinShares recorded this week.

Get this in your inboxThe Crypto Coin Show newsletter covers the policy and market moves institutional crypto investors are pricing in.

Subscribe

Crypto Coin Show
DeFi

Aave Labs proposes adding Stripe-backed stablecoin OUSD to core markets

, , , , , ,

DeFiCrypto Coin Show News Team·September 30, 2026·3 min read

Aave Labs has published an ARFC proposing to onboard Open USD (OUSD) to the Aave V3 Core Instance and the Aave V4 Core Hub on Ethereum. OUSD is a dollar stablecoin issued by Bridge Building Inc, a Stripe subsidiary, and the listing would make Aave a day-one venue for lending and borrowing the token.

  • OUSD would launch as supply and borrow only, with collateral usage disabled on both deployments
  • Redemptions are capped at 10% of outstanding OUSD supply in any 24-hour period
  • Risk parameters await recommendations from LlamaRisk before a Snapshot vote can proceed
  • 200+ companies in the OUSD partner consortium, per the post
  • 10% cap on 24-hour redemptions as share of outstanding supply
  • 5 Zenith audit reports covering the issuer’s template, none OUSD-specific

The ARFC lays out OUSD’s structure in detail: cash, short-term Treasuries and qualifying money market funds back the token at least 1:1, with BlackRock managing the Treasury reserve and BNY and Lead Bank providing banking. Bridge Building Inc, a subsidiary of Bridge Ventures LLC and ultimately Stripe LLC, issues and redeems OUSD under contract with Open Standard LLC, the program’s governance entity. Aave is listed among the consortium’s over 200 partners, alongside Visa, Mastercard, Coinbase and BlackRock.

Reserve Income Model Differs From Typical Stablecoins

Unlike most fiat-backed stablecoins, OUSD is designed to return the bulk of reserve income to partners that adopt and distribute it, with Open Standard keeping a management fee. The post states Aave Labs will not be paid for this: “Aave Labs has not received and will not receive any compensation or reserve income tied to OUSD distribution.”

If the listing passes, the Aave DAO itself would still collect reserve factor and liquidity fee income from OUSD borrowing activity on its own markets.

Issuer Keeps Freeze, Seize and Upgrade Powers

The contract at 0x9f6F…C4436 is upgradeable, and the issuer holds mint, burn, pause, freeze/seize and allowlist/denylist functions. The post says Bridge secures these keys through Fireblocks MPC and follows documented freeze and blacklist processes it describes as compliant with the GENIUS Act.

Issuance is expected to eventually move to Bridge National Trust Bank, which holds preliminary conditional OCC approval as of February 12, 2026, without changing token contracts or addresses.

Process Mirrors, Then Diverges From, Recent Listings

OUSD follows the standard three-step Aave path: forum feedback, then Snapshot vote if sentiment is positive, then an onchain AIP with final parameters. That contrasts with Aave’s recent direct-to-AIP listing of USDe on Avalanche, which skipped the ARFC and Snapshot stages entirely.

The document does not explain why OUSD is taking the longer route while other recent stablecoin listings bypassed it.

What Changes In Practice

For Aave users, a passed proposal means a new dollar asset to borrow against existing collateral, but no new collateral option at launch since OUSD usage as collateral is explicitly disabled. LPs supplying OUSD would earn yield from Aave borrowers rather than direct exposure to Open Standard’s reserve income share.

Aave DAO treasury would gain reserve factor and liquidity fee revenue on OUSD borrow volume, an incremental addition alongside existing stablecoin markets like USDe.

The proposal sets no supply cap, borrow cap or interest rate curve; those depend on LlamaRisk’s pending recommendations and Chainlink feeds already live in production.

The document also does not disclose OUSD’s current circulating supply or onchain liquidity, factors that would normally inform how aggressive those caps should be.

“Unlike most fiat-backed stablecoins, OUSD returns the large majority of reserve income to the partners that adopt and distribute it, with Open Standard retaining a small management fee.”

Aave governance forum, ARFC post

The CCS read. A stablecoin whose issuer retains freeze, seize and upgrade keys, backed by no asset-specific audit, is standard for GENIUS-era dollar tokens, not a red flag unique to OUSD. The real question is whether LlamaRisk’s parameters keep initial caps tight enough that Aave’s exposure stays proportional to OUSD’s still-undisclosed onchain liquidity.

Community sentiment on the ARFC determines whether Aave Labs moves OUSD to a Snapshot vote; no date for that vote is set, and LlamaRisk has yet to publish the risk parameters the proposal says will populate before onchain execution.

Get this in your inboxThe Crypto Coin Show newsletter covers the policy and market moves institutional crypto investors are pricing in.

Subscribe

Crypto Coin Show
Blockchain

Geth releases v1.17.7 with custom history pruning option

, , , , ,

EthereumCrypto Coin Show News Team·September 30, 2026·2 min read

Geth’s core team pushed out v1.17.7, a patch release triggered by a failed Ubuntu PPA publish of v1.17.6. The build adds a new flag for custom history pruning and folds in fixes touching the miner’s gas accounting and a memory leak in the chain’s block prefetcher.

  • v1.17.7 was cut mainly because publishing v1.17.6 to the Ubuntu PPA failed
  • Both v1.17.6 and v1.17.7 are certified ready for Sepolia’s Amsterdam fork on Oct 6, 2026
  • A new –history.chain flag lets operators set a custom block-and-hash pruning point
  • v1.17.7 latest Geth release tag, up from v1.17.6
  • Oct 6 Sepolia’s Amsterdam fork activation date
  • 5 new NodeOps bootnodes added to the client

The release is explicit about why it exists: “This is a quick release, cut mainly because publishing v1.17.6 to the Ubuntu PPA failed.” The notes add that “Both v1.17.6 and v1.17.7 are ready for the Amsterdam fork on Sepolia (Oct 6, 2026), so Sepolia validators can run either version,” meaning testnet validators are not forced onto the newer tag.

Custom History Pruning Lands via PR #35792

Node operators can now pick their own pruning point with –history.chain <block number>:<block hash>, shipped in pull request #35792. It works both for pruning an existing node through geth prune-history and for snap sync, where it skips downloading chain history before the chosen block.

That gives operators finer control over disk footprint than Geth’s prior fixed pruning presets.

Miner Gas Accounting Updated for EIP-8037

PR #35773 changes how the miner selects transactions for a block, now accounting for both execution and state gas under EIP-8037. This affects block builders and any operator running Geth as a miner or block-building client.

The release notes do not say which networks besides Sepolia have activated or scheduled EIP-8037, nor do they give a mainnet timeline.

Memory Leak Fix and Six Other Patches

PR #35821 fixes a memory leak by making the client wait for the block prefetcher to stop when the chain halts. Other changes in the same build: releasing pathdb clean caches when the database is disabled, encoding and hashing block-level access lists in one pipeline, restricting access-list fetches to blocks near the chain head, and restoring a txpool fallback that regressed in v1.17.3.

Five new multi-cloud bootnodes operated by NodeOps were also added alongside the existing bootnode set.

What Changes for Operators and Builders

Sepolia validators do not need to upgrade specifically for v1.17.7 since v1.17.6 already carries Amsterdam fork support; the update mainly fixes a packaging failure, not a consensus bug. Operators running low-storage or archive-adjacent nodes gain a new lever with –history.chain that was not available in v1.17.6 or earlier tags.

Miners and block-builder operators inherit the EIP-8037 gas-accounting change automatically on upgrade, since it alters transaction selection logic rather than adding an opt-in flag. The memory-leak fix in the prefetcher is a stability patch rather than a protocol change, relevant mainly to long-running nodes that previously saw creeping memory use on chain stalls.

This is a quick release, cut mainly because publishing v1.17.6 to the Ubuntu PPA failed.

Geth v1.17.7 release notes

The CCS read. A release forced by a packaging failure still shipped a real protocol-facing change in EIP-8037 gas accounting, a reminder that Geth’s patch cadence increasingly doubles as pre-fork plumbing for Sepolia rather than pure maintenance.

Sepolia’s Amsterdam fork activates Oct 6, 2026; validators on either v1.17.6 or v1.17.7 must be synced before that block.

Get this in your inboxThe Crypto Coin Show newsletter covers the policy and market moves institutional crypto investors are pricing in.

Subscribe

Lido committee plans to eliminate 1,500 ETH deposit reserve until October launch
Blockchain

Lido committee plans to eliminate 1,500 ETH deposit reserve until October launch

, , , , , , , ,

BlockchainCrypto Coin Show News Team·September 28, 2026·4 min read

Lido’s Curated Module Committee said in a Sept. 2 statement that it plans to cut the protocol’s 1,500 ETH deposit reserve target to zero once its new Easy Track authority is used, a move its own stress model shows would shorten worst-case stETH finalization from 7.9 days to 6.3 days. The committee also flagged a second step, restoring a 1,500 to 2,000 ETH reserve after a new staking module launches, which the same model puts at up to 8.5 days under stress, so institutional holders now have a direct stake in which way a five-person multisig turns the dial.

  • The Curated Module Committee’s 5-of-9 multisig gained Easy Track power to set the reserve on Sept. 25 but had filed no motion as of Sept. 27.
  • The committee’s plan would zero the reserve until 0x02 CSM’s mainnet launch, which it expects in October, then restore 1,500 to 2,000 ETH.
  • A governance-imposed ceiling caps any single committee-set target at 9,600 ETH, well above the current 1,500 ETH setting.
  • 1,500 ETH current deposit reserve, unchanged as of Sept. 27
  • 7.9 days modeled stress-case wait at 1,500 ETH versus 6.3 days at zero
  • 9,600 ETH committee’s ceiling for the target, versus 1,500 ETH now set

Lido’s buffer holds three priority-ordered pools of ETH, according to the protocol’s contract documentation: a deposits reserve, a withdrawals reserve for unfinalized stETH requests, and an unreserved pool that can fund either. The deposits reserve target, currently 1,500 ETH, decides how much of that buffer is walled off for validator deposits even when withdrawal demand is heavy. Governance handed the Curated Module Committee direct control over that number on Sept. 25, but the committee has yet to invoke it.

CMC says CMv2 migration no longer needs the 1,500 ETH buffer

The reserve was set at 1,500 ETH to guarantee deposits into Curated Module v2 during its migration from the earlier module, the committee wrote in its Sept. 2 statement. It now says CMv2 already holds the keys it needed for that migration, while the Community Staking Module has few depositable keys left before its 0x02 upgrade goes live.

In the committee’s reading, the protected reserve today mostly channels stake toward the now-legacy CMv1 rather than serving any active migration.

That is why the committee’s first proposed move is to cut the target to zero rather than raise it. Lido describes 0x02 CSM as a permissionless module already approved by the Lido DAO, with mainnet still pending; the committee points to an October target while Lido’s own documentation gives a broader fourth-quarter window. Once 0x02 CSM is live, the committee says it would consider restoring a 1,500 to 2,000 ETH reserve if node operators show demand for new validators, a step it calls Step 2 without committing to an exact figure.

Sizing analysis puts the stress-case gap at 1.6 days between zero and 2,000 ETH

The analysis used to size the initial reserve ran 500 simulations, each resampling 100 days from 360 days of historical staking inflows and withdrawal requests. Its high-stress scenario assumes roughly a 30-day Ethereum validator exit queue plus about five days for skimming and oracle processing. Under normal conditions the modeled ETH-weighted average finalization time barely moves: 2.3 days at zero reserve versus 2.6 days at 1,500 ETH.

The spread widens under stress. The model shows 6.3 days at zero, 7.9 days at 1,500 ETH, and 8.5 days at 2,000 ETH.

A 10,000 ETH scenario in the same study reaches a modeled 15.7 days under stress, though that figure sits above the 9,600 ETH ceiling set in the Easy Track governance proposal and the study includes no row at that exact limit.

The proposal gives the committee’s multisig authority to initiate motions up to 9,600 ETH, while the DAO retains the ability to object, set the target directly, or revoke the permission entirely.

What changes in practice for stETH holders queuing withdrawals

The mechanics matter only when withdrawal requests and executable validator deposits compete for the same limited buffer; with enough ETH to cover both, the reserve target makes little practical difference. A reduction below the currently active reserve takes effect immediately, while an increase waits for the next accounting oracle report before more ETH gets deposit priority, a lag Lido’s contract documentation confirms is built into the system. Holders who need ETH faster than the protocol queue allows can still sell stETH on secondary markets, where available liquidity and price determine the exchange.

The open question is timing, not mechanics. Whether the committee moves to zero before 0x02 CSM ships, and what exact figure between 1,500 and 2,000 ETH it later restores, remains undecided as of Sept. 27, according to CryptoSlate’s review of on-chain target-setting events and the reserve factory’s motion history.

Governance processes elsewhere in DeFi face a similar test of committee discretion versus DAO oversight, as seen in Aave governance’s review of a hub-and-spoke lending framework for V4, where a working group’s technical judgment likewise sits ahead of a full token-holder vote. Staged rollouts carrying an interim state before a fuller upgrade also echo a post-quantum cryptography proposal for Lightning’s offchain layers, which likewise phases changes around a not-yet-finalized milestone.

The CCS read. Large stETH holders should treat the reserve target as a liquidity dial they do not control and cannot predict from public data alone. A zero setting now would ease exits during any near-term stress, but that comfort is temporary and reverses the moment 0x02 CSM ships and operator demand justifies restoring the buffer. Treasury desks holding stETH as collateral should model both ends of the range, not just today’s setting.

The committee’s 5-of-9 multisig can open its first Easy Track motion at any time now that the factory is live, and its own timeline points to 0x02 CSM’s mainnet launch as the trigger for reversing course. Until that motion appears on-chain, the deposit reserve target sits at 1,500 ETH, and stETH holders in the withdrawal queue are working against a setting the committee has already said it intends to change.

Get this in your inboxThe Crypto Coin Show newsletter covers the policy and market moves institutional crypto investors are pricing in.

Subscribe

Load More