Bitwise Sent the SEC Two Letters in 48 Hours. Both Ask the Same Unanswered Question.

Who's liable when a token-status filing turns out to be wrong? That's the question Bitwise put in front of the SEC on October 21. And it's the one question the crypto fund business needs answered before it can size a single position.

Here's what happened. Bitwise filed a supplemental comment letter with the SEC on October 21. It builds on an earlier letter from October 19. Both land in the comment file for the proposed Regulation Crypto Assets framework, docket S7-2026-27. Two letters. Forty-eight hours apart. Same argument, sharper edges.

That's not a company throwing opinions at a wall. That's a company watching its own product roadmap and asking the regulator to close a gap.

The Gap, In Plain English

Regulation Crypto Assets proposes a process where a token issuer files a Form TR to declare that its asset has separated from an investment contract. Fine. But that filing gets made by the issuer. The people who actually need the answer are the ones building products around the asset, and they're working off public information.

So Bitwise wants the SEC to separate two things. One, an issuer filing Form TR. Two, the moment a separate market participant can rely on an unchallenged filing.

Those aren't the same event. Not even close.

The letter asks for three more things on top of that. Protection for reasonable, good-faith determinations if somebody challenges the filing later. A rule that filing Form TR isn't an admission about the asset's previous legal status. And for that treatment to carry through the investment company and investment adviser definitions.

Three requests. All of them about consequences, not paperwork.

That last one is the tell. If filing Form TR can be spun as an admission that the asset used to be a security, no issuer with a real legal budget files it. Then the framework is dead on arrival and everyone keeps pretending 2026 is 2018.

Why This Is a Liability Story

Headlines will call this regulatory progress. It isn't. This is an industry participant drafting the liability shield the SEC hasn't written yet.

And that's the honest read. Bullish on hopium. Bearish on math.

Think about the structure. A fund manager holds a token. She has public filings, a legal memo, and no access to the issuer's internal records. Something goes sideways two years later. The SEC's position at that point determines whether she relied on a filing in good faith or whether she should've known better.

That "should've known better" is the whole ballgame. It's the difference between a compliance line item and an enforcement action.

The supplement is explicit that it's asking about consequences, not simply whether the form exists. Bitwise's first letter made the same point from a different angle: it builds investment products from crypto assets, it doesn't issue them. The information asymmetry is structural. It's not a mistake, and it doesn't get fixed by better disclosure.

Now zoom out. The investment company and investment adviser definitions are where registered funds live or die. If a token's status under those definitions doesn't track the reliance framework, you get the worst outcome available: an asset that's fine to trade and impossible to hold in a registered vehicle. Distribution without access. Great deal for offshore venues. Terrible deal for US bag holders who wanted a wrapper.

This ends badly. The data already knows it.

What the Buy Side Is Saying

Fund managers watching docket S7-2026-27 will tell you the same thing off the record. Nobody's waiting on the adoption release to make product decisions. They're waiting on one sentence inside that release defining when reliance is reasonable.

According to the two letters, that sentence doesn't exist yet.

Here's the part that should annoy you. Bitwise is doing work the commission's own staff should have done before publishing a proposal. Framing the reliance question. Mapping it into the adviser definitions. Flagging the admission risk on Form TR. That's drafting. Free drafting. From a firm that manages money, not one that writes rules.

Is that a healthy comment process or a sign the proposal shipped half-finished? Both. It's both.

There's a second-order problem nobody's pricing. A reliance safe harbor protects the middleman. It doesn't tell you whether the token is a security. So you get a world where funds can hold an asset with legal cover while the underlying legal status stays foggy for years. That fog is a cost. It shows up in fees, in insurance, in how large a position any desk will take. Ambiguity isn't free. It's just invoiced later.

Everyone has a plan until liquidation hits. Ask anyone who held through a delisting.

What to Watch

Three concrete things. First, whether the adopting release for Regulation Crypto Assets contains an explicit reliance standard for non-issuer market participants, or whether it just describes the Form TR mechanics and leaves reliance to the courts. If it's the latter, this letter failed.

Second, the effective date and operational details for Form TR itself. A form with no reliance consequence is a PDF with extra steps.

Third, watch the amendment text for the investment company and investment adviser definitions. If a Form TR submission doesn't cross-reference cleanly into those definitions, registered funds stay locked out no matter what the framework says.

The comment file is open and the docket is S7-2026-27. Read the October 21 supplement yourself, all of it. The summary version floating around misses the point.

Bitwise asked a good question. The SEC hasn't answered it. And until it does, every fund holding a token with a fresh Form TR is running on hopium and a legal opinion.