Good Morning Bitcoin, 30 October
Today's Snapshot
- 38 issuers tell OKXICE no
- CFTC sues Utah, tenth state in prediction market fight
- BSV node ships v1.2.3 throughput fixes
Tokenization's biggest names keep running into the limits of their own structures, and today's three stories show it in different ways. A compliance notice names 38 companies that want nothing to do with one tokenized venue, a federal regulator files its tenth lawsuit over the same jurisdictional question and BSV's node software ships a release focused on the unglamorous work of syncing and staying synced. Let's get into it:
OKXICE's own filing shows 38 companies blocking it from tokenizing their shares
The news
OKXICE TSV's public notice, dated 28 October 2026, lists 38 issuers under "Notice of Issuer Objection." Each is named with its ticker, including Microsoft, Alphabet, Goldman Sachs, JPMorgan Chase, Walmart, Eli Lilly, Oracle, Intel, IBM, Cisco, Wells Fargo and Coca-Cola.
OKXICE TSV is run by OKXICE LLC, a Texas joint venture split evenly between Intercontinental Exchange Holdings and OKC USA Holding. It operates under the SEC's Order Granting Temporary Conditional Exemptive Relief, published at 91 Fed. Reg. 60168 on 22 September 2026 and valid until 17 September 2031. Under that order, an issuer has 30 calendar days from notice to object, and an objection bars the venue outright.
The notice states OKXICE TSV holds no custody, runs no order book, extends no credit and conducts no primary offerings. Trading runs through permissioned Uniswap v4 pools on XLayer against USDC and USDG, with each Tokenized NMS Stock backed one for one by shares held by a broker-dealer the notice calls the "Tokenizer." An external audit by Certified Kernel Tech LLC is still pending before operations begin.
What's next?
The 30-day objection window continues to run for the remaining issuers OKXICE notified. The external audit by Certified Kernel Tech LLC has to clear before the venue can go live at all.
The Takeaway
The Takeaway: a named objector list is a scoreboard for who tokenization has not yet won over
Thirty-eight companies named individually in a regulatory filing isn't an abstract concern about tokenization. It's a documented refusal by specific issuers to let a third party tokenize their shares on terms they don't control. That's a countable number, not a sentiment.
BSV's approach never depended on an issuer's permission to wrap an existing security in a new wrapper. Data and payment rails built directly on BSV don't require a broker-dealer custodian standing between an asset and its tokenized form, because the asset and the record can be native to the chain from the start.
For builders, the contrast is practical: a venue that needs issuer consent, an SEC exemptive order with a hard expiry in 2031 and an external audit still pending has three separate points where the whole structure can stall. Infrastructure that doesn't depend on any of those approvals carries less of that risk by design.
The CFTC sues Utah, its tenth state action over prediction market jurisdiction
The news
On 27 October 2026, the CFTC announced a lawsuit against the State of Utah, seeking to stop the state from enforcing its own laws against CFTC-registered contract markets and exchanges operating under federal authority.
CFTC Chairman Michael S. Selig stated that "Congress entrusted the CFTC to be the federal regulator with sole responsibility to oversee these markets." The Commission's filing argues federal preemption: Congress gave it exclusive jurisdiction over commodity derivatives, and a state law can't obstruct a federally registered exchange's operation.
The Commission's announcement confirms it has already brought actions against nine other states before Utah and filed briefs in four federal courts of appeal and one state supreme court. Utah is the tenth state drawn into this specific jurisdictional dispute.
What's next?
The appellate briefs already filed in four federal circuits and one state supreme court will produce the first rulings testing whether federal preemption holds. Those outcomes will shape how the Utah case proceeds.
The Takeaway
The Takeaway: a regulator fighting the same battle ten times over is a cost that lands on every platform relying on it
Ten state lawsuits over one jurisdictional question is a pattern, not an incident. Any platform that built its prediction market product around CFTC registration now has to budget for a fifty-state legal campaign running alongside its business.
BSV-based payment and settlement systems aren't prediction market products and don't inherit this specific fight. But the underlying lesson applies broadly: a system whose legitimacy rests on winning the same jurisdictional argument state by state carries a cost structure that a permissionless, globally available settlement layer does not.
For builders weighing where to put transactional infrastructure, a chain level choice that avoids a multi-jurisdiction legal campaign as a precondition for operating is worth more than it might look on a feature list.
BSV node software version 1.2.3 targets block download and validation throughput
The news
The Bitcoin SV node repository's release notes for version 1.2.3, an upgrade from 1.2.2, describe a performance-focused release, chiefly targeting initial block download and block validation.
The release reconfigures the CoinsDB database with a larger default file size, a dynamically calculated open files limit and a dedicated cache setting. It also improves parallelism during block validation through optimised transaction grouping. Accelerated SHA-256 and merkle root computation via SHA-NI instructions have been added, and the Linux and BSD P2P socket loop switches from select() to poll(), removing a prior silent cap that held -maxconnections near 865 on poll() builds.
The release notes also add a rescanblockchain RPC command for wallet applications to rescan specific block ranges, optional USDT instrumentation for tracing RPC and P2P latency and bug fixes covering coins-cache memory accounting, block download tracker issues, out-of-range integer handling in OP_SPLIT and invalid memory access in CScript and the mempool eviction tracker. New configuration options -coinsdbcache and -prunehysteresis were added, with -maxcoinsdbfiles now dynamic at roughly 8192 and -maxcoinsdbfilesize set to 128MB.
What's next?
Node operators now have the release notes to work from when upgrading from 1.2.2. The removal of the poll()-based connection cap is the detail worth testing first on nodes running high connection counts.
The Takeaway
The Takeaway: removing a silent connection cap is the kind of fix that scaling claims have to survive contact with
A cap on -maxconnections near 865 that nobody set on purpose, quietly imposed by the choice of select() over poll(), is exactly the sort of limit that goes unnoticed until a network needs more connections than that. Removing it in 1.2.3 is a concrete step, not a promise.
The other changes point in the same direction: a dynamically sized CoinsDB file limit, a dedicated cache setting and SHA-NI accelerated hashing all target the same bottleneck, how fast a node can download and validate blocks as volume rises.
This is what distinguishes BSV's scaling claim from a slogan. A chain that says it can carry unbounded transaction volume has to keep shipping releases like this one, where the fix is in the database file handle limit and the socket loop, not in a marketing document.
What to Watch
- OKXICE objection window - watch for the 30-day deadline outcomes on issuers notified after 28 October. Each additional objection narrows what OKXICE TSV can actually list.
- CFTC v. Utah proceedings - rulings from the four federal appellate courts and one state supreme court already briefed will signal how the Utah case and future state suits are likely to land.
- BSV node upgrade to 1.2.3 - node operators moving from 1.2.2 should test the poll() based connection handling first. It's the change most likely to affect network capacity at scale.
Thirty-eight objectors, a tenth lawsuit and one dynamically sized database cache: the difference between a tokenization story and infrastructure is which of those three actually ships.