Bitcoin payments to robot cars, by radio, from a lake with no internet. What you're watching: • A handset with its own Bitcoin wallet. The key was made on the device and has never left it. It signs a payment and sends it by LoRa radio. • A relay up a tree hears it, puts it on the network, and passes it on to the cars. • Each car checks the payment on its own five-dollar chip, every signature, in about a tenth of a second. Then it moves. No server tells it the payment is good. • Car 5 has one rule built in: never turn right. When I paid for a right turn, it checked the payment, found it valid, and refused anyway. The payment is still on chain. Trying to make a machine break its rule costs money every time, and leaves a record. Why it matters: machines that sell their work in tiny amounts. A turn, a reading, a minute of power, paid as it happens. That only works if a payment costs less than what it buys. Each command here cost 130 satoshis on BSV, fee included, a fraction of a hundredth of a cent, and the cars act the moment the payment checks out, with no ten-minute wait. On BTC today the same command would cost tens of cents, and an unconfirmed payment can be replaced, so a machine would have to wait for a block before trusting it. Same idea, different economics. For machines, the economics decide. Honest notes: this was the first field test. The refused payment only reached the network later, because the handset stopped repeating it too early; car 4 should have turned right but never received it, for the same reason. That gets fixed before the next run. Car 4 also got stuck on a bump in the table. Every order in the film is on chain. Forward: whatsonchain.com/tx/81a63c3f… Turn left: whatsonchain.com/tx/a5c23932… Turn right, the one car 5 refused: whatsonchain.com/tx/de702026… #BSV

New Gateway Wallet UI is live on BsvBsv.com 💰 📱 Set the wallet as your front page on mobile 🧊 Hot ⇄ Cold transfers now under More Gateway Wallet will never be discontinued like Centbee or RockWallet. Your keys live on your device, not a central server.

RockWallet legacy retires 30 Sept. Keep your BSV: send to a new Kallubi address, or restore with HD path m/0'/0/0. Seed stays on your machine.

ビットプラン（BitPlan Gateway）がBSV決済によるマルチモデルAI推論サービスを開始。 HTTP 402を通じ、AIエージェントが必要な推論処理をその場で購入できる仕組みを提供。 複数のAIモデルに対し、共通の支払い及び同アクセスが可能に。 gateway.bitplan.dev

FCA & Bank of England: "We cannot accept solutions where customers have no recourse when assets are lost or stolen." That statement alone rules out every "code is law" blockchain. BSV's NAR was built exactly for this. The regulators drew the line. Only BSV was ready for it.

Can Bitcoin SV save the Bank of Japan from its own bottleneck? 📈 The Bank of Japan just put a number on national-scale digital cash: 500,000 transactions per second. Bitcoin SV was built to carry that load without splitting one account into hundreds of software rows. That figure is the working assumption in the June 2026 CBDC pilot progress report, posted again on 11 September by the Bank’s official English account. The split matters: → 100,000 TPS of updates → 400,000 TPS of balance inquiries Most of the load is not a payment. It is asking one account: what do I hold? On a single account the pilot hit a wall. They split one balance into 600 records to reach about 18,500 TPS. No fatal knockout factor, they wrote — and still a large bill for servers and network. ⚠️ Would a G7 central bank ever say the account model itself is the error — or will it keep splitting rows forever? That is the problem. One account. One lock. One queue. You cannot run a country on a row that has to be carved into hundreds of pieces. Coins as separate outputs move in parallel. Settlement sits on the base layer. Fees stay near zero at volume. You do not patch the customer after the pilot. The Bank has not issued a digital yen. The report does not name a public chain. It names a throughput and contention problem every account-based CBDC meets at social scale. The rescue is not a press conference in Tokyo. It is a protocol that already treats scale as the default. While the tape argues the Fed print, a G7 central bank is designing for half a million TPS. The architecture that can carry that load without breaking the account model is already running. Yes or no: should a national digital currency settle on a public UTXO base layer instead of an account database? 👀 The storm is coming. 💥 Sources: Bank of Japan – Central Bank Digital Currency Experiments: Progress Report on the Pilot Program (June 2026) Bank of Japan English account – 11 September 2026 BoJ report §2.1.2 – 500,000 TPS design assumption; single-account split test #RealBitcoin #BitcoinSV #SatoshiVision #FunctionalUtility #Crypto #CBDC #Blockchain