Lightstone retweeted
TokenSquare has introduced KRWQ, a Korean won-backed stablecoin built on the BSV blockchain in collaboration with the Switzerland-based @BSVAssociation aiming to enable real-time payments, micropayments, & enterprise settlements in South Korea.
$BSV
Lightstone retweeted
I want to address some of the common responses to this I've seen.
The biggest misconception about Bitcoin: “It isn’t real until it’s confirmed.”
Yesterday someone sent a transaction over a handheld radio with no internet and no phone signal. The pushback came straight away: “It doesn’t count until it settles on the blockchain.”
That objection gets something basic wrong about how commerce works, and about how Bitcoin was designed.
Accepting a payment and settling it were never the same thing.
When a shop takes a cheque, the money hasn’t moved yet. Card payments settle days later and can be reversed months later. Merchants accept them anyway, because commerce has never run on certainty. It runs on managed risk. The whitepaper says so in its first paragraph: under the existing system, “a certain percentage of fraud is accepted as unavoidable.”
Satoshi answered this in 2010.
In the “Bitcoin snack machine (fast transaction problem)” thread, he described accepting payments in seconds with “good-enough” checking. When someone pushed back, he wrote: “I didn’t say impermeable, I said good-enough,” and said the loss in practice would be “far lower than with credit cards.” He wasn’t selling a technical utopia. He was describing how real businesses work.
What the merchant actually knows offline
With Bitcoin (BSV), the customer presents the transaction along with Merkle proofs for its inputs. The merchant checks those against block headers stored on their own device. No internet is needed. In seconds they know the coins exist, they’re in the chain, and the signatures are valid.
The only remaining risk is a double-spend. Think about what that means in a physical shop. The customer is standing at your counter, on your cameras, buying something in person. Double-spending you there isn’t a clever attack on the protocol. It’s fraud, it’s a crime, and you know who did it. That’s exactly the same protection that kept cheques working for a century.
Confirmations are a dial the merchant sets, not a rule the network imposes.
Section 11 of the whitepaper works out double-spend probability as a function of how many blocks you wait. That only makes sense if the recipient chooses how long to wait. So:
- A coffee or a bus fare: accept it instantly.
- A laptop: maybe wait for the network to see it.
- A car: wait for confirmations before you hand over the keys.
Same protocol, different decisions, because the economics are different.
Where the misconception came from
Many people believe “Bitcoin needs confirmations” because BTC changed its relay policy so that unconfirmed transactions can be replaced (Replace-By-Fee). Once replacement became the norm, zero-confirmation payments stopped being trustworthy there, and a generation of users learned that waiting for blocks was the only safe option. That was a policy choice, not part of Bitcoin’s design. BSV kept the original first-seen rule, so the payment that reaches the network first is the one that counts.
The bottom line
Bitcoin was built for the real world, where there are laws, identities, cameras, reputations and courts. It was never meant to replace all of that with block confirmations. It was meant to make payments cheap, instant and final enough for the risk involved.
Offline payments on BSV aren’t a workaround. They’re the system working as Satoshi described it.
Lightstone retweeted
Wow, wow, wow. I just left the National Press Club where Minister of Communications @AnikaWells spoke. She repeatedly and brazenly lied about the fake accounts, claiming they were only for enforcement, even though the legislation says in black and white that the eSafety Commissioner can use them in unlimited ways for "educational" and "promotional" purposes.
One big moment came when a Politico reporter got up and said something about how mean people like @PaulineHansonOz were to eSafety Commissioner Julie Inman-Grant. Seriously. A supposed reporter was white-knighting for a government official during the official Q&A. The same reporter had come up to me before Wells' speech and asked if I had criticized Inman-Grant. Who needs government censors when you have Politico?
After he asked his question, Wells showed the most emotion, describing online criticism of Inman-Grant as "abuse." She also talked about her own staff's supposed suffering. I kid you not. The mask dropped, and you could see what really upset her: people — including a sitting Senator — criticizing government officials.
After gaslighting the audience about fake accounts, Wells repeatedly insisted the government wasn't trying to censor content. She said this after filling her speech with examples of content she claimed harmed people. You couldn't make it up.
This legislation is the culmination of decades of progressives equating words with physical violence. Wells cynically compared her legislation to prevent psychological "harm" to various laws that protect people from physical harm, like seat belt laws.
BTW, Wells never said what content it was that she thought caused eating disorders. Pictures of skinny women? Dietary advice? Who knows. Nobody asked.
Another important moment came when Wells explicitly said Australia would be pursuing censorship alongside other nations, including the UK, France, and Spain—all countries where governments risk losing power to populists.
I spoke with Julie Inman-Grant before the speech began and asked about the fake accounts. She insisted they were there just for enforcement, and when I asked why the law allowed them to be used for government propaganda, she said she might write an "enforcement memo," which, of course, would have no impact on the legislation.
After her speech, I went up to Wells and asked if she was seriously saying the legislation didn't allow the government to use fake accounts for government propaganda. She refused to answer. A man who said he was from the National Press Club stepped in front of me and said I could interview her afterward. But that wasn't possible because they rushed her out the back to avoid any difficult questions.
So there you have it. The pettiest people in Australia are seeking to silence citizens and their political opponents in the name of protecting children. These deeply intolerant and cynical people want to control what you can see and say online. And they're doing it with most of the media's support. Australia has reached a new low in its rapid descent into dogmatism, intolerance, and censorship.
The government today will introduce sweeping censorship that @AlboMP & @AnikaWells lie about. Below she claims the government wants to create a bot army of fake accounts for “research” when the bill clearly intends for them to be used in partisan warfare against fooled citizens.
Lightstone retweeted
Join me, Neil Oliver, Gary Kealy, Sir Toshi, The F-in Farmer, & Kurt Wukert Jnr as we discuss BSV in more detail than before and why it may be the most important money conversation since 2009.
youtube.com/watch?v=ia-KqzBZ…
If BSV is the original Bitcoin, then it should own the name too.
Rap has always been a voice for protest.
YOU STOLE MY NAME — EDDIE MONROE
“You stole my name. I want it back.”
A protest song for BSV / Bitcoin SV.
#BSV #BitcoinSV #Bitcoin #EddieMonroe #Rap
I just sent IPv6 network packets between BSV overlays, using BEEF transactions, recording proof of delivery on a Teranode test chain, and fully valid end to end. This is running over a multicast lab. Everything is SPV verified to the packet level. BSV scales. The future is now.
Lightstone retweeted
Dr. CSW is preparing a test of 10 billion TPS all by himself, using 10 servers around the globe with the assistance of some AI agents (I assume Chinese ones, since he prefers them); this is truly a Satoshi Nakamoto-style proof of work.
Lightstone retweeted
You will wake up at three digits. 📈
There is a rule in markets that most people learn too late.
The price moves first. The news comes second.
This is not a theory. It is the documented, repeatable pattern of how information flows through financial markets — and it applies to Bitcoin SV with particular force right now.
Here is how it works.
Decisions about real-world adoption — enterprise integrations, government-level data infrastructure, large-scale tokenization projects, payment network deployments — are not made in public. They are made in boardrooms, in legal departments, in procurement offices. The people in those rooms know what is coming. They also know that the asset they are about to use or endorse is currently trading at a fraction of what it will trade at once the announcement is made.
So they buy first.
Not all of them. Not always. But enough of them, often enough, that the price begins to move before the public has any idea why. Volume picks up quietly. The chart starts to shift. And then, weeks or months later, the announcement comes — and the crowd rushes in to buy an asset that has already moved 10x, 20x, or more.
The crowd pays the premium. The early holders collect it.
This is not speculation about Bitcoin SV specifically. This is the structure of how information asymmetry works in any market where the underlying asset has real-world utility that is not yet priced in. Bitcoin SV is the original protocol — the one that scales, the one that processes data transactions at enterprise volume, the one that supports micropayments and tokenized applications at a cost that makes them economically viable at scale. The utility is real. The adoption decisions are being made. The public does not know the details yet.
That is the setup.
Consider what the current price implies. Bitcoin SV is trading at a level that reflects a market that has largely forgotten it exists. Global daily volume across all exchanges is measured in single-digit millions of dollars. The awareness gap is not a weakness — it is the opportunity. The smaller the crowd that currently holds the asset, the larger the move when the crowd arrives.
Now consider what happens when a single significant real-world deployment is announced publicly.
The crowd does not trickle in. It rushes. And when it rushes into an asset with thin liquidity and a small float of actively traded supply — because the long-term holders have already moved their coins to cold storage — the price does not move gradually. It moves in steps. Large steps. Fast steps.
You will wake up one morning and Bitcoin SV 🔥 💥 will be trading at several hundred dollars. Not because something changed overnight. Because something was decided weeks or months earlier, by people who understood what they were deciding, and who positioned themselves accordingly.
The question you need to answer is not whether this will happen. The question is whether you will be positioned before it does, or whether you will be reading about it afterward.
There is no middle option. There is no "I will wait for confirmation and still get in early." Confirmation is the announcement. The announcement is after the move. Waiting for confirmation means paying the post-move price.
The window is open now. It will not be open at several hundred dollars per coin.
There is no third door. Confirmation is the headline. The headline is after the move.Will you own Real Bitcoin (SV) in the quiet — or buy the explanation at three digits? 🔥
The storm is coming. 💥
#RealBitcoin #BitcoinSV #SatoshiVision #FunctionalUtility #ValueInvesting #CryptoSources:
livecoinwatch. com/price/BitcoinSV-BSV
CryptoClub FormRap26-09-20_0800
CryptoClub FormRap26-09-29_0800
Lightstone retweeted
I’m continuing my 10 million-plus testing and working towards expanding to ten nodes. No, I shall not be publishing the IP addresses. A global test does not require the entire internet to appoint itself an unpaid research assistant.
This is my own testing environment, not mainnet. I’m running on a non-standard port, and multicast is configured. These are experimental arrangements, not invitations to invent a conspiracy because a port number has offended somebody’s expectations.
The practical difficulty is that I am one person. Router management, updates, maintenance, PFV3, logging, checks, network administration: none of it becomes optional merely because I would prefer to concentrate on the experiment.
So I have a variety of AI agents handling different responsibilities. Without that assistance, conducting a global test on this scale would not have been possible for me in the past. The work requires a team.
I have therefore acquired one. Unfortunately, it is rather like employing a collection of excessively trained uneducated three-year-olds.
Imagine giving a toddler Cisco CCIE-level knowledge of routers, no dependable understanding of why this particular network needs to behave as it does, and permission to touch things.
Now imagine several toddlers.
They possess the technical vocabulary of a senior engineer and the touching conviction that anything which can be changed ought to be improved immediately. They can explain how to move the staircase. Whether you happen to be standing on it belongs to another department.
This is not an argument against using them. Quite the opposite. Their assistance makes the work possible. They can save enormous amounts of time—provided one does not allow their enthusiasm to create an entirely new category of work.
The distinction is between knowing how to execute a command and understanding why that command belongs in this experiment, under these conditions, at this moment. A beautifully executed alteration can still ruin what you were trying to measure.
That is where I come in: deciding the purpose, setting the boundaries, checking the results, and ensuring that “helpful” has not quietly become “unauthorised.”
This is the world we are now in. One person can undertake work that once demanded a substantial team, assisted by machines of extraordinary utility and occasionally breathtaking innocence.
The nursery has acquired administrative privileges.
It has not acquired adulthood.
Lightstone retweeted
I want to provide an update for the BSV community regarding the current US regulatory landscape and how it applies to BSV.
The CLARITY Act failed to get a vote in the Senate. This happened in spite of a bill that had passed the House in a bipartisan manner, and after more than a year of debate in the Senate. However - this doesn't mean the conversation is over. It means the rulebook is now being written by the CFTC and the SEC, and both agencies have already made it clear they intend to move forward with or without Congress, and are expected to draw heavily on the CLARITY Act as a framework for their rulemaking.
I want to share where BSV stands in all of this, because we've been in the room with both.
At the CFTC, we covered the full picture, financial use cases included. But what they latched onto was the data utility side: blockchain as infrastructure for data at scale. And they were genuinely excited, because this was new messaging for them. Ninety-nine percent of the industry lobbying them isn't talking about that. That positioning is a winning one, and it's helping regulators and legislators understand there's far more to this technology than what they've been told.
Why is this message so new to them? Because the industry has spent over a decade pushing bad narratives, and nearly all of them trace back to one assumption: that these systems don't scale. Every workaround, every "digital gold" story, every excuse for why blockchain can't do real work comes from that mistake.
We walked in with a different message: Bitcoin always scaled. It was designed to from day one in 2009. BSV is just proving it to the world.
At the SEC, we addressed one of the biggest misconceptions in the CLARITY Act: the idea that a blockchain's maturity can be measured by how decentralized its governance is. Decentralization was treated as a coefficient for maturity.
That gets it backwards. There's a fundamental confusion here between decentralized governance and distributed systems. Bitcoin was never meant to be governed by committee. It's a distributed network with defined rules.
What actually matters is a locked protocol. When the protocol is set in stone, anyone can build on top of it without worrying that the rules will change underneath them. That's what enables unbounded innovation. That's why the Association maintains the Network Access Rules and protects the original protocol. The result is maximum "decentralization" where it actually counts: in innovation and application building, not in protocol politics.
We also reinforced something I've said many times: BSV is the restoration of the original Bitcoin protocol. We are rooted in Bitcoin's history.
That matters more than ever. In March, the SEC and CFTC issued joint guidance recognizing BTC and BCH as digital commodities. Our meeting was an education, and they were highly receptive to it. They left understanding why BSV shares the very same fundamental principles the agencies are looking for in a digital commodity, because BSV is that protocol, restored.
The rules are being written right now. We intend to make sure they're written with the original Bitcoin in mind: the scalable one, the regulation-friendly one.
Lightstone retweeted
On 2026-09-18 I asked whether we could put a zero knowledge shielded pool on Bitcoin.
First line of code 2026-09-20. On 2026-09-21 a real proof of a real pool spend verified inside Bitcoin Script, on a real Bitcoin SV node, in 3.08 seconds.
What it is: private transactions that settle on Bitcoin. You deposit, you send, you withdraw. The amounts and the parties are hidden.
No bridge. No sidechain. No custodian. Nobody to ask permission from. It is an ordinary transaction, and the miners enforce it, because the proof is checked by the script itself.
The part that holds the money is built on hashing rather than on elliptic curves. That was deliberate, and it is where this goes next.
It will be free and open, including the verifier, which is ours and is not specific to this pool. A private pool nobody can audit is worthless. The only version worth shipping is the one you can read.
Still building. No date. You will see it when it runs.




























