X Read BSV intelligence from X, every three days Archive
Issue No. 18Oct 6, 2026~7 min read

Teranode v0.16.0 Ships as CMC Metadata Fight and Jack Liu Exit Rattle the Community

A quiet but real engineering release lands against a backdrop of listing-metadata disputes, developer infighting over BRC-100 compatibility, and the abrupt deletion of a prominent critic's account.


What Mattered

Protocol and Technical

Teranode's v0.16.0 regular release and immediate v0.16.1-beta-1 pre-release were reported by thebsvtimes and amplified by PacArtCollect, with the beta cycle described as continuing operational hardening around internal service access controls. This is the substantive protocol-level item of the window.

The most consequential developer-side story is johncalhooon's thread about BRC-100. He states that bsv-browser shipped a private blocklist on September 26 that prevents web apps from signing with BRC-29-derived keys, with no prompt and no release note, breaking mobile posting in his Zanaadu app. hbgnostic (Bridget) responded that BRC-100 still needs hardening and experimentation, and asked whether he has an alternative architecture in mind. nverston urged him to keep criticizing publicly, arguing the buggy implementation undermines BRC-100's "universal standard" claim. ProjectBabbage was tagged into adjacent threads but engaged more on the question of non-mining validation nodes rejecting invalid blocks than on the specific BRC-100 breakage.

Separately, ProjectBabbage posted a conceptual thread arguing that honest nodes following well-defined rules can reject attack blocks without needing hashpower, framed as a defense of the economic security model.

WuTao2023 pushed back on throughput narratives, noting that Teranode has shipped to mainnet only in limited form, that the 1M+ TPS figure remains a testnet number, that realized mainnet throughput is orders of magnitude lower, and that Teranode is still pre-1.0 four years after announcement. This is one of the few posts in the window grounding the capacity claims against observed usage. WilliamShortss added a data point in the same direction: roughly 34,000 transactions over 24 hours, averaging 0.4 TPS, with about $3.50 in total user-paid fees.


Apps, Launches and Infrastructure

Business, Listings and Metadata

GavinMehl's push on CoinMarketCap's BSV page — missing max supply, missing white paper — anchored several threads. He confirmed a law-firm letter was scheduled to go out on the 5th. captainordin backed the effort, pointing out the CMC page ranks #1 on Google for BSV queries. HAFPINTMUSIC tagged CMC directly about the misinformation. Internal pushback came from eightyATE, who argued the fix request should go to BSVA rather than CMC and framed Mehl's framing as overblown. WilliamShortss raised and then withdrew a theory that Vanguard's BSV ETF cashtag was conflicting with the crypto ticker, after MemeWaveApp pointed to Arweave as a counterexample of a smaller-cap asset with a working cashtag.

A separate thread from TrueECNBroker surfaced an unverified claim about Korea running daily transactions on BSV, sourced from a Vince50818862 quote. There is no corroborating announcement in this window, so treat as unresolved.

PacArtCollect noted Coinbase never listed BSV for buy/sell in the first place, in response to a Coin Bureau post about Coinbase delistings.

Kryptokrates published a substack piece on ICMA's bond-blueprint and what it implies for BSV's answer on where tokenized bond settlement actually routes — worth reading for anyone tracking the tokenized-securities adoption angle.

BullRushClub posted two pieces linking BSV's capacity story to external developments: Robinhood's September 29 in-app AI trading agent, and the AWS write-up citing a six-region, two-week, 1M TPS, zero-loss test on an SV node. Framed as "the rails are ready, the demand hasn't routed here yet."


Community and Discourse

The dominant interpersonal story was Jack Liu ("Jek") deleting his X account, flagged by BgansBSV and widely discussed. Reactions split cleanly: BgansBSV, captainordin ("I was the front man in the early days… Jack is a troll"), and BSVB4U framed it as a necessary departure of a bad-faith critic; cryptorebel_SV wondered aloud who the next recurring detractor will be; ctblizzard noted Liu had participated in a 6.5-hour BSV Twitter space just before deleting and expected him to return. BitcoinSVCOL drew a parallel to Joshua Henslee's earlier departure and framed both as "double agents." ChadCollin50662 pointed out NasdaqNancy appears to be a parody/troll account mocking the community, which is worth keeping in mind when reading the "call me" posts.

Rafael LaVerde (vamosvigilante) took a related but distinct line: that BSV's technical moat is closing as T+1 settlement, tokenized stocks, and other institutional rails route elsewhere, and that insiders in BSV are themselves the obstacle to listings. He also pressed BSVAssociation publicly on when BSV will be listed on Hyperliquid — no answer in the window.

Joel Dalais posted a long acknowledgment of Craig Wright's foundational contribution, which drew significant engagement and should be read as a loyalty statement rather than news.

A UK legal thread from tuftythecat summarized a hearing before Mellor J on the BSV delisting class action, including the amendment seeking to treat non-selling holders as if they had sold on a single assumed day, and provided price context around the April 2019 delistings. This is a live case worth tracking.

BitcoinSvGuide offered a more skeptical frame, arguing that BSV at $200 doesn't make sense in a world where BTC is $80K+ and ETH/SOL trade where they do, and that the valuation gap suggests the broader market system "isn't worth playing."


Background and Evergreen

The @BSVTeranode account continued its daily themed scaling posts (IoT, healthcare, supply chain, AI integrity, micropayments, gaming), restating already-established Teranode capacity claims. These are routine educational posts, not announcements. Similarly, PacArtCollect, Allheart_08, saltavallas1, Hekto100, and others ran their usual "BSV is Bitcoin / stack now / insurance policy" cadence; none of this is news, though PacArtCollect's note that BSV processed 4GB blocks and 2.5M-tx blocks as early as 2022 is a useful historical reference point.


Unresolved

What to Watch
Full sources for this issue →
The archive
Browse past issues →