X Read BSV intelligence from X, every three days Archive
Issue No. 10Sep 12, 2026~6 min read

Teranode Patches, BSV Browser 1.6.0, and Bank of Japan's 500K TPS Target Put Scaling Back in Focus

This cycle's throughline: shipped infrastructure updates and a fresh BoJ CBDC benchmark gave the scaling-and-compliance pitch some external anchoring, even as the community's usual identity fights continued in the background.


What Mattered

Protocol and Technical

The concrete shipped work this cycle came from two posts by thebsvtimes. Teranode v0.15.9-beta-1 backports UTXO-related fixes targeting a condition that could wedge block validation and replay behavior involving transactions whose earlier records had been pruned. These are reliability patches, not new capacity features. Separately, BSV Browser 1.6.0 added an optional YubiKey-backed vault for encryption keys and encrypted remote recovery for wallet metadata, moving sensitive key material onto external hardware.

KallubiBSV made the Kallubi BSV Wallet source public on GitHub, with prebuilt files framed as convenience only.

Teranode's own account (BSVTeranode) continued its steady cadence of explainer posts on unbounded blocks, horizontal scaling, Go language choice, and side-by-side rollout alongside SV Node. These are recurring educational restatements rather than new announcements, but they set the framing that other accounts leaned on when the BoJ report dropped.

On the BRC-100 front, Uncledolfo reported that Yours Wallet's migration to the new BRC-100 standards has left MNEE UTXOs invisible in the wallet, asking the community and yoursxbt for help. Worth watching whether this gets a public fix or affects other assets.


Business and Adoption

The Bank of Japan CBDC pilot report was the external event that drove the most substantive discussion. VinceLaBido summarized the three features he saw as most aligned with BSV: the 500K TPS requirement, explicit UTXO model investigation, and the acknowledgment that single-account bottlenecks can't be fully solved in the current design. Vince50818862 amplified this to a wider audience with a post that hit 6,150 views claiming BSV handles all three natively. BullRushClub wrote a longer piece framing BSV as an answer to the BoJ's stated bottleneck. StrategyBSV cited a 1M TPS figure post-Teranode Chronicle upgrade, and BlockExtreme pitched a BSV Association partnership. GabrieleProBet claimed 75 million TPS in tests. Treat the specific TPS numbers with the usual skepticism, but the underlying BoJ document is a real external anchor the community can point to.

Two Clarity Act posts from BitcoinSvGuide framed pending Senate language around lawful freeze, seize, burn, and reissue capabilities as something BSV was architecturally early for. saltavallas1 also cited Clarity Act momentum as a reason to expect broader exchange availability. Whether any of this materializes in listings is unresolved.

New apps and product activity worth surfacing:

On adoption from the field, BitcoinSVCOL reported that several people in their local area have started accepting BSV as payment for small jobs. NickG222222 documented the multi-step friction of buying $500 of BSV through Rock Wallet after Rock Wallet moved to custodial status and deleted their account, ultimately paying about $41 in fees to route through USDC on Solana. Multiple accounts including BWDaugherty and MoonCoinRising picked up the thread, with Daugherty noting the exchange-listing effort has visibly regressed compared to two years ago.


Community and Discourse

The Blake2b/BIP-110 fork of BTC continued to dominate cross-camp discussion, with several BSV commentators drawing parallels. Arthur_van_Pelt tracked the Blake2b coin's price collapse (down to $120 on NeoxEX) and predicted it will find BSV-level lows around $10, comparing the seller pattern to BCH in 2018/2019 and BSV in late 2024. He also flagged that Blake2b community accounts are openly promoting theft of the forked coins from BTC holders, contrasting it with what he called Craig Wright's freeze-and-confiscate approach. BTCdrivechains published a comparison of eCash (BIP-300) and Blake2b (BIP-110) as two philosophically opposite forks that both went live this summer, which drew 3,853 views.

BSVCasey ran a community poll (183 responses) on priorities and asked for help acting on the top two results, though the specific items weren't detailed in-thread.

Hekto100 posted a longer reflection on frustration with BSV micropayment social platforms, arguing that adoption requires bridging existing user behavior before self-sovereign models can take hold. BSVCasey engaged directly in reply, agreeing self-custody of data is critical but treating it as an active-use goal rather than a solved problem.

BlockExtreme published a concise framing of BSV's design: consensus rules and protocol rules locked, node software and architecture free to evolve, positioned as Clarity Act-relevant.

VinceLaBido posted a reminder that the US Bitcoin Strategic Reserve, from pre-fork BTC seizures, also holds BCH and BSV holdings that the reserve legislation didn't cleanly address. 1,018 views.

kurtwuckertjr made a cross-camp point that holders can own BTC, BCH, and BSV without politicizing it and still see how far Bitcoin Core has drifted.

cryptorebel_SV raised concerns about Freemasonic symbolism in BSV projects, including what he described as a blue pyramid logo adopted by the BSV Association, and alleged targeted sabotage of non-Freemason developers. Unresolved and unverified, noted here because it drew replies.

CryptoCurrent77 asked what happens to the original BSV coin if XBSV on Proton becomes deemed the compliance-preferred token. No answer in-thread; worth tracking if Proton's role expands.


Other

The recurring "BSV is Bitcoin" posts, Hekto100's daily mood-and-price commentary, and GlucoseNot's Genesis-address explainer continued at their usual cadence. Notable within that stream: Twetch's twetchapp posted that BSV already hit $5 when adjusted for inflation, which drew 1,942 views.


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