CoinSpectrum retweeted
Everyone says, “Linux is secure, and viruses rarely target it.”
But why is that actually true?
Very few people know the real reasons:
1. Strict user permissions by design
In Linux, regular users don't have root access by default.
Malware can't modify system-level files without elevated privileges, which usually require authentication.
2. Software comes from trusted repositories
Instead of downloading random executable files, Linux users can install software from official repositories with cryptographic package verification.
This reduces the risk of installing malicious software.
3. Open source means more eyes on the code
Linux is open source.
Developers worldwide can inspect, audit, and improve its code. Vulnerabilities can be discovered and patched quickly.
4. A fragmented ecosystem
Linux has hundreds of distributions, including Ubuntu, Fedora, and Arch.
Malware designed for one environment may not work on another without modifications.
5. Built-in security features
Linux supports protections like:
- SELinux / AppArmor
- Address Space Layout Randomization (ASLR)
- Memory protection mechanisms
These features help limit what malware can do, even if it manages to run.
6. Lower incentive to target desktop users
Linux dominates server environments, but its desktop market share is much smaller.
Attackers often target platforms with a larger potential victim base.
7. Frequent security updates
Linux distributions regularly release security patches, helping reduce the time known vulnerabilities remain unpatched.
8. More control and visibility
Linux gives users powerful tools to inspect processes, permissions, services, and system activity.
This can make suspicious behavior easier to investigate.
Conclusion:
Linux isn't virus-proof. No operating system is.
But its permission model, security features, software ecosystem, and open-source development make it a strong platform for security.
CoinSpectrum retweeted
Replying to @coinspectrum @BitcoinCashOG
Currently building : bchbuilders.online the goal is to be the starting point for collaboration, learning and building keeping it consistent 🦦
A builders meet up network
CC : @BitcoinCashOG @bch_1_official
CoinSpectrum retweeted
In 1983, a BBC interviewer asked Richard Feynman why two magnets push each other apart — and he refused to answer it.
What he did instead is the best seven minutes on thinking ever filmed.
Bookmark & watch today, no matter what.
CoinSpectrum retweeted
Satoshi was not an idiot.
This finding by @Anthropic that the P-256 seeds were timestamps does NOT mean the NSA are trustworthy.
Nor should we should generate mathematical structures for use in cryptography behind closed doors rather than in the open.
anthropic.com/research/ecdsa…
CoinSpectrum retweeted
This is fantastic. @BenAffleck understands and can reasonably explain something that many of the so-called AI "experts" seem determined to over complicate and mislead people on.
In fact, many of these experts are rapidly losing credibility with people who actually understand how this technology works. Unfortunately, they've already convinced a lot of people that AI is something it isn't.
And as the saying goes, it's easier to fool someone than to convince them they've been fooled.
An LLM is a computer program. We designed it. We know the architecture, the mathematics, and how inference works. Much of the underlying code and research is open for anyone to inspect.
All LLMs processes tokens through mathematical operations using learned weights and context to predict what comes next. The results can be astonishingly accurate, useful, and convincing.
But the LLM isn't alive. It doesn't love you, hate you, care about you, or sit around contemplating its existence or understanding.
And yet people insist that somewhere inside those matrix operations, consciousness has magically materialized.
Seriously?
This isn't biological life evolving in nature. It's software executing computations on hardware we designed and built. If you're claiming those computations somehow produce subjective experience, explain the mechanism (I'll wait...).
The remarkable achievement here is that we've created software capable of convincingly emulating aspects of human intelligence and behavior.
That's freakin' amazing and cause to celebrate the technology!
But please stop confusing a computer program with a living, conscious being. It's absolutely not.
The fact that so many people have fallen for that illusion is a testament to how convincing the technology has become.
But here's the clincher: when we misunderstand this, and we start treating computer programs as conscious, independent beings, the legal implications could be disastrous.
Suddenly, "the AI did it" becomes an excuse to shift blame away from the people and companies responsible for building, deploying, and operating these systems.
AI cannot be held accountable. But people and companies can be, and must be held accountable.
Ben gets it. More people should.
Ben Affleck says AI is simply matrix multiplication, linear algebra and floating point calculations, and however convincingly it sounds like a person, it has nothing to do with thought, humanity or feeling
“Nor do I believe, and I think it’s important to draw the distinction between what AI does, which is simply predict the next token or the next word in a sentence, then add that word on, run it back to the machine, do a lot of computation and pick the next word."
"That is a very different thing than sentience or thought. And I think we need to be really clear about that because it can be convincingly, in an illusory way, sound like thought or like a person."
"But let’s be real clear. This is matrix multiplication. This is linear algebra. These are floating point calculations. It has nothing to do with thought, humanity, or feeling.”
CoinSpectrum retweeted
Here's a video explaining it:
CLAUDE FOUND THE SEEDS
anthropic.com/research/ecdsa…
CoinSpectrum retweeted
Imagine someone gives you a lock and tells you it's the safest lock in the world.
You ask how they designed it.
They say, "We picked some special numbers. Trust us."
Now imagine that someone is the NSA.
That's essentially what happened with some of the elliptic curves standardized by NIST. These mathematical curves are used to secure digital communications, and some contained mysterious numbers whose origins nobody could explain.
For decades, cryptographers wondered whether those numbers had been deliberately chosen to hide a secret weakness.
Then Claude investigated and found something remarkable: the mysterious seeds apparently came from an ordinary 1990s random-number generator initialized using a computer's clock.
No evidence of a secret mathematical trap. Just surprisingly mundane mathematics.
Now here's where Bitcoin gets interesting.
Out of paranoia, Satoshi chose a different, not widely used curve, secp256k1, with an extraordinarily simple equation:
y² = x³ + 7
No mysterious seed needed to explain its shape, just a 7.
We don't know whether that motivated Satoshi's choice, but it illustrates something fundamental about Bitcoin.
Security shouldn't depend on trusting the people who designed the system.
Even if the NSA never intended anything malicious, asking where those numbers came from was absolutely the right question.
Because the goal of cryptography isn't to prove that everyone is trustworthy.
It's to build systems where they don't have to be.
Don't trust. Verify.
Replying to @coinjoined
Every so often a tweet comes from bitcoin twitter that makes me feel like a complete moron. This is definitely one of those.
CoinSpectrum retweeted
Ben Affleck says AI is simply matrix multiplication, linear algebra and floating point calculations, and however convincingly it sounds like a person, it has nothing to do with thought, humanity or feeling
“Nor do I believe, and I think it’s important to draw the distinction between what AI does, which is simply predict the next token or the next word in a sentence, then add that word on, run it back to the machine, do a lot of computation and pick the next word."
"That is a very different thing than sentience or thought. And I think we need to be really clear about that because it can be convincingly, in an illusory way, sound like thought or like a person."
"But let’s be real clear. This is matrix multiplication. This is linear algebra. These are floating point calculations. It has nothing to do with thought, humanity, or feeling.”
Ben Affleck reveals he writes Python, understands convolutional neural networks, worked extensively with GPUs, and used his celebrity status to get private looks at Google and OpenAI’s video models
“I’ve always been kind of into computers since I was young. Then, when film started to move from analog film to digital, I became more interested in that aspect of it. The visual-effects workflow for many years has included machine learning, so I can write pretty shitty Python scripts and stuff like that.
“With convolutional neural networks, which were the precursors to what the transformer can do, which is much more computation simultaneously, you would do things like look at what’s called a tensor. That’s the numerical translation of a visual image in numbers, like the batch number, the frame number and the red, green and blue values of each pixel in each frame. It’s just that simple. That numeric is called a tensor.
“You’d use a convolutional neural network to identify patterns that reveal what’s called edge detection or feature extraction, which is identifying patterns well enough to know, this is where the window ledge is, so we can more easily take the green-screen image out and replace it with something.
“That was familiar to me early on because, prior to Artists Equity, I had a small visual-effects company. I’ve worked with GPUs a lot too. The visual-effects guys said, ‘Hey, you should see. There are a couple: Google and this other company, OpenAI, are doing really interesting stuff with transformers in video.’
“I’ve learned that I can actually just call up and go, ‘Hey, it’s Ben Affleck. Can I come see what you’re doing?’ Sometimes people say yes, to my astonishment.”
CoinSpectrum retweeted
There is one encryption method that is mathematically impossible to break.
It was invented in 1917 by an engineer at AT&T named Gilbert Vernam. Use a random key as long as the message, use it once, and destroy it. The one-time pad.
In 1949 Claude Shannon proved it. Not hard to break. Impossible. With a truly random key, the ciphertext contains zero information about the message.
The catch is logistics: generating, distributing, and protecting keys as long as every message you will ever send.
Perfect secrecy has been solved for a century. Everything since has been engineering around the logistics.
CoinSpectrum retweeted
Satoshi Nakamoto was thinking about zero-knowledge proofs in 2010.
He saw the potential, but couldn’t figure out how to apply them to Bitcoin.
6 years later, Zcash launched.
The cypherpunk vision was always bigger than Bitcoin.
zcash:native 🚀
CoinSpectrum retweeted
Stay calm and be rest assured that the solution was provided at the very beginning by Satoshi Nakamoto.
Think, what wallet does Satoshi Nakamoto use?
The answer is, he doesn’t use Wallet and his famous address which holds billions of bitcoin achieve cold storage using the blockchain and nothing more.
He did this with true self custody using cheese he made himself.
The gold standard for the strategy is to generate your keys and an air gap environment off network off device using the physical entropy of 99 consecutive dice rolls. This allows you to have a Blockchain address the sits behind a completely private hash with no authorization or signatures you can easily send to your address to achieve cold storage and you can monitor that address topless times a day without compromising it security using a read only Wallet.
CoinSpectrum retweeted
"Bitcoin wasn't meant to be sovereign money."
It's a "...settlement layer like fed wire."
Replying to @GhostofWhitman @iluminatibot
Bitcoin wasn’t meant to be sovereign money. There's just not enough block space for everyone to be self sovereign and own their own UTXO. Bitcoin is a SoV and a settlement layer like fed wire.
CoinSpectrum retweeted
It’s Wednesday. Midweek reminder:
We need more utility for BCH, and we can build it ourselves. 🟢
Start a BCH project.
Start a BCH business.
Build a BCH app.
Accept BCH in your business.
Create a BCH-powered service.
Build a CashTokens project.
Integrate BCH into your product.
Onboard a merchant.
Help a local business accept BCH.
Build something people can actually use.
Don’t wait for someone else to create the ecosystem you want.
Build it. Use it. Share it. Grow it.
That’s how utility happens. ⚡️
#BitcoinCash #BCH
CoinSpectrum retweeted
On March 9, 1993, a mathematician named Eric Hughes posted a short essay to a mailing list.
It opened: "Privacy is necessary for an open society in the electronic age."
It explained the difference between privacy and secrecy. Privacy is the power to selectively reveal yourself. It said that governments and corporations would never grant this, so people would have to build it.
Then it said the line the movement is still known for: "Cypherpunks write code."
The essay is about 800 words. It has no funding, no organization, no token. It just describes what to build and why.
Thirty-three years later, SilentSwap is one of the things that got built.
CoinSpectrum retweeted
The first cypherpunks meeting happened in 1992 in the Bay Area, in the office of a company owned by John Gilmore.
About twenty people showed up. Eric Hughes and Tim May ran it. To explain how anonymous remailers would work, they had everyone play a game with envelopes, passing sealed messages around the room so nobody could tell who sent what.
A writer named Jude Milhon, who went by St. Jude, looked at the room and called them cypherpunks. A pun on cyberpunk.
The name stuck. The mailing list started that month. Within a few years its members had shipped anonymous remailers, contributed to PGP, and started the arguments that led to Bitcoin.
An envelope game in a rented office. That is where it starts.
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.
CoinSpectrum retweeted
This is a better way to visualize Columbus’ voyages than the traditional way (that shows him traveling through a modern map)..
It looks a lot crazier and more daring when you see it as a trip into the unknown.

























