Hodos Browser

Hodos Browser public beta is live. Privacy-first browser on full Chromium. Native BitcoinSV wallet. Ad blocking, tracker blocking, fingerprint protection. Your keys run in a separate Rust process — never in JavaScript. Windows + macOS. Download: HodosBrowser.com

I've introduced HR 8470, the Surveillance Accountability Act, with @RepBoebert. It requires a probable cause warrant before the federal government can search your private data — even if that data is held by a third party. Warrantless searches are unconstitutional.

@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

For context — this is one year of solo building, from a proof-of-concept at a BSV hackathon to a shipping public beta. It's a beta, not 1.0. - Security audit is on the roadmap. Treat it like beta software: start small, keep your seed safe. Feedback welcome, bugs especially.

Hodos Browser public beta is live. Privacy-first browser on full Chromium. Native BitcoinSV wallet. Ad blocking, tracker blocking, fingerprint protection. Your keys run in a separate Rust process — never in JavaScript. Windows + macOS. Download: HodosBrowser.com

And now — we wait.

Hi. Professional C/C++ programmer here. The open-source code I can find written by Adam Back and Satoshi Nakamoto don't look remotely similar. Back's code looks typical of academic Unix programmers who also hack their code to run on Windows. Satoshi code was written by a professional Windows programmer who also wrote for Unix. Stylistically, they look nothing alike. There's not enough time between 2005 when I can find the newest Adam Back and January 2009 when Satoshi published Bitcoin/0.1 to account for the change. Both are perfectly competent programmers, but stylistically, they are completely different. The NYTimes tried to compare their English language in posts/emails. I'm compare their C/C++ language in their open-source code. The NYTimes merely points out they both use C++ as if that's another corroborating detail, when the actual code seems to disqualify Adam Back.

Another great question. We agree with the vision Maxthon expressed in 2020. They aren't gone from BSV — Jeff Chen is still listed as a BSV Association ambassador and NBDomain is still a feature in Maxthon 7 — but priorities clearly shifted. We think the shift in priorities was likely because they were early. The ecosystem and infrastructure weren't ready to support what they were building. Three things have changed since then: 1. Teranode is live — the scaling layer is now production-grade 2. BRC-100 exists — a standardized wallet protocol so apps don't have to integrate per-wallet 3. The overlay network is real — SHIP/SLAP discovery, identity certificates, MessageBox, encrypted P2P payments are deployed services, not whitepapers On NBDomain specifically: it's still operational and the protocol is documented. Adding NB:// resolution to Hodos's address bar isn't a huge sprint. Should we implement it? BSV today has a few hundred active users. Web3 broadly is still tiny relative to its potential. We expect that to change dramatically over the next decade — but the path to mass adoption isn't competition between existing projects for the existing audience. It's cooperation on the standards, protocols, and user experiences that will bring in the next 50 million users. We hope @Maxthon is keeping an eye on the ecosystem. When the timing is right, the more browsers building toward this, the better for everyone. For more on the original vision, check out @RealCoinGeek's videos with Maxthon founder Jeff Chen: youtube.com/watch?v=qug71B… youtube.com/watch?v=N49fMs… x.com/HodosBrowser/s…

@HodosBrowser Maxthon did the same thing.. What makes Hodos different?

One year from proof-of-concept to public beta. Hodos Browser — a privacy-first web browser with a native BitcoinSV wallet. Ad blocking, tracker blocking, fingerprint protection. Full Chromium compatibility. Your keys never leave a Rust process. It started a year ago this week at the BSV Hackathon in Austin, TX. Public beta goes live next week. More technical posts coming — the architecture, the decisions, and why we built the wallet natively.

Great question — and one we've already gotten several times a will keep getting. Quick context for anyone unfamiliar: B:// and C:// are Bitcoin URI schemes — same idea as https:// but pointing to content stored directly on the blockchain instead of a web server. (URI = Uniform Resource Identifier — the technical name for what most people call a "web address.") Unwriter's Bottle browser was built around them. When unwriter went quiet around 2020, the whole native blockchain browsing layer went unmaintained. Hodos doesn't natively handle B:// today but it is architecturally positioned to support it cleanly when someone revives it. We built on real Chromium (so HTTP works for everything you do today) AND we have a native Rust wallet running as a separate process with full blockchain access — exactly what you'd need to resolve transaction IDs into renderable content. Our version isn't a separate "Bitcoin browser" you switch to. It's one browser where a normal HTTPS tab can sit next to a B:// tab, and your wallet is the same wallet across both. No context switching. No toggling between Web2 and Web3. Bigger picture: we don't think mass adoption happens by asking people to teleport from Web2 straight to a fully on-chain web. It happens through waypoints. Hodos is fully Web2-compatible today (YouTube, Google, your bank, all of it). As Web3 protocols mature — passwordless login, micropayments, native blockchain content — Hodos users get them automatically. No second browser. No migration. Just new capabilities that work next to the ones they already know. If anyone is actively working on reviving native blockchain browsing on BSV — talk to us. We'd love to make Hodos the first browser to support it natively again.

@HodosBrowser Does it have native blockchain browsing, Bitcom (like B://)... like Bottle browser by _unwriter?

Wallet developer perspective: this would be huge. Wallets hammer WoC constantly — fetching merkle proofs (TSC/BUMP), parent transactions for BEEF ancestry, UTXO sets, output spend status. Every wallet on every device, every time the user opens it. The problem with the current model: you can't ship an API key inside a distributed wallet binary. Users would extract it instantly. So wallet devs are stuck on the free tier, which can't scale, or signing contracts that don't fit the distribution model. 402 micropayments solve both — every wallet pays per call from the user's own balance. No keys, no subscriptions, fair compensation per actual user load. Hodos agree's with John's list. A few additions wallets also depend on: - /tx/{txid}/outspend/{vout} — spend status (critical for certificate revocation checks) - /block/{hash}/header — header verification for merkle proofs Thank you @deggen tor this info - /tx/{txid}/proof/bump — now Hodos can skip the TSC→BUMP conversion entirely A 402-gated WoC ARC endpoint would give BSV real broadcast redundancy. Right now Hodos primarily goes through @MineLikeAnApe's ARC and fall back to WoC's /tx/raw — which isn't built for production load. A second production-grade ARC behind micropayments means wallets aren't single-vendor dependent for the most critical operation: getting a transaction to the network.

@johncalhooon 100% What are the most critical endpoints you'd like to see implement this?

Any chance you guys can put your API behind 402 (micropayments... one of BSV's best use cases)? I cannot afford subscription access to your API

I met @ishaan_lahoti and @johncalhooon at that hackathon. Thanks to both for contributing to Hodos during development and helping push the project forward.