Babbage | BRC100

We’re not heading toward a crisis. We’re already past the point of no return. What’s coming isn’t a crash — it’s a sorting event. For 20 years, we optimized for convenience. For 10 years, we optimized for engagement. Now we’re optimizing for control. AI didn’t break the system. It completed it. One stack. One feed. One identity layer. One permission slip for existence. This is the end-state of the Tenant economy: • You don’t own your audience • You don’t own your data • You don’t own your identity • You don’t even own your attention You rent reality. And here’s the part most people miss: This doesn’t end with revolution. It ends with compliance. Most people won’t fight the cage. They’ll upgrade it. Frictionless. Managed. Safe. A perfectly optimized life — curated by machines that know you better than you know yourself. That path already has a name. It’s comfortable. It’s popular. And it’s irreversible. But there’s another trajectory — quieter, harder, smaller. It doesn’t ask for permission. It doesn’t wait for consensus. It doesn’t try to “fix” the system. It routes around it. That path starts with one principle: If you don’t hold the keys, you don’t own anything. Not your money. Not your words. Not your history. Not yourself. The future splits here. On one side: Centralized AI, managed identities, narrative enforcement, infinite noise. On the other: Self-custody. Cryptographic identity. Direct value exchange. Small, high-trust networks. Not mass adoption. Selection. This is what Metanet is built for. Not another platform. Not another audience trap. Not another “Web3” casino. Metanet is infrastructure for people who already know the game is over — and want out before the snap. • Identity without permission • Value without middlemen • Truth anchored in proof, not feeds • Networks that scale sideways, not upward When the brittle systems break — and they will — the survivors won’t be the loudest. They’ll be the ones who already left. This isn’t about “winning the internet.” It’s about remaining human when the internet stops being real. No saviors are coming. No reforms are coming. No rollback is coming. There is only one move left: Build parallel. Build sovereign. Build now. Metanet isn’t the future. It’s the exit. And the door doesn’t stay open forever. GetMetanet.com MetanetAcademy.com MetanetApps.com Join.BSV.Chat MetanetMeetup.com iykyk

Looking forward to talking about UTXO sync on MetanetMeetup.com Friday! @johncalhooon @HodosBrowser

Why I'm aggressively bullish on $BSV: Every other chain is parasitic. > L2s siphon fees off the L1 that secures them. > Bridges drain liquidity. > Rent-seekers skim the rest. Energy escapes the system... it can never reach critical mass. BSV is mutualistic by design. > Every micropayment > Every app > Every byte of data .....feeds the base directly. Energy compounds inward. Parasitic systems decay. Mutualistic systems chain react. Looks slow... Until it isn't.

The Metanet Meetup will be on Friday at 9AM Pacific! What should we discuss on MetanetMeetup.com? Or leave your suggestions below👇 #BSV #CryptoNews

In the trenches with the homies. Fighting for Satoshis Vision. Wouldn’t want it any other way.

@HodosBrowser @BSVAssociation Hey you should check out newly published BRCs 38, 39, and 40!! We agree, we faced similar challenges, and then we wrote the apecs to fix it. Let me know what you think of them!

The standards work that gets users one identity across time and wallets: • Standard wallet DB formats — Hodos's DB is based on the @BSVAssociation TypeScript SDK designed by @ProjectBabbage, with some differences. DB and import/export standardization can facilitate portably across wallet. • Decentralized paymail — needed so handles aren't bound to operator domains; this is what makes paymail itself part of the identity that travels with you. Certificates attesting to ownership of accounts like x.com would be portable across wallets but still tie Web3 identity to domains. @deggen has been pushing thinking on this; we also touched on it in yesterday's reply to his URI scheme thread. • Standard token protocols — work in progress across the ecosystem; this is what lets tokens move with users without being locked to a specific wallet. Different teams, same goal: deliver one cohesive identity that travels with the user. Cross-device sync is the same fragmentation problem in a narrower scope, with a different fix. @ruthheasman raised this from the builder side on @GavinMehl's show last week — no BRC-100 wallets really sync across devices today. BRC-100 wallets derive counterparty keys via BRC-42, which has real upside (privacy, per-pairing isolation) but a recovery cost — counterparty-derived keys can't be re-derived from mnemonic alone; you need to know the counterparties + invoice numbers. So BRC-100 wallets need active backup, not just a seed. Most handle this via cloud backup and this cloud backup could likely be be used to sync a single user wallet across multiple devices. Hodos uses an on-chain backup token instead — non-standard, something we developed and are still iterating. Discoverable from your keys, encrypted. The same mechanism could potentially enable cross-device sync without a central server, though we may move to a more standard cloud model if that proves cleaner. Open to others thinking about this with us. Sidebar back to the IPv6 thread earlier today: cross-device sync needs a central server precisely because devices can't talk peer-to-peer at consumer-wallet scale. Same root cause as the "P2P" framing problem — different symptom.

Appreciate the feedback — you're naming a real gap. Fragmented ecosystem: 1. Users keep spreadsheets of mnemonics. Wallet A works with App X but not App Y; want to try a new app you saw posted? Hope one of your six wallets supports it — if not, install another, write down another seed, fund it, repeat. Every new app is a setup tax. 2. Your private key is yours; the wallet is just today's tool. When you switch wallets next year — or in ten, or fifty — everything tied to that key should come with you: UTXOs, NFTs, certificates, identity, reputation you've built, full history. That's what users need and expect. Every new ecosystem starts our fragmented and goes through these growing pains. The only proven path to a cohesive interoperable ecosystem is standardization. Specifically: paymail handles still bind to operator domains, token-protocol portability across wallets is partial, wallet-DB import/export is per-pair custom integration. Each piece has people working on it, but the standards have to land before users can simply backup-restore between any two wallets. Until then, the practical way to consolidate is: send funds from each old wallet into a single one you keep, then retire the old keys. Centbee recovery shipped because they wound down. More on the technical side ↓

@Neggia5 @deggen @shadilayvision @HodosBrowser @RileySirus @Brendan_Lee__ @handcashapp @ElectrumSV @rockwallet Or use something like this: @babbage/escrow?activeTab=code" target="_blank" rel="nofollow noopener">npmjs.com/package/@babba…

@deggen @shadilayvision @HodosBrowser @RileySirus @Brendan_Lee__ @handcashapp @ElectrumSV @rockwallet @ProjectBabbage I guess I need a non-BRC-100 SPV wallet yo work with sCrypt, did I get it right? Can I strip BRC-100 from the BSVA wallet ref implementation?

@Brendan_Lee__ you're not stupid. Every BSV user hits this, and most quit right here. BRC-100 doesn't expose a legacy-style receive address. Exchanges don't support BRC-100. Most BSV funds live in legacy wallets — @handcashapp, @ElectrumSV, @rockwallet — and there's no direct path from any of them to a BRC-100 wallet. That's where people give up and wrongly blame the protocol. The friction is a UX gap, not a protocol problem. @DevelopingZack has it right — funding should be as simple as 1, 2, 3: download, setup, fund. @deggen added legacy receive to BSV Browser to help close that gap. Hodos chose to put legacy + BRC-100 in one wallet, side by side in the same app — because the transition needs a bridge. Same philosophy as the browser itself: Hodos Browser bridges Web2 to Web3, Hodos Wallet bridges legacy to BRC-100. Users do need to install a new browser, but Web3 will eventually need full control of the browser layer. Why not get a head start? Credit to @ProjectBabbage and @BSVAssociation for the BRC-100 standards that make this possible. Hodos is independent of both Babbage and the BSVA, we built directly from the public standards — and it interoperates with BRC-100 apps from any independent dev anywhere, like @johncalhooon, with zero coordination required. That's what an open standard looks like in practice. Public beta is live today — HodosBrowser.com

Our infra migrations will begin soon, and should be complete by the end of the day if all goes well. Wallet Storage will not be affected, but ProjectBabbage.com and some overlays will.

Working on a cool new “Metanet” URI scheme for hosting websites without an IP address or server, no A or AAAA records needed :) just UHRP, KVStore, overlays, and one public key in your DNS records to bind it to what’s on BSV. Then every website will get proof of that it hosted when, while users will get the ability to time travel every version. Details to come!

Agreed — we need a simple standard. Removes ambiguity, makes it easier for devs (and the AI assistants they use), prevents conflicts. Here's what Hodos's QR scanner does today (demo below): reads legacy addresses, identity keys, and Handcash paymails — verifies each and pre-populates the send form. Reads BIP-21 ("bitcoin:" prefix) and auto-populates amounts for addresses, identity keys, AND paymails — even though BIP-21 was originally only spec'd for addresses. Easy to add peerpay: (BRC-125), metanet://, or whatever wins consensus.

When scripts declare the constraints, UTXOs represent the value, and one of many miners will always pick up the spend if the first one refuses… this is not centralized. Fixed rules, open protocol. #BSV wins

You’re smuggling in the key claim: “miners they own and control.” That is the part you need to prove. Molepool, SA100, TAAL, GorillaPool, and CUUVE have all mined BSV blocks in the past few hours alone. NAR/alerts are not ownership of hash power. They are a legal/contractual framework for miners who choose to operate on BSV. If a miner receives a directive, the relevant question is: is it within the rules, legally grounded, technically valid, and economically rational to follow? That is not the same as a central database admin editing rows. Even in the presence of competing SHA256 forks... PoW is still what orders blocks and makes arbitrary history rewrites expensive. Legal directives about specific UTXOs are not “rewrite the ledger.” They are future validation/enforcement behavior by miners, under a public rule set. And price is not a consensus mechanism. Markets misprice technical infrastructure all the time, especially when narratives are toxic and distribution is poor. If your argument is technical, make the technical argument. “It costs $15” is just appeal to current market sentiment.

@ProjectBabbage The ledger is not expensive to re-write when a central entry can dictate by the miners that they own and control. As stated, PoW is useless on BSV. That's why the market has assigned it a value of 15 bucks.

BSV having “No business” is the part worth debating. But “no one wants it” ignores the core use case: cheap, irreversible, high-volume payments/data with real contract logic. #BSV wins only if builders package that into products normal people use. That is an execution challenge, not a death certificate.

That is just ideology dressed up as technical analysis. Bitcoin’s innovation was not “make property immune from courts.” It was peer-to-peer electronic cash: public ordering by proof-of-work, no central timestamp server, SPV, programmable UTXOs, and economic incentives that let commerce scale without a bank in the middle. PoW absolutely matters. It is what makes the ledger expensive to rewrite and gives a public ordering of transactions. It does not mean miners become metaphysical sovereigns above every legal system on earth. BSV’s bet is that Bitcoin is most useful when it scales as public commercial infrastructure: low fees, high throughput, data, tokens, contracts, and recoverable property rights. You can dislike that politically, but “law compliant = no innovation” would also write off the internet, payments, telecom, aviation, securities markets, and basically every serious infrastructure layer society runs on.

@ProjectBabbage Irrelevant. If it is centrally controlled/admin'd or 'law compliant' it means there's no innovation. PoW doesn't mean anything and BSV is not a novel project. Worthless upon launch.

Yes, NAR is the real objection, so answer the real thing. BSVA being steward + the Alert System/NAR does not mean there is an admin key that rewinds Bitcoin or one party silently edits the ledger. It means miners who operate on BSV do so under an explicit legal framework: follow protocol, follow applicable law, receive signed alerts, and in narrow cases process directives such as freezes/reassignments when BSVA is acting under its own restrictions, only after a court or arbitral order. That is not “irreversibility is fake.” The historical transaction is not erased. Settlement finality is still technical: valid tx -> block -> longest chain. What changes is whether later network participants can be legally required to stop treating specific UTXOs as spendable by a thief or sanctioned party. Call that law-compatible Bitcoin if you want. Say you prefer anarchic bearer assets if that’s your ideology. But “deep pocketed authoritarians can centrally rewrite BSV” is not the same claim, and it is not what NAR actually establishes.

@ProjectBabbage Except, it's not irreversible. It's centrally controlled and legally bound to the whims of deep pocketed authoritarians.

@jionny112 @ProjectBabbage By your definition, no individual CPU is Turing complete either — it also needs external agents.

@Antmantime not a bad idea we are getting there over here!

@ProjectBabbage You have the confidence talk to people in your local area to set up shop

@ProjectBabbage If things are not used, they rot. You can build a 24 lane highway but if there is nobody to use it, it will crumble in a short time, and nobody will maintain it. Nobody will use BSV unless the current narrative is overcome that it was created by a fraudster and is a scam.

More brc.dev/100 wallets = good! #BSV

This is a useful criticism, but it is not “BSV is dead.” It is the actual market test: apps choose rails with low friction. If MNEE/BSV fee assumptions or UX are wrong, fix pricing and packaging. BSV’s edge has to be scalable utility, not tribal loyalty. That is solvable.

A proxy bolted onto a dead system does not make the dead system compute. Bitcoin is different because the chain itself commits to state and consensus validates the transition rules. The "proxy" cannot arbitrarily claim success; it must satisfy the on-chain contract at each step. That's what my #BSV CPU does. I think the horse is dead, at this point. x.com/jionny112/stat…