UTXO citizen. Not your keys, not your coins.

MyTwatterHandle 🟩 retweeted
🔥 #BCH meets #XMR, wtf?! Sent to one address, but a different address got the bitcoin-cash:native? Something is off here >> or is it just private? I think #Zcash just got serious competition. This tx is already post-quantum, verified on-chain. Let that sink in $ZEC.
15
32
132
8,735
MyTwatterHandle 🟩 retweeted
Two ZK proof systems verified natively on BCH's base layer. No sidechain. No rollup. No custom execution environment. Just the BCH virtual machine, running on Chipnet, accepting or rejecting transactions based on whether the cryptographic proof checked out. The common assumption is that Bitcoin-style chains are too constrained for ZK verification. Bitcoin Script is a simple stack machine designed for spending conditions — not for the large-integer arithmetic that elliptic-curve pairings and polynomial commitments require. If you want ZK on a Bitcoin-family chain, the conventional answer is: build a separate execution environment and bridge to it. BCH took a different path. And the result is on-chain, verifiable, and replicable by anyone running a Chipnet node. The first demonstration is ShieldKit, built by Toorik. It implements a Groth16 zk-SNARK verifier on the bn254 curve, compressed to 54 kilobytes, running inside a single standard BCH transaction. The use case is a shielded pool: a user computes a proof offline that they're authorized to deposit or withdraw, submits it to the on-chain verifier, and the transaction either satisfies the constraint or it doesn't. No trusted intermediary. The proof is the authorization. Genesis, deposit, and withdrawal transactions are publicly viewable on Chaingraph's Chipnet explorer. Open source on GitHub. The second is BCH-FRI-STARK-Verifier, built by 0zkbrewer. A hash-based DEEP-ALI FRI-STARK verifier — structurally different from Groth16, built on different mathematics. Where Groth16 uses elliptic-curve pairings, FRI-STARKs use hash chains and polynomial commitments. The verifier runs on the unmodified BCH VM via a multi-input P2SH32 covenant transaction where the spend itself is the verification. A demo version was funded and spent on Chipnet at block heights 314509-314510: 28 covenant inputs, 92,191 bytes. The network accepted it. That acceptance is on-chain proof the covenants executed correctly. Now the comparison that matters. BTC's script VM has not received a meaningful capability expansion since Taproot in November 2021. The conversation around covenants and OP_CAT on BTC has been running for years with no activation date. Michael Saylor framed BTC's consensus rules as a "constitution" in 2026 — arguing base-layer changes should be rare and require near-unanimity, explicitly including covenants in that framing. BTC's resistance to base-layer change is a deliberate design goal. Immutability is the point. The result is that a comparable ZK verifier on BTC's base layer would require a consensus change. That's the kind of change currently in explicit dispute. BCH's VM expansions came through the CHIP process on the annual May 15 schedule. The U8 upgrade in 2022 added native transaction introspection and 64-bit integer arithmetic. The VMLA upgrade in 2025 delivered CHIP-2024-07 BigInt — removing the VM's fixed integer length limit entirely. Before that, BCH Script was capped at 8-byte integers. ZK proof verification requires arithmetic over numbers far larger than 2^64. Pairing operations in Groth16 and polynomial evaluations in FRI-STARKs both need field-element arithmetic that a 64-bit cap cannot support. BigInt removed that ceiling. Integers are now bounded only by the 10,000-byte stack element limit. The Layla upgrade in 2026 added bounded loops and function definitions — a verifier that needs to iterate over proof components can now do that with a loop rather than duplicated bytecode. Two different proof systems. One base layer. The reason both worked is that the VM became general-purpose enough through incremental upgrades to handle the underlying mathematics of each. The honest status of both projects: neither is mainnet-ready. ShieldKit is unaudited and development-only. The FRI-STARK verifier is explicitly labeled research code by its author — a fully soundness-wired version currently runs 120,537 bytes, over BCH's 100KB standard-transaction limit, and byte-reduction work is in progress. Both are real, on-chain, and testable on Chipnet today. Not finished products. The structural point is what the comparison reveals. A Groth16 SNARK and a FRI-STARK are built on fundamentally different cryptographic assumptions. If only one had verified natively on BCH, you might reasonably call it a coincidence — some alignment between that specific proof system's math and what BCH Script happens to compute. Both working independently is evidence the VM's capability expansion was general-purpose, not narrowly tailored to one scheme. BTC's VM, unchanged since 2021, cannot run either. The scripts that make ShieldKit and the FRI-STARK verifier possible — BigInt arithmetic, bounded loops, P2SH32 covenants — do not exist on BTC. A ZK application on BTC today goes to a sidechain or a rollup. On $BCH, two independent teams demonstrated it in the base layer, on testnet, using the VM that every full node already runs. One chain's VM has been expanding on a predictable annual schedule. The other's has been stable by design. The ZK verification capability is a direct output of that difference.
2
4
26
618
Yup. BCH has quantum safety. BTC does not.
BTC's quantum plan requires a soft fork nobody agrees on and a proposal to freeze Satoshi's coins. BCH's shipped in a wallet, because the VM was expressive enough to do it without asking.
1
3
19
379
MyTwatterHandle 🟩 retweeted
Damn Ukraine! 😂
351
9,071
43,393
1,167,296
MyTwatterHandle 🟩 retweeted
Donald Trump Jr.’s lavish Bahamas wedding was secretly bankrolled by a Russian oligarch close to Putin—ProPublica
77
775
4,591
181,911
Another fun fact - Clinton was the ONLY president in recent times that actually managed a surplus in Federal budget. Isn't that interesting?
Билл Клинтон: «МЫ заставили Украину отказаться от ядерного оружия, крылатых ракет и стратегических бомбардировщиков, МЫ обещали защитить Украину от России, МЫ сделали Украину уязвимой. Так что да, это НАША война». Когда говорит Президент США, а не аферист-девелопер с Манхэттена.
74
Indeed. Dumb as a door mat.
Trump: “We could do tremendous good for ourselves by just not trading with countries. We lose $200 billion dollars a year with the European Union. If I didn't trade with them, we would lose nothing.” Dumbest. President. Ever.
2
45
MyTwatterHandle 🟩 retweeted
$SIVE announced today that it is expanding InP manufacturing in Glasgow. The new capacity target is: ~100 million CW DFB laser annual production. Using Sivers’ historical $50-$100 per 8-laser array pricing, the implied revenue capacity might be ~$625M-$1.25B/year (not guidance, just illustrative modeling) I’m personally very surprised by the amount of capacity coming online from their new hybrid manufacturing model, targeted Q4 2027. Especially during an industry shortage, mentioned by $AVGO earnings call today.
110
92
1,374
289,753
MyTwatterHandle 🟩 retweeted
This is real decentralized, peer-to-peer cash revolution happening in the Philippines. No custodians. No middlemen. Just people transacting directly with people. Powered by Bitcoin Cash! #BitcoinCash #BCH #Paytaca
The future of #CryptoPH is decentralized—literally. 🇵🇭 🚨 While major capital cities often host community meetups and nationwide events, regional hubs like Tacloban and Cebu are quietly laying down the infrastructure for practical web3 utility. Want to learn how Tacloban and Cebu are driving the next wave of local crypto expansion? Read our full coverage below! 👇 @_paytaca_ 👉 Full Details: bitpinas.com/go/bcconf
1
15
40
859
MyTwatterHandle 🟩 retweeted
Bitcoin Cash is money. So how many ways can you spend it? ⚡️ We’re kicking off BCH Explore with 3 real-world options: 🇳🇬 PaySats — airtime & data 🛒 Bitgree — shop online with BCH 🇦🇷 ParagonBit — gift cards, coming soon More BCH utility to explore. 🌍
6
21
58
1,950
MyTwatterHandle 🟩 retweeted
The Knots guys have discovered pruning+SPV to solve IBD. If they'd read the Bitcoin whitepaper, as we recommended them often, they could have had this information since 2009. UTXO commitments will be next. Regardless, it is good to see that once again all roads lead to BCH.
I stripped every spam carrier out of 194,863 Bitcoin blocks, wrote the result to disk, then re-verified all 194,863 against their own headers reading nothing but the stripped store. Zero failures. No fork. No confiscation. Nobody's permission. Here's the mechanism and what fell out of it. — WHY A BLOCK SURVIVES LOSING ITS DATA A block's merkle root is computed over txids. Store the 32-byte txid of every transaction you modify or discard, and nothing downstream ever needs to re-derive it from transaction data. So the data can go and the block still verifies against its header — against real proof-of-work. The stored txids are self-verifying. Fabricate one and the merkle root stops matching the header. The list can't be forged. Transactions you don't touch cost nothing extra; the reader computes those txids itself. Only modified transactions pay 32 bytes. This is what the standard objection misses. "You can't remove OP_RETURN, it's committed inside the txid" is true only for designs that *recompute* txids. It doesn't apply when the txid is stored. — WHAT CAME OUT Blocks 767,430–962,292 on a fully synced Knots node: Inscription envelopes (taproot witness): 37.1 GB Stamp-style bare multisig: 77.5 MB OP_RETURN over 83 bytes: 12.3 MB Oversized scriptSig: 13.8 KB Total spam: 37.2 GB — 12.56% of block bytes in that era. 80.66% of transactions were left completely untouched. — THE DETECTOR THAT LIED TO ME My first run reported 0 bytes of stamp-style bare multisig. I published that. It was wrong. The detector flagged keys whose first byte wasn't 02, 03 or 04 — but Stamps deliberately use those prefixes so their outputs pass standardness. It caught nothing and returned a clean zero, which is the worst possible failure, because a zero reads as a finding. The fix: check whether each key is actually a point on secp256k1. Compute y² = x³ + 7 mod p, test quadratic residuosity by Euler's criterion. A real pubkey always passes. Arbitrary data passes about half the time, so one key proves little — but a bare multisig carries several and the odds halve with each one. Real figure: 77.5 MB. Cross-checked against an independent UTXO-set scan that found 2.6M unspent bare multisig outputs. — THE FINDING I DIDN'T EXPECT 806,626 outputs were dropped from block storage. Each kept a filter entry — outpoint, amount, scriptPubKey, height — so a future spend could still be validated locally, with no peer involved. How many of those 806,626 were ever spent? Seven. One in 115,000. Monetary outputs get spent because someone wants the coins. Data carriers sit forever because nobody ever wanted the coins, only the bytes. That's a measured distinction between money and data, not an opinion about it. All seven had their filter entry. Six had their ECDSA signatures re-verified against scriptPubKeys recovered from the index — one a 2-of-2 requiring both keys. Cryptographic proof that deleting an output doesn't strand it. — AND THE SEVENTH The seventh failed verification, and the reason is more interesting than the six successes. SIGHASH_ALL signs the spending transaction's outputs, not just its inputs. That transaction spent a bare multisig output *and created another one* — which my stripper removed. The signature is valid; the preimage it committed to no longer exists. Stamps transactions consume and produce bare multisig by design, so they're precisely the transactions this hits. The precise statement: transactions retained whole (80.66%) keep full signature re-verifiability. Modified ones (19.34%) don't. All were validated in full, once, by Knots, when the block was connected. I'd previously written "stripped transactions cannot be re-verified." Too loose. This is narrower and it's the correct claim. — WALLETS STILL WORK Balances and transaction history computed from the stripped store, diffed against an independent Electrum server reading complete blocks. 32 of 32 completed comparisons identical. Zero invented transactions. — WHAT'S NOT BUILT Monetary IBD is design only and has never been adversarially reviewed. The daemon isn't built. There's no alpha. A stripped block can't be served to a legacy node. If monetary nodes ever became a large share of the network, who serves the chain is an open question I don't have a good answer to. Three published figures from this project have been wrong and retracted. Probably more to come. — WHAT I NEED Rerun the measurements on your own node and tell me where we disagree. Attack the IBD design. Every earlier version of this failed on second inspection, and this one hasn't been inspected. Argue about the classification boundaries. Where should the line sit for OP_RETURN? For dust? Runes mostly fall under 83 bytes and currently pass — is that right? Tools are standard-library Python, no dependencies. Every raw log is in the repo. If a number in a write-up disagrees with a log, the log is right. github.com/sambitcoin/Bitcoi…
8
11
51
1,920
MyTwatterHandle 🟩 retweeted
I love how so many people requested $SIVE that Saxo Japan went out of their way to list it! Just goes to show how much demand there is for this laser company. Special shoutout to Saxo. And of course, excited for Sivers earnings + planned Nasdaq listing coming up.
📢 お客様のご要望にお応えして、新たな海外銘柄の取扱いを開始しました! ✅ Sivers Semiconductors AB(SIVE) ✅ Lynas Rare Earths Ltd.(LYC) ✅ Ivanhoe Mines Ltd.(IVN) サクソバンク証券は、今後もお客様の声に寄り添いながらより良いサービスの提供に努めてまいります。
67
53
1,100
378,329
MyTwatterHandle 🟩 retweeted
Wake up babe, new Podcast project just dropped. Time to get some up-to-date data on 1 minute block sentiment. Just under 3 months to lock-in. My idea is that consensus.cash will help bring some clarity to the current muddy status & discussion.
Hello Bitcoiners, Forming consensus in a growing network is no trivial matter. 1 min blocks - yay or nay? So we're here to help! Have your say today, or just check the vibe: consensus.cash Shoutout @zndtoshi for the original inspo. Maybe now you can learn from us?
2
7
40
2,327
MyTwatterHandle 🟩 retweeted
Truth doesn't rust. Note how EVERYONE is capitulating their narratives to the vindicated BCH. - BTC: Ok BCH built better tech. - BIP110: Ok you were right about the Hijacking & node hoax. - BSV: Ok we cratered our project, CSW was a liar & scammer, wish we hadn't split.
10
14
58
1,495
MyTwatterHandle 🟩 retweeted
Replying to @C_Zar_69420
BCH has never once EVER had a good run of momentum on price in combination with a calm, focussed, united, and tech enabled BCH community. We're now ready for both. If that combo comes together, people are going to find the results literally unbelievable.
3
10
46
471
MyTwatterHandle 🟩 retweeted
Imagine if the bull run is starting & for the first time ever BCH outperforms on the way up. The narrative change would be seismic.
8
16
79
5,977
MyTwatterHandle 🟩 retweeted
20 million sats moved on-chain through BCHNostr. That's not a projection — that's already happened, through a social platform where tipping is built into the same interface where you post, browse a marketplace, list a job, or back a crowdfunding campaign. Here's what that looks like in practice. A business in Argentina — one of the 400+ merchants in that country already accepting $BCH — sets up a Business Page on BCHNostr. They control the wallet. No intermediary holds the funds, no platform takes a cut before the money arrives, no approval queue. A customer finds them through the platform, tips them directly for a post or pays for something listed in the marketplace. The BCH goes straight to the wallet the business controls. That's it. This matters more in contexts where payment intermediaries are the problem, not the solution. Argentina has spent years cycling through capital controls, frozen bank accounts, and a parallel exchange rate that makes official financial infrastructure actively hostile to small businesses. The workaround for many has been cash — physical, anonymous, untraceable — because the formal system extracts too much and delivers too little. BCH at sub-cent fees is a digital version of that workaround, except it works across borders and doesn't require physical presence. BCHNostr adds a layer to that: the discovery and community infrastructure that cash doesn't have. A business with a BCHNostr page is findable. Their posts are visible. Their tip wallet is attached to their identity on the platform. The social graph and the payment rail are the same thing, not two separate systems bolted together awkwardly. The mechanism is Nostr — a decentralized protocol where no single company controls the relay infrastructure or the identity layer. Accounts are cryptographic key pairs, not usernames stored in a database that can be deleted or shadowbanned. BCHNostr builds on top of that with BCH-native features: the tipping, the marketplace, the jobs section, the crowdfunding. Because BCH transactions cost a fraction of a cent and settle in seconds without waiting for block confirmation, the economics of tipping actually work. Sending someone the equivalent of $0.25 for a post they wrote doesn't get eaten by a $2 fee. The tip is worth sending. Compare this to how creator monetization works on most platforms. The platform takes 30% or more. Payments require a bank account, which requires documentation, which requires infrastructure that isn't uniformly available. International tips involve currency conversion and wire fees that make small amounts pointless. The creator sees a fraction of what the supporter intended to send, weeks later, after the platform decides to release it. On BCHNostr, the business in Argentina with 400 followers and a tip wallet sees the full amount, immediately, in BCH they control. No platform holds it. No approval required. The 20 million sats already moved through the platform aren't sitting in escrow or pending review — they're in wallets their recipients own. Back to that Argentine business. They listed a service on the BCHNostr marketplace. Someone in Germany found it, decided it was worth paying for, and sent BCH. The fee was a fraction of a cent. The transaction confirmed in under 10 minutes. No bank account required on either end. No currency conversion gatekeepers. No platform intermediary deciding whether to release the funds. That's the BCH economy built into the social layer. Not a concept — 20 million sats of documented reality. bchnostr.com
3
14
35
1,610
Bcash making moves. #bcash #bitcoincash #bch #bitcoin
🔥 Bitcoin Cash privacy + future-proofing taking strides The first linked 2-input post-quantum confidential spend just got verified on BCH chipnet. In plain English: You can now privately spend from two different coins at once in a single transaction. The amounts stay hidden. The link between the two inputs stays hidden. And the math that proves everything is legit is quantum-resistant - meaning even the powerful quantum computers of the future can’t break it. One shared secret (the “witness”) ties both halves of the on-chain check together so the network can verify it without learning anything private. This is real progress toward actual private, quantum-safe digital cash on Bitcoin Cash - not just theory. Massive respect to @0zkBrewer for shipping it. #BCH #BitcoinCash #Privacy #PostQuantum
1
3
20
548
MyTwatterHandle 🟩 retweeted
🧪✨ Big Cauldron DEX Update ✨🧪 The wizards over at @CauldronSwap have been brewing something special… You can now deposit BTC, ETH, BNB, DOGE, LINK, RUNE and a whole cauldron of other coins directly into the app thanks to the new Thorchain integration 💚 Cross-chain magic is live. Bring assets from other chains → swap into BCH tokens or provide liquidity on the World’s Fastest DEX, all from app.cauldron.quest This is a proper leap for BCH DeFi. No more “how do I get value onto BCH?” friction. Just pure alchemy. The cauldron is bubbling. The wizards are cooking. Bitcoin Cash just got a whole lot more connected. Go check the update and tell the wizards what you think 🔮🧙‍♂️✨ #BitcoinCash #BCH #Cauldron #DeFi
Deposit BTC, ETH, BNB, DOGE, LINK, RUNE, and lots of other coins to @CauldronSwap with our new update! @Thorchain + @CauldronSwap = 💚
2
15
42
927