Today’s Community Picks highlights posts, projects, ideas, and reader comments from around the BSV community that remain worth attention. Some are new, some are continuing threads, and some are earlier signals that still help explain where builders and community voices are focused.
Browsers / Wallet Infrastructure
Hodos Browser puts a native BSV wallet inside a full Chromium browser
Hodos Browser is now available as a public beta for Windows and macOS.
The project combines a Chromium-based browser with a native BRC-100 wallet, rather than depending on a wallet extension added after installation. Its architecture separates the browser interface from a Rust wallet process so that private keys are not handled directly by website JavaScript.
The beta also includes advertising and tracker blocking, fingerprinting protection, legacy-address compatibility, direct-payment support, and BEEF/SPV transaction handling.
This is a meaningful application-layer direction because browsers sit between users and nearly everything they do online. When identity, payments, certificates, and signed actions are native browser capabilities, compatible websites can interact with a user-controlled wallet without requiring a separate account and extension for every service.
Hodos remains beta software, and the project says a formal security audit is planned before version 1.0. Users should therefore begin with small amounts, preserve their recovery information carefully, and treat the current release as active public testing.
Source: Hodos Browser / GitHub / X
Physical Infrastructure / Wine Provenance
dVIN explores shared infrastructure for the wine economy
A 2026 case study on dVIN Labs remains worth attention as an example of blockchain infrastructure connected with a long-established physical industry.
Wine moves through vineyards, producers, storage facilities, distributors, merchants, restaurants, collectors, and secondary sales. Each stage can generate records about origin, ownership, condition, authenticity, and transfer, but those records often remain divided among separate organizations and databases.
dVIN’s model explores decentralized physical infrastructure for connecting these participants through more transparent and reliable records.
The important idea is larger than attaching a digital certificate to a bottle. A bottle can accumulate a continuing history as it moves through the industry, while producers, owners, and service providers can coordinate around records that are not confined to one company’s private platform.
Blockchain does not prove that every piece of submitted information is true. Physical verification, trusted participants, sensors, and responsible data entry remain necessary. What a public ledger can provide is continuity: once an event or claim is recorded, its later alteration becomes detectable.
That makes wine a useful example of how BSV Blockchain can support provenance, ownership history, and coordination around physical goods.
Source: BSV Blockchain case study
Developer Education / Bitcoin Script
bsv-no-wallet shows what exists beneath a wallet framework
The bsv-no-wallet repository is a small educational project designed to show the basic components beneath a BSV wallet.
Instead of beginning with a complete wallet framework, it reduces the process to four parts: hold a private key, find available transaction outputs, assemble and sign a transaction, and broadcast it.
The repository then moves beyond a conventional payment by introducing a hash puzzle and a claimable quiz. Coins can be locked behind the hash of an answer and later claimed by providing the correct answer, demonstrating that an output is controlled by a locking script rather than by an address in the abstract.
A recent community post documented completing this exercise and creating a hash-puzzle transaction after working through the accompanying learning material.
This kind of experiment is valuable because wallet interfaces can hide what Bitcoin transactions actually do. Frameworks remain useful and necessary for secure applications, but builders benefit from seeing the lower-level mechanism before relying on higher-level abstractions.
The repository uses mainnet with very small amounts and clearly identifies itself as a learning tool. Private keys created for the exercise should never hold meaningful value.
Smart Contracts / Developer Experiments
pow20-runar implements a proof-of-work BSV-21 contract through Rúnar
pow20-runar is an experimental implementation of a proof-of-work BSV-21 token contract using Rúnar.
The repository provides equivalent contract frontends in TypeScript and Zig, both compiling into Bitcoin Script. Its design uses a hash puzzle with gradually increasing difficulty and covenant rules that verify the continuation of the contract and the output carrying each reward.
The project is interesting less for the token itself than for what it demonstrates about the development environment.
A contract can be expressed in a higher-level language, compiled into native Bitcoin Script, tested through different language frontends, and constrained so that future transaction outputs must follow defined rules. That gives builders a more readable way to experiment with state, issuance conditions, difficulty, rewards, and transaction structure.
The repository remains alpha-stage reference work. It has no formal release and should not be treated as a finished platform or broadly adopted standard.
Even so, it offers another practical example of Rúnar being used to move from high-level contract logic to scripts that execute directly through BSV Blockchain transactions.
Update — July 21, 2026
Leave a comment