Bitwise Amends Spot Ethereum ETF Filing to Add Staking, Slashing Language

Bitwise has filed an amended S-1 registration statement for its spot Ethereum ETF, adding new language covering staking mechanics, validator operations, slashing risk, and staking-yield accounting, according to a September 7 report from NewsBTC. As of this writing, no second independent outlet in our source set has corroborated the filing’s contents, so this is a single-sourced claim worth flagging before it hardens into consensus.

What’s Actually Confirmed, and by Whom

The core claim is narrow: Bitwise submitted an amended S-1 for its spot ETH ETF that inserts staking-related disclosures. That includes how validators would operate, how slashing penalties could hit fund assets, and how any staking yield would be accounted for on the fund’s books. NewsBTC’s report points readers to the SEC’s public filing platform for the underlying document.

What the report does not claim is equally important. There is no approval attached to this amendment. Bitwise is proposing a mechanism, not receiving a green light. The SEC has not authorized staking inside any spot Ethereum ETF to date, and nothing in the reporting suggests that status has changed.

Why the Staking Language Matters

Ether is not a passive holding the way gold or a currency reserve can be. It secures a proof-of-stake network, and validators who lock it up earn rewards for doing so. A spot ETF that simply holds ETH without staking leaves that yield on the table, a gap competing products have flagged for over a year.

Building staking mechanics directly into an S-1, rather than leaving it for a future amendment, signals that Bitwise wants the operational plumbing in place before regulators even consider the question. Slashing risk disclosure matters here specifically: if a validator misbehaves or goes offline, a portion of staked ETH can be forfeited, and any ETF passing that yield through to shareholders needs a documented answer for who absorbs that loss.

What Remains Unverified

We have not seen a second outlet reproduce the specific S-1 language, the exact date of the filing beyond NewsBTC’s September 7 timestamp, or confirmation of which validator or custody partner Bitwise names in the document, if any. Readers building on this should treat it as one report until the underlying SEC filing is checked directly, not as a confirmed regulatory milestone.

The distinction is not cosmetic. A filing amendment is a company’s request; an SEC approval is a regulator’s decision. Those two things get conflated constantly in crypto ETF coverage, and this is exactly the kind of story where a 20-minute wait for a second confirmed source beats a fast but shaky headline.

Sources

• newsbtc.com
• bitcoinist.com