Jonathan Silverblood

stu 🥪🥞 Verified account @stutxo · Nov 5

View quoted post on X

European Central Bank Verified account @ecb · Nov 4

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 ecb.europa.eu/press/blog/dat…

View quoted post on X

Jerry | Lightswarm Verified account @Lightswarm · Nov 5

Bitcoin Cash's 1-minute block proposal: Are we rushing toward the finish line?

I've been following the 1-minute block proposal (gitlab.com/0353F40E/fablo…), and while I support the concept in principle, I'm increasingly hesitant about the push toward the November 15 Chipnet activation and lock-in.

Faster confirmations could be a meaningful improvement for bitcoin-cash:native, especially for DeFi and other applications that depend on confirmed transactions.

But supporting the idea and being confident that it's ready are two very different things.

My biggest concern isn't necessarily the proposal itself. It's the process and the urgency surrounding it.

We're changing one of the most fundamental properties of Bitcoin Cash. This involves considerably more than producing blocks 10x faster. There are changes to timelocks, infrastructure requirements, network behavior, and potential security implications that deserve extensive scrutiny.

And frankly, I'm uncomfortable with the amount of social momentum being built around meeting the November 15 deadline.

Public endorsements are valuable, but popularity isn't technical validation. We should be encouraging critical review, not creating an environment where raising concerns feels like standing in the way of progress.

This also raises an important question about Chipnet.

The proposal is scheduled to activate on Chipnet six months ahead of mainnet. That's supposed to give us time to discover problems before they affect real users.

But what happens if we discover something serious?

Under the modern CHIP process, we haven't had to navigate a major redesign following Chipnet activation. That doesn't mean we'll never need to.

If the design is effectively locked in on November 15, how much flexibility remains to address fundamental issues discovered afterward?

And who decides whether a finding warrants a patch, a revision to the CHIP, or postponement of mainnet activation?

I think these questions deserve clear answers before the lock-in date in 10 days.

More importantly, I want to see the BCH community aggressively stress-test Chipnet.

Not just run a few transactions and confirm everything appears to work.

I mean deliberate, adversarial testing. Push the network to its limits. Challenge assumptions. Test abnormal conditions, node behavior, timelocks, infrastructure compatibility, and potential resource-exhaustion scenarios.

Invite developers, miners, infrastructure operators, and security researchers to actively try to break the proposed upgrade in a coordinated testing environment.

The objective should be to uncover problems, not merely demonstrate that the implementation works as intended.

Findings should be documented, independently reviewed, and addressed before the upgrade is considered mainnet-ready.

And if serious issues require revisiting the design, we should be willing to revisit it, even if that means missing May 2027.

I recognize the tremendous amount of work developers have put into this proposal, and I don't want that effort to go unappreciated.

But BCH has made substantial technical progress over the last several years. CashTokens, covenants, and VM improvements are still opening doors that the broader industry has barely explored.

We shouldn't feel pressured to rush fundamental consensus changes simply because faster block times are attractive or because there's momentum behind a particular deadline.

When presented with the option of either a rush job or a delayed release, I'd rather see BCH take another year to get something right than spend years dealing with the consequences of getting it wrong.

Chipnet should be where we try to break things, not where we begin assuming everything will work.

And if we aren't prepared to change course based on what we discover there, what exactly are we testing for?

As the old @Blizzard_Ent mantra goes - "It's ready when it's ready"

View quoted post on X