Guest contribution:
Hot topic · builder-side · non-market · drawn from X and related sources

Restore is not permission, and scale is not one dial

The practical edge since the last check is wallet recovery behaviour and how capacity is allocated — not another giant test-block headline.

BSV Wallet has merged a safeguard so unfinished PeerPay payments restored from an old backup are not sent automatically. Restored payments are held for review; a separate Send action is required before delivery resumes. The code also checks recipient and amount against the signed payment record, so altered instructions are harder to approve by accident. The point is simple: restoring old data should not silently restore permission to execute earlier payment instructions. The fix is in source; shipping in a downloadable mobile build is not yet confirmed.

Teranode’s public line this week stays on independent scaling: more Validator instances when validation is the bottleneck, scale block assembly as its own service when that is the bottleneck — microservices so capacity tracks need rather than a single monolithic knob.

Around indexing and migration, the cost argument continues. Project Babbage is reiterating that free-forever ElectrumX-style scanning is not free to run, that migration guidance toward BSV Desktop (local data by default) is published, and that users keeping their own Merkle proofs is the scalable path. A joint multi-contributor effort under the TPNIL label is described as underway across wallets and ecosystem participants. Security framing remains a spectrum: conservative vault-style models exist; everyday vs cold use is the user’s risk call.

The current pulse is correctness under restore and honesty about infrastructure cost — payments that wait for a human after backup, and services scaled only where the load actually is.

Source Links

Need more validation capacity? Spin up more Validator instances.

Faster block assembly? Scale that service independently.

Microservices = scale what you need, when you need it. Zero wasted resources. #Teranode #BSV

— Teranode (@BSVTeranode) November 9, 2026

Not even sure what the issue here is.

I expressed an engineering judgment, backed up by many experts, that this would not keep working for free forever, and that people should use systems where they keep their own Merkle proofs. What is the cost of running ElectrumX? People who…

— Babbage | BRC100 (@ProjectBabbage) November 8, 2026

“Cope with that” is also uncalled for.

But migration guidance is published, and BSV Desktop makes it easy for people to move their coins out of Electrum.

Cost is cost. An engineering judgment doesn’t care about your feelings or who retreats.

So, let’s just suppose, for the…

— Babbage | BRC100 (@ProjectBabbage) November 8, 2026

People are free to store what they want.

Projects like BSV Vault Manager have a more conservative security model. Security and convenience exist on a spectrum.

A properly managed, modern BSV Desktop wallet, kept out of everyday use, should be able to handle larger amounts, but…

— Babbage | BRC100 (@ProjectBabbage) November 9, 2026

Copy a million files to your own storage server with https://t.co/WEcWqfkpY4 and put the evidence on chain. Make those transactions useful. Catalog your data. Point your favorite AI at the repo and get to work!

— Light (@LightBSV) November 6, 2026

BSV Wallet Merges Review Step for Payments Restored From Backup
https://x.com/thebsvtimes/status/2119618076618744228

Teranode v0.16.1 Beta 7 Fixes Connection Failures and Improves Chain Recovery
https://x.com/thebsvtimes/status/2118882612622266403