mohrt

We were supposed to get a shipment of pi boards today, now they moved it back to Monday the third, but I am not around until the ninth. So if you order a device, it will ship on the ninth. thanks for your patience! 🐉

@vamosvigilante Thank you! That was bare packets per second over a link, one transaction at a time. I then released the BRC-142 Bundle format and hit 16 million TPS on the same server just by coalescing transactions together on the same frames. 😄

...multicast recently did 9M+ TPS. I was the only analyst to note this historical event. Congratulations Light!!!👏👏👏

@LightBSV @EquityDiamonds So you stance is HD keys are bad in general? They are disaster recovery, and may require a paid service to recover eventually.

@mohrt @EquityDiamonds Of course. I just think it's unreasonable for people to expect to recover their entire blockchain life from one seed phrase. That expectation comes from the current "Digital Gold" narrative, which arose from misunderstanding of the system. Hierarchical keys have needs: index info

Some people say seed-phrase wallets will be “replaced” because they don’t scale. That’s usually aimed at the wrong layer. A seed is a recovery root. Day to day, a wallet should maintain its UTXO set: which outpoints you can spend, at which keys. If you keep that set updated on receive and spend, you don’t need to re-walk an infinite HD address tree every time you open the app. The thing that scales poorly is rediscovery: “here is my seed / xpub — please scan the world and tell me which of my addresses have coins.” That needs an indexer (WhatsOnChain, Electrum-style servers, etc.). At low volume it’s fine. At extreme throughput, universal free full-history address indexing becomes an economics problem — fewer operators, paid APIs, pruned history — not a cryptography problem. Client “scan weight” is not the chain. Looking up ~40 gap-limit addresses against an index stays cheap even at 1M+ tx/sec. What gets heavy is building and serving that global index. Your personal UTXO set stays small; it scales with your coins, not global TPS. Receives are the catch for any air-gapped signer: outs you sign update spends and change perfectly; inbound payments never cross the air gap unless you import them (ideally with SPV proofs). Offline balance on a cold device = balance of coins it knows, not magic full HD awareness unless receives are synced too. On-chain “UTXO DB” checkpoints can work as rare encrypted backups on BSV fees. They’re a disaster replica, not the hot database. You still need a way to find the latest blob and re-check that outpoints are unspent. So: is PiWalletSV going to have the same problem ElectrumSV / ElectrumSVP is going to have soon? Same dependency class today for discovery: the companion rebuilds UTXOs from the account xpub via WhatsOnChain gap scans (cached in the browser). That is the Electrum-shaped weak link — indexer availability, rate limits, privacy of address queries — not the seed itself, and not the air-gap signing model. Where PiWalletSV differs: keys never live on the online half; the Pi verifies BEEF/BUMP before signing and doesn’t trust the companion’s balance claim. The long-term fix for the shared indexer problem is the same for any serious wallet: treat local (or explicitly synced) UTXO state as source of truth, seed as disaster recovery, indexers as bootstrap/rescan helpers — optionally receive-proof sync to the Pi for offline known-balance. Not “abandon seeds.” Seeds aren’t dying. Blind reliance on free global rescan is.

@LightBSV @EquityDiamonds The wallet can persist state, but if that needs reassembly from seed phrase, the state also need rebuilt. The other option would be a wallet service that manages state. Maybe there is a way to manage on-chain, but there are always trade-offs.

@mohrt @EquityDiamonds There just needs to be a good standard way to save outputs and proof information locally, and in the cloud; like files. I think this already exists, just needs to be used.

@kittytreats Trackpad for me. I use an external one.

My Microsoft mouse died months ago. Now it works again after my Apple’s mouse is acting up

Seed phrases don’t die from scale. A seed is purely a recovery root. Day-to-day the wallet just maintains its own UTXO set (which stays small and only scales with your coins). The hard part at high TPS is rediscovering those UTXOs from seed alone via global address indexes. Pruned nodes that keep only the current UTXO set help operations, not pure seed recovery. That’s why good design treats local UTXO state as source of truth and the seed only as disaster recovery. Indexers become bootstrap helpers, not the permanent dependency.

A bit beefy on the technical stuff; I’m not really sure what you’re saying here. If a complement Node keeps only the UTXO set and prunes everything else, then would seed phrase recoveries ever really die from scale? Are you considering seed phrases only from the wallet operations view? Because seed phrases should only be analyzed from a wallet recovery view.

@SmilaZParadis @CsTominaga @pete_rizzo_ @deggen Jack is the bitchat, adam is the tabs solution he proposed years back. youtube.com/watch?v=aUgL-4…

@mohrt @CsTominaga @pete_rizzo_ @deggen Jack's what Adam's?

YOU CAN NOW SEND #BITCOIN OFFLINE WITHOUT INTERNET VIA BILLIONAIRE JACK DORSEY'S BITCHAT THE APP IS SO POWERFUL GOVERNMENTS AROUND THE WORLD ARE TRYING TO BAN IT GITHUB WANTS TO DELETE THE CODE GLOBAL FREEDOM TECH IS SPREADING 🔥

@SmilaZParadis @CsTominaga @pete_rizzo_ @deggen Except the offline BSV payments are actually chain transactions that eventually sync. Jacks system is akin to Adam’s tabs.

@CsTominaga @pete_rizzo_ Didn't @deggen recently do this on #BitCoinSV via Bluetooth? 🤔 ... you copy cats😲 and just pretending!

@pete_rizzo_ Go SQL

@SteveBu85134492 PiWalletSV.com

@mohrt Hey Mohrt, where could we purchase the Piwallet ?

I used ElectrumSV almost exclusively to manage my cold wallets, namely Ledger Nano S and KeepKey. Neither of these natively supported BSV, but with ElectrumSV it worked. Then ElectumSV was sunset. Eventually it had issues when its indexers disappeared. Sometime after that cryptorebel took it over and revived it into ElectrumSPV. Fantastic, but ah, no hardware wallet support anymore. That is how piwalletsv.com came to be, a need for a real air-gapped cold wallet with BSV as its focus, on open source hardware and software. No proprietary code. No BSV hostility. This was a real need, at least for me. I finally have a cold storage wallet I'm comfortable with. If you can't find it, build it! 😎 This was a pretty big undertaking, I had to build a point-of-sale system from the ground up to support credit cards and BSV payments, almost as big of a job as the wallet!

BTC owners will accept any technical solution so long as it supports their bags.

@ShockedWorlds They are not your seed words. Only the owner can use them. That’s how seed words work.

@mohrt Why no seed words work?! 😕

Let’s see those wallets early adopters!🔥🔥🔥

@Belgriek QR over multiple frames is a standard QR protocol feature.

@mohrt I don't have such a wallet but I just watched the videos (I didn't have time to explore the website/app) and yes, it is an interesting project. I am not familiar with the 28 frames QR so it is another thing to figure out.

On a serious note, the whole BIP110 thing is dumb. Just come to BSV.

👀👀👀

@saylor So is it set in stone, or not set in stone? You can’t do both. Protocol changes shouldn’t happen.

Bitcoin’s core design is set in stone. Protocol changes should be rare, conservative, and driven by necessity, not ambition. Don’t fix what isn’t broken.

@coinyeezy That isn’t Craig at all. He says in the first sentence it’s set in stone, and then in the second sentence goes right on talking about protocol changes.

saylor is creg posting

@Sofia50020Sofia There were no wireless remotes

Something is wrong in this 1960s living room. Can you spot it?