Wallet Infrastructure Watch / Applications
Update — September 18, 2026: Kallubi has confirmed to BSV TIMES that v1.0.1 was the wallet’s first public drop and that v1.0.2 is now the current desktop build for Linux, Windows and Apple Silicon Macs. The developer says HD restore and live balances are working, while a Windows save step following Restore is still being corrected and documentation is being refined. Kallubi asks users to treat the current desktop builds as public testing releases rather than a finished 1.0 general release, and to begin with small amounts.
In Brief
Kallubi BSV Wallet has moved to version 1.0.2 as its current public-testing desktop build, following the first public drop of version 1.0.1.
The independently developed, non-custodial wallet is available for Linux, Windows and Apple Silicon Macs and includes an HD recovery system designed to scan multiple derivation conventions used by earlier BSV wallets.
A user can enter compatible recovery material and have Kallubi search known receive and change paths for funded addresses rather than manually reconstructing each historic wallet configuration. Current presets cover derivation styles associated with Centbee, Centi BSV, RockWallet, ElectrumSV, Ellipal, RelayX, HandCash 1.x and simply.cash, alongside custom-path recovery.
Kallubi has clarified directly to BSV TIMES that the current desktop builds should be treated as public testing software rather than a finished 1.0 general release. The developer says HD restoration and live balances are functioning in v1.0.2, while a Windows save step following Restore is still being corrected and the documentation is being refined.
The Kallubi BSV Explorer source is public. The wallet source is not yet public and is planned for release after the current restore and save issues are cleaned up.
News Report
Kallubi BSV Wallet has advanced to version 1.0.2 as development continues on an independently maintained desktop wallet focused partly on recovering funds created under different derivation conventions used across earlier generations of BSV wallets.
Version 1.0.1, released publicly on September 17, was the project’s first public desktop drop.
Kallubi has since replaced it with version 1.0.2 on its download page for Linux, Windows and Apple Silicon Macs.
In a direct clarification to BSV TIMES, the developer stressed that the version numbering should not be interpreted as indicating a finished general-release product.
The current desktop builds should instead be treated as a public testing release.
Kallubi says HD restoration and live balance detection are working in the current version, while development is continuing on a Windows save step that follows Restore and on tightening the accompanying documentation.
Users are being advised to begin with small amounts.
One Seed Can Lead to Different Addresses
The most distinctive part of Kallubi’s current wallet is not another basic send-and-receive interface.
It is an attempt to address a practical recovery problem created by years of differing wallet implementations.
Hierarchical deterministic wallets generate many keys from common root material, but the derivation path determines which branches and addresses are produced.
Two wallets can therefore begin with the same compatible seed while deriving different addresses.
That creates a familiar recovery problem.
A user can possess the correct mnemonic yet import it into another wallet and see a zero balance because the replacement software is looking along a different derivation path from the one used by the original wallet.
The funds have not necessarily disappeared.
The replacement wallet may simply be looking in the wrong place.
Kallubi attempts to reduce that problem by searching several known derivation conventions automatically rather than requiring the user to identify and enter every historical path manually.
Scanning Earlier BSV Wallet Conventions
Kallubi’s current HD recovery system searches both receive and change chains.
Development information published around the 1.0.1 release described the recovery scan as checking a gap of 130 addresses while working across several wallet-specific path conventions.
The interface currently provides presets associated with Centbee, Centi BSV, RockWallet, ElectrumSV, Ellipal, RelayX, HandCash 1.x and simply.cash.
A custom-path option is also available when the required derivation pattern is not included among the supplied presets.
The recovery guide describes the current system around BIP39, BIP32 and BIP44-style derivation and includes Kallubi’s own path alongside conventions in the m/44'/0'/… and m/44'/236'/… families.
BRC-42 recovery is not part of the current implementation.
That boundary is important.
Kallubi should not be understood as a universal recovery engine for every wallet architecture that has existed on BSV.
Its purpose is narrower: when users already possess valid compatible recovery material, the software can search several known historical derivation conventions and identify addresses where funds are found.
The Optional “13th Word”
Kallubi also supports what its interface describes as an optional 13th word.
Technically, this is a BIP39 passphrase used in combination with the mnemonic rather than an additional word appended to the original 12-word phrase.
The distinction matters during recovery.
The same mnemonic combined with a different passphrase derives different keys and therefore different addresses.
A user who originally protected a wallet with a BIP39 passphrase must use the corresponding passphrase when attempting to locate the expected addresses.
The wallet password is separate from both.
It protects locally stored wallet data rather than changing the deterministic seed derivation itself.
Recovery Uses Network Lookups
Although Kallubi is non-custodial and keeps the user’s keys on the local machine, its recovery scan should not be understood as an entirely offline process.
The wallet can derive candidate addresses locally, but identifying whether those addresses contain transaction history or spendable value requires information from the network.
Kallubi therefore tells users that the HD scan communicates externally while checking generated addresses and may take time to complete.
This separates two different concepts that are sometimes grouped together.
Key custody can remain local while blockchain lookup remains network-connected.
Kallubi’s published roadmap has also identified reducing dependence on external lookup infrastructure through its own node as an area of continuing work.
Its earlier user guide describes a related transaction-broadcast arrangement in which Kallubi’s own node is attempted first, with WhatsOnChain available as a fallback.
Local control of keys therefore does not imply that every network operation is performed entirely within the desktop application.
HD Restore Works, but Windows Save Work Continues
The developer’s September 18 clarification gives a more precise picture of the current release status than was publicly available when version 1.0.1 first appeared.
Kallubi says that HD restore and live balances work in version 1.0.2.
However, a Windows-specific save step following Restore is still being corrected.
The developer did not characterize the underlying HD recovery itself as non-functional. Instead, the remaining issue concerns a later save step in the Windows flow.
Documentation is also still being tightened as the desktop baseline develops.
That is why Kallubi asks users to treat the current builds as public testing software and to begin with small amounts rather than interpreting the 1.x version number as evidence of a finished stable release.
A Conventional Desktop Wallet Around the Recovery Layer
Outside the recovery system, Kallubi provides the conventional functions expected from a self-custodial desktop BSV wallet.
Users can create a new 12-word wallet, generate receiving information, send BSV, view transaction history and protect the locally stored wallet with a password.
Wallet state is stored locally rather than through a Kallubi user account.
The current 1.0.2 testing build is distributed for three desktop platforms:
Linux through an x64 AppImage, Windows through a portable executable, and macOS for Apple Silicon.
Kallubi has also published checksums alongside its downloadable builds so users can compare downloaded files with the hashes supplied by the developer.
The project describes itself as independent, non-custodial and non-commercial.
Independent From BSV Association
Kallubi also explicitly separates its wallet from BSV Association and from WhatsOnChain.
It is an independent wallet implementation.
That distinction remains useful as multiple wallet architectures continue developing across BSV.
Some current projects are centered on the BRC-100 wallet-to-application model, derived-key systems and richer application permissions.
Kallubi’s present desktop wallet is focused more directly on conventional hierarchical deterministic recovery, address discovery, UTXO management and ordinary payment functions.
The approaches therefore solve different problems.
Kallubi’s immediate emphasis is compatibility with recovery material that users may already possess from earlier BSV wallet software.
Explorer Source Is Public; Wallet Source Is Not Yet
Kallubi has also clarified the source-code status directly to BSV TIMES.
The Kallubi BSV Explorer source is public on GitHub.
The Kallubi BSV Wallet source is not yet public.
The developer says the wallet repository will be released after the current restore and save issues have been cleaned up, with the intention that the first public source commit correspond closely to what users are actually downloading.
That means the current wallet should not yet be described as open source.
It is a publicly downloadable non-custodial application with published binaries and checksums, while publication of the wallet repository remains planned.
Once available, the wallet source should provide developers and users with an additional way to inspect its implementation of seed handling, path scanning, transaction construction and local storage.
Android Comes After the Desktop Baseline
Kallubi also confirmed that an Android version remains planned.
It is not yet being assigned an app-store date.
The developer’s immediate priority is establishing the current desktop baseline, resolving the remaining restore/save issues and publishing the wallet source before proceeding to Android.
That places mobile development behind completion of the present desktop-testing phase rather than alongside it.
From First Public Drop to Public Testing
The clarification also establishes a useful chronology.
Version 1.0.1 was Kallubi Wallet’s first public drop.
Version 1.0.2 is now the version distributed through the project’s website.
Neither should be treated as a finished general release simply because the software carries a 1.x version number.
The developer’s preferred description is public testing.
That terminology better reflects the project’s actual stage: the wallet is publicly downloadable and can operate with real BSV, but its maintainer is still actively correcting platform-specific behavior, improving documentation and asking users to proceed cautiously.
BSV TIMES Read
Kallubi Wallet’s recovery work addresses a problem that becomes increasingly visible as an ecosystem accumulates several generations of wallet software.
A seed phrase is commonly spoken about as though it were the wallet.
It is not.
The seed supplies root material from which keys can be derived.
Software still needs to know how those keys were derived.
If an older wallet and a replacement wallet follow different paths, possession of the correct recovery words does not automatically cause the expected addresses to appear.
That is why multi-path recovery has practical value.
Kallubi attempts to move some of that historical knowledge from the user into the wallet itself.
Rather than expecting somebody to remember which application, account branch and derivation convention was used years earlier, the software can test several known patterns and report where funded addresses are detected.
At the same time, the developer’s clarification about release status matters.
Recovery software deals directly with the material that controls user funds. Public availability and a 1.x version number should not substitute for a clear statement about maturity.
Kallubi has now provided that statement itself.
The current wallet is a public testing release.
HD recovery and live balances are operating, but work remains on the Windows restore/save flow, documentation is still being refined, and the wallet’s source repository has not yet been published.
That makes caution appropriate without diminishing the underlying problem the project is attempting to solve.
The recovery problem is older than Kallubi’s software.
Users should be able to move between wallet implementations without losing visibility of funds simply because the replacement wallet defaults to a different derivation path.
Kallubi’s contribution is compatibility work: preserving a practical route between recovery material created under earlier wallet conventions and software available today.
Version 1.0.2 is still part of that testing process.
But the goal it addresses is straightforward and increasingly important: recovery material should remain useful even when the wallet that originally created it is no longer the wallet a user wants—or is able—to run.
Source Links
Kallubi BSV Wallet — Download Page
Kallubi BSV Explorer — Roadmap
Primary-source clarification provided directly to BSV TIMES by the Kallubi developer on September 18, 2026.
Originally posted September 17, 2026; updated September 18, 2026
Leave a comment