Mathieu Geukens

#CashTokens is the #BitcoinCash comeback, join!

Background on the Starship story

On this day in history, 16 years ago, Satoshi Nakamoto explained why Bitcoin is safe from quantum computing breaking the software because, “When you run the upgraded software for the first time, it would re-sign all of your money with the new stronger signature algorithm”

@fran__dv Oh very cool! Exciting developments! 😃

An update on this answer: Given the interest, we'll have a "US Gift Cards" category from day 0 of the beta. Just a few items at first, for those who want to try the app. Full US and international support may come sooner than we expected👀

@steve603z @TheBCHPodcast Well, we're launching exactly that soon. But not only gift cards: You'll also be able to pay for services like electricity, gas, water, etc... Or subscriptions like Patreon... Everything in Bitcoin Cash, with a seamless UX. Follow @PagoconBit to stay updated!

The next episode of The BCH Podcast will be live tomorrow (Saturday) 11th July at 14:00 UTC. #186: CashMint feat Nilupul The @CashMintLabs dev joins us to talk starting @BCHcash_mint as an NFT marketplace on BCH, @BCHMinty, Ethereum's pivot to "native UTXOs", BIP-110 & more.

@BitcoinCashOG "We’re now at the point where real Groth16 verification works on BCH today" 💯 maybe the most important takeway, thank you for emphasizing this point!

Latest update from the BCH Groth16 Verifier Competition - Standard BCH mainnet: Best verifier now does 32 inputs across 3 transactions - Single tx (non-standard): Already fits in one transaction - New "bch-spec" category (max 100kb scripts): 1 tx with 5 inputs - current best What Does it all Mean? Groth16 is a powerful zero-knowledge proof system. A "verifier" is the code that checks if a proof is valid. Running this efficiently inside Bitcoin Cash’s scripting language has been the challenge. The open competition at verifier.cash is rapidly shrinking these verifiers. We’re now at the point where real Groth16 verification works on BCH today and gets even better in relaxed/experimental modes. This is a big step toward native privacy features, confidential DeFi, and advanced on-chain applications - all without needing protocol changes. Full post + leaderboard below 👇 #BitcoinCash #BCH #ZK #Privacy

@bch_1_official excellent overview of the three week, high velocity timeline thanks for the write-up 🙏

Zero knowledge proofs on $BCH are becoming practical. Not theoretical. Actually fitting within BCH's consensus limits measured in bytes and opcode cost. Here is what happened. Groth16 is a zero knowledge proof system that produces the smallest and fastest proofs to verify. It is the standard used by ZCash for private transactions and L2 scaling. Running a Groth16 verifier on Bitcoin Cash has been a goal since the 2026 VM upgrades unlocked bounded loops and reusable functions. Mathieu Geukens mapped the Pareto frontier for Groth16 verifiers in BCH Script. The Pareto frontier is the curve of best possible tradeoffs between two competing goals. In this case bytesize, which determines user fees, and compute cost, which determines whether the verifier fits within BCH's VM budget. Geukens found that compute is the binding constraint, not byte size. The practical target for optimization is the lowest opcost point on the frontier. This finding matters because it tells every builder after him where to optimize. The engineering path is now mapped. verifier.cash turned this into a competitive leaderboard. 13 implementations on the BN254 curve from developers like mr-zwets, Toorik, and Richard Brady. The best BCH-native Groth16 verifier dropped 86% in size since the first fitting build in June from 1.8 MB to 240 KB. In three weeks. That is the velocity you get when constraints are clear and the work is open. BCH kept its script and transaction limits while enabling on-chain ZK verification. BCH kept them and split the work across 32 chained inputs, each staying under the 10,000 byte and 8 million opcost limits. The harder path produces better engineering. Geukens also built the CashTokens ecosystem. This is not a newcomer discovering BCH. It is the same builder who shipped the last generation of BCH programmability now pushing into zero knowledge proofs. This is what ecosystem maturity looks like. ZK on BCH enables private transactions, L2 scaling, and verifiable computation. All on a base layer designed for peer to peer cash with sound money properties. The leaderboard shows it happening now. Not a roadmap. An open competition with 13 entries and measurable progress.

Chat control in the EU, VPN restrictions in the UK. All in service of ensuring that the natives don't dare critique the regimes online. When the Brits and the rest of Europe has finally had enough of this, it'll be an explosive moment.

Update on the BCH script Groth16 Verifier competition: Currently the best BCH mainnet (standard) Groth16 verifier is 32 inputs across 3 txs, without standardness this fits a single tx we added a new category "bch-spec", with max script size is 100kb. Best: 1tx, 5 inputs

🔬 ZK Progress on Bitcoin Cash! BCH Developer and entrepreneur Mathieu Geukens mapped the Pareto frontier for Groth16 verifiers in BCH Script. (Pareto frontier = the curve of best possible trade-offs between two goals. You can’t improve one without hurting the other.) Here it shows the optimal balance between verifier bitesize (fees) and compute cost (opcost). Key finding: compute is the binding VM limit, so target the lowest-opcost point on the frontier. Graph + details: verifier.cash Important step toward practical zero-knowledge on BCH!

Cashonize v0.8.2 is live! Security improvements + important bug fixes for the cross-platform Bitcoin Cash wallet. BCH users - upgrade now for a safer experience.

📣 The moment is here. 📣 TypeScript 7 is officially released! 7️⃣ devblogs.microsoft.com/typescript/ann…

Cashonize v0.8.2 release 🦾 New in this release: Security improvements and important bug fixes. Users are encouraged to upgrade. See the full changelog on the release page: github.com/cashonize/cash…

CashAddr (the bitcoincash:q... format) was introduced specifically to make BCH addresses instantly recognisable and reduce the risk of accidentally sending to the wrong chain. Simple change, meaningful protection for everyday users. This is exactly the kind of thoughtful design that makes BCH better for real peer-to-peer cash.

Is this BCH bullpoasting? 👀💚

love to see it, viabtc setting a great example