Jonathan Silverblood

Jack-of-most-trades that likes deep subjects like bitcoin, governance and energy.

Not a trained economist, please do not take my tweets as financial advice.

[Kallisti.cash 🍏 @kzKallisti]

I've been running a tempnet lab to gather live data on the upcoming BCH Faster Blocks upgrade before deployment.

https://t.co/HlTmRJ1bfi

You can broadcast a random transaction on tempnet and chipnet and watch your transaction get mined in real time.

We're also measuring how ABLA and DAA respond as well as time-to-first-confirmation in terms of both blocks and wallclock time.

Running this lab has effectively squashed any remaining unease I had about the upgrade! Check it out - suggestions welcome.

5 more days until lock-in!

[BCH BLAZE @bchblaze]

BCH runs on its organisations & projects, but most of all runs on its most passionate individual contributors.

@toorik is one of the most stalwart supporters of the BCH ecosystem. Check out his recent work on bringing shielded transactions to BCH. 🔥😱

Thanks Toorik! Legend.💚

[Jonathan Silverblood @monsterbitar]

@christine_dkim Meanwhile, in BCH land...

[General Protocols @GeneralProtocol]

Bitcoin Cash might have an unexpected advantage: a fresh look with a solid history and multiple upgrades.
After years of controversy and hostility, much of the early BCH drama has faded. Now a new generation of crypto users can discover Bitcoin Cash without all that historical baggage - @TheDesertLynx, BCH Bliss 2026
https://t.co/1zrjIlBQIC

[Knuth @KnuthNode]

🚀 Knuth v1.6.0 is out.

⏱️ Faster Blocks: implementation of CHIP-2025-03 and tempnet support for testing 1-minute Bitcoin Cash blocks, with tick metadata exposed through JSON-RPC and the C API.

🌐 Knuth node in your browser: powered by WebAssembly and WebSockets, with multiple peers and persistent chain state across reloads.

🔌 More integration options: expanded JSON-RPC coverage, plus optional gRPC and Cap’n Proto query backends.

🛡️ Stronger transaction relay, orphan handling, mempool limits, and recovery after invalid blocks.

🔐 A new full-validation IBD mode verifies scripts and signatures from block 1, keeping checkpoints only as header anchors.

⚡ Recent mainnet IBD runs, from genesis to tip on the same Ryzen 9 9950X3D + NVMe machine:
• Checkpoint mode: **1h 03m**
• Full script and signature validation: **2h 07m**

The full-validation result includes additional storage and batching optimizations now on master, beyond v1.6.0.

🔗 https://t.co/FMFwpSMnXj

#Bitcoin #Cash #BCH #Knuth #Cpp23 #WebAssembly

[Jonathan Silverblood @monsterbitar]

and looking at the reasoning, to get an even better grade all that's needed is to.. use it more?

like, more active addresses and transactions per day are currently dragging the ranking down xD

[Jonathan Silverblood @monsterbitar]

https://t.co/NqNu27JclI

A++, #1, Cool stuff.

[Jonathan Silverblood @monsterbitar]

@im_uname like all other fields, crypto have to adapt.

formal specifications allows for non-open-source implementations that are opaque and harder to "search for bugs in", for example.

Not my go-to, hopefully not needed, but future will look different from the past, one way or another.

[Jonathan Silverblood @monsterbitar]

@im_uname It's a phase/cycle. Utility wins long-term.

[Jonathan Silverblood @monsterbitar]

@kzKallisti I'm confident the number is higher now, since from start of the poll there has been a lot of engagement and positive coverage. That said, a twitter poll is still just a twitter poll - subject to algorithmic overlords xD

[Jonathan Silverblood @monsterbitar]

pre lock-in selloff is weird. xD

[General Protocols @GeneralProtocol]

If an entire blockchain relies on a single privacy mechanism, everyone shares the risk if it fails.
Competing privacy protocols at the scripting layer offer a different approach. @monsterbitar explains why diversity matters 👇

[emergent_reasons#100🌵 @EmergentReasons]

You don't hate KYC enough.
https://t.co/EkhfKb5lsm

[Jonathan Silverblood @monsterbitar]

There's a lot of vulnurabilities out there and dealing with them is a normal part of operations, but somehow 2026 takes the cake and sets a whole new standard for how bad things can be on the internet -.-

[Jonathan Silverblood @monsterbitar]

We don't need more monetary system, more regulation and more costs. We need more freedom. #Deregulate

[European Central Bank @ecb]

Extreme weather is becoming more frequent and more severe, and the associated costs are rising.

Europe needs better protection against the financial fallout from climate change and a more flexible energy system, says President @Lagarde in her blog post https://t.co/kJ0xWaJHk9

[Jonathan Silverblood @monsterbitar]

@Lightswarm @cculianu BCHN and Knuth is mining on tempnet. Activation clients are not released yet, but are expected to be out well ahead of activation.

[比特幣現金台灣 (Bitcoin Cash Taiwan) 🇹🇼 @twbitcoincash]

#bitcoincash
#bch

Following careful research, observation, and the dedicated efforts of developers in operating the testnet.

We have decided to shift our stance from "Neutral" to Supportive—and we now advocate for a lock-in this year!

[Kallisti.cash 🍏 @kzKallisti]

Jerry thoughtfully asks: what happens if something goes wrong on Chipnet AFTER November 15, 2026, but BEFORE May 15, 2027?

It's a good question, and worth asking! Contingency plans are a good thing!

It seems there is already some alignment forming on simply canceling the upgrade if there is some catastrophic discovery found during the chipnet window.

Kallisti: "I would issue my own statement that I would not upgrade my infrastructure to the new version."

Jeremy: "We are prepared to change course."

Silverblood: "The first step is to fix it. If not possible in time, then next step is to cancel activation."

Molecc: "If fundamental problems are found that require a redesign, I'll be one of the first to support cancellation."

We are a reasonable and pragmatic community, and we measure proposals on technical merit, not emotional appeals. We are engineers. If there's a problem, we simply fix it.

Any reasonable objection must be met with a reasonable answer by the CHIP author(s). This is the standard. The author, in my opinion, has met this standard.

Jerry is asking a reasonable question, and the answer is equally reasonable. We will not ship a breaking change to mainnet.

Let us have confidence in the 18+ months of planning, research, and discussion that went into this proposal compared to the relative simplicity of the blocktime parameter. Let us also have confidence in the BCHN, BCHD, and Knuth test suites, as well as the universal VM fuzz tests Jason made for us with the VMLA upgrade.

Let us not mysticize the blocktime target like was done to the blocksize cap. :)

[Jonathan Silverblood @monsterbitar]

@TheBCHPodcast I share this understanding. The lock-in is for the chip as documented at the time, and so any changes that isn't local implementation changes but actually changes the behavior or requirements of the chip has not been agreed to and should therefor go back to the drawing board.

[Jonathan Silverblood @monsterbitar]

@nknownonx @Lightswarm I know of at least: testnet3, testnet4, scalenet, chipnet, tempnet and various local regnets.