Jerry | Lightswarm

This account is verified. Learn more

@Lightswarm

$BCH @optnlabs. Opinions are my own. Brood War Maxi.

Toronto, Ontario optnlabs.com Joined June 2009

1.5K Following 2.1K Followers 20K Posts

Latest posts 5

Pinned post

Jerry | Lightswarm @Lightswarm Aug 16

We got localization support for

English
Spanish
Portuguese
French
Chinese (Simplified / Traditional)
Japanese
Korean
Vietnamese
Russian
Arabic
Hausa (Nigeria)

Reach out if you want to help with the translations - Codex translations can definitely use improvements

OPTN Labs @OPTNLabs Aug 16

OPTN Wallet v1.7.3 released

Key updates include:
- improved wallet sync
-updated cashfusion
- expanded localization to 12 languages

Download links below:
Google Play - play.google.com/store/apps/det…

Direct Download - github.com/OPTNLabs/OPTNW…
View quoted post on X

Jerry | Lightswarm @Lightswarm 2d

This is the way

Cauldron 🧪✨ Verified account @CauldronSwap 2d

On @CauldronSwap:

🧪 LPs own 100% of their pools
🔮 Flat 0% platform swap fee
🪄 LPs can exit pools anytime
📚 Pools are non-custodial

cauldron.quest
View quoted post on X

Jerry | Lightswarm @Lightswarm Nov 5

Let's put bitcoin-cash:native's 1-minute blocks to the test. 🔥

It's been encouraging to see the different perspectives and technical discussions around the upcoming 1-minute block upgrade, but publicly and in private chats.

While opinions differ on readiness and implementation, I think there's something we can all contribute toward: gathering more real-world technical data.

With Chipnet activation approaching on November 15, @OPTNLabs is planning to lead a community-level testing initiative, focused on understanding how the new block cadence affects BCH and its surrounding infrastructure.

Here's what we're looking to coordinate:

- DeFi stress testing: Use Cauldron swaps and coordinated trading bots to gradually ramp up transaction volume, test competing liquidity-pool UTXOs, and identify bottlenecks.

- Network and infrastructure: Encourage independent Chipnet nodes and indexers to measure block propagation, synchronization, resource consumption, and performance under load.

- Smart contract compatibility: Run separate tests covering timelocks, covenants, CashTokens, and legacy transaction behavior under the new rules.

- Wallets and SPV: Examine header synchronization, bandwidth overhead, and application reliability with 10x more frequent blocks.

We'd like to provide setup guides, open-source testing tools, and a way for participants to contribute their own measurements.

Most importantly, we want the results to be transparent and reproducible.

That means publishing the methodology, configurations, raw measurements, and findings—including anything that doesn't perform as expected.

The goal isn't to prove the upgrade is good or bad, or to tell anyone what conclusion to reach. It's to give the community better technical evidence to evaluate the changes ahead of mainnet activation.

With @bchblaze happening around the same time, it's also a great opportunity for more builders to get hands-on with BCH infrastructure. This is an independent community effort, not an official hackathon activity.

We're aiming to begin shortly after November 15 and would love to hear from anyone interested in running infrastructure, contributing bots or test cases, or helping collect and analyze the results.

More data, less guesswork. Let's build and test together.

#BitcoinCash #BCH

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

Jerry | Lightswarm @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"

gitlab.com ac-0353f40e / Faster Blocks for Bitcoin Cash · GitLab Faster Blocks for Bitcoin Cash (fa-blo-us: faster blocks for us)

Jerry | Lightswarm @Lightswarm Nov 5

I wonder how Texas managed to flip blue 🤔🤔🤔

Larry Dean Verified account @larry_mcwethy Nov 5

And this is just the tip of the iceberg!
TEXAS REPORT REVEALS 2.9 MILLION NEW VOTER REGISTRATIONS WITHOUT PROOF OF CITIZENSHIP
Austin, TX - November 5, 2026
An Official Election Administration and Voting Comprehensive Report buried all the way on page 193 of the document shows Texas processed 2,900,357 new valid voter registrations between 2022 and 2024 without proof of citizenship. Documented proof of citizenship like birth certificate, passport and naturalization papers is not required at the time of voter registration in Texas. This loophole allowed millions of names onto the rolls with no verification that the applicants were eligible citizens.

View quoted post on X