Browser Infrastructure Watch / Applications
Hodos Browser is bringing a native BSV Blockchain wallet architecture into a Chromium-based desktop browser, combining ordinary web browsing with BRC-100 authentication, payments, identity certificates, encrypted messaging, and transaction functions.
The application is already available as a public beta for Windows and macOS. Its renewed visibility follows a discussion about browsers becoming a practical access point through which users can interact with BSV Blockchain applications without installing a separate wallet extension.
Unlike a browser extension that places wallet logic inside the browser’s extension environment, Hodos separates its architecture into three layers. A React and TypeScript interface manages the visible browser and wallet controls, a C++ shell built on Chromium Embedded Framework handles browsing and permissions, and a Rust process performs cryptography, signing, key storage, and blockchain communication.
Under this model, the browser interface does not directly handle private keys or transaction signing. The wallet operates as an isolated local process, while the Chromium layer mediates requests between websites and the wallet.
Hodos describes this as a native wallet rather than one “bolted on” through an extension. Websites supporting BRC-100 can request authentication, transactions, certificates, or other wallet functions through the browser, subject to the user’s permissions and configured spending controls.
The beta also supports conventional BSV Blockchain addresses, allowing users to send to or receive from wallets that use standard P2PKH payments. This gives Hodos a bridge between existing wallet activity and applications built around newer BRC protocols.
Its documented protocol support includes BRC-100 for the common wallet interface, BRC-29 for direct payments, BRC-42 and BRC-43 for key derivation and invoices, and BEEF transactions with Merkle proofs for simplified payment verification. The project also lists encrypted peer-to-peer messaging and browser-to-browser payments among its implemented functions.
The browser itself is intended to operate as a conventional desktop application rather than a limited wallet interface. It includes tabs, multiple windows, browsing history, bookmarks, downloads, profiles, keyboard shortcuts, and find-in-page functions. Hodos also lists network-level ad blocking, cosmetic filtering, scriptlet injection, and browser-fingerprint protection.
Security is one of the project’s central design claims. Private keys are held in the separate Rust wallet process and are not exposed to website JavaScript. The browser applies domain-level permissions and per-site spending limits, while wallet-side checks provide an additional validation layer before transactions are approved.
On Windows, the project documents OS-level protection through DPAPI alongside PIN-based AES-256-GCM encryption. Its public website also lists macOS Keychain protection, although users should continue to treat all such security descriptions as project-reported while the application remains in beta.
The publicly accessible GitHub repository provides architecture documents, build instructions, implementation notes, and portions of the application code. However, Hodos should not be described as open-source software: its repository states that the code is proprietary and that all rights are reserved. “Open development” is the project’s preferred description.
The current public download is identified as version 0.3.0-beta.29 and supports Windows 10 or later and macOS 10.15 or later. The project does not presently list a Linux download on its public site.
The browser was already publicly available before this week. Its current news relevance comes from renewed attention to the distinction between a mobile browser with integrated wallet functions and a native Chromium desktop application built around a separately isolated BRC-100 wallet process.
Hodos remains beta software. Public availability demonstrates that the architecture can be downloaded and tested, but it does not independently establish the security of its key-management system, the reliability of every supported protocol flow, or readiness for unrestricted production use.
BSV TIMES read:
A blockchain browser becomes more significant when it does more than display blockchain-related websites. Hodos places wallet permissions, signing, payments, identity, and encrypted communication within the browser architecture while keeping private-key operations outside the web-content process. This could give BRC-100 applications a more consistent desktop environment and reduce dependence on separately installed extensions. The longer-term test will be whether the design can combine ordinary browser usability with security, compatibility, and dependable wallet behavior as the beta matures.
Posted on August 4, 2026
Leave a comment