Kallubi Publishes RockWallet BSV Recovery Path Ahead of September 30 Legacy-App Retirement

Wallet Infrastructure Watch / Applications

In Brief

Kallubi BSV Wallet has published a dedicated recovery path for users who still hold BSV through RockWallet’s legacy application, which RockWallet has confirmed is scheduled to retire on September 30, 2026.

The recovery method uses RockWallet’s documented BIP32 derivation path, m/0'/0/0, allowing users who retain their legacy 12-word recovery phrase to scan for the corresponding BSV addresses through Kallubi Wallet.

The development comes as Kallubi moves to version 1.0.3, which the developer now describes as its current public desktop release rather than a public-testing build in the earlier 1.0.2 sense.

Kallubi has also published the BSV Wallet source repository, fulfilling an earlier commitment to make the wallet code public after completing additional restore and save work.

The wallet remains independent, non-custodial software. Kallubi advises users to verify downloaded SHA256 hashes and begin with a small amount before relying on the recovery workflow.

News Report

Kallubi has published a recovery procedure intended to help legacy RockWallet users retain access to BSV after RockWallet’s original application is retired on September 30.

The development addresses a specific compatibility problem.

RockWallet’s legacy BSV wallet derives addresses using the BIP32 path:

m/0'/0/0

RockWallet documents that path in its own support material and warns that restoring a wallet into another application requires compatible derivation rules. A correct recovery phrase imported into software using another derivation path can produce different addresses and therefore appear to show no funds. RockWallet Help Center

Kallubi Wallet already included multi-path HD recovery designed around that problem.

Its new RockWallet guidance applies the system directly to users affected by the retirement of the legacy application.

RockWallet Legacy App Retires September 30

RockWallet has publicly confirmed that its legacy application is scheduled to retire on September 30, 2026.

The company has rebuilt its wallet around a newer application and is encouraging legacy users to move their assets before the earlier software is withdrawn.

For users able to access the new RockWallet, the conventional migration route is straightforward: create the new wallet, obtain a new receiving address and send assets from the legacy application before it is retired. RockWallet’s migration documentation describes this as an on-chain transfer rather than restoration of the old wallet inside the new application. RockWallet

That route does not work equally for everyone.

RockWallet says its new application is currently available only in the United States, with functionality varying by state. Users outside the U.S. may therefore be unable to migrate directly into RockWallet 2.0. RockWallet Help Center

This is where independent recovery options become more relevant.

RockWallet Documents the BSV Recovery Problem

RockWallet itself acknowledges that BSV presents a different recovery situation from several other assets supported by its legacy wallet.

Its support documentation lists validated third-party recovery options for some assets, but states that it has not validated a third-party wallet using the same derivation path for BSV recovery.

RockWallet instead documents an advanced independent route involving BIP39/BIP32 recovery tools and ElectrumSV, while making clear that such third-party methods are not built, owned or verified by RockWallet. RockWallet Help Center

That distinction is important for understanding Kallubi’s role.

Kallubi is not an official RockWallet successor and is not presented by either side as such.

It is an independent BSV wallet implementing the derivation convention that RockWallet publicly documents.

Kallubi Uses the RockWallet Path Directly

Kallubi’s recovery article gives users two basic options.

The first remains the preferred route whenever the old RockWallet application can still send normally: create or use another wallet, generate a receiving address and send the BSV from RockWallet while the legacy application remains functional.

No seed restoration is required in that case.

The second route applies when the user needs to recover directly from the legacy RockWallet recovery phrase.

Kallubi instructs users to choose its seed-recovery function, enter the 12-word phrase, use RockWallet’s m/0'/0/0 derivation path and scan the resulting HD addresses.

The wallet can then search for addresses associated with the recovery material and report balances found on the corresponding path.

This is the same class of compatibility problem BSV TIMES examined earlier in September when Kallubi first expanded its multi-path recovery support.

A seed phrase alone does not specify every wallet convention.

The derivation path determines which keys and addresses the software produces.

If the path changes, the resulting addresses change even though the underlying mnemonic remains the same.

RockWallet’s own documentation makes the same point: importing assets into another wallet requires the derivation path to match. RockWallet Help Center

Recovery Does Not Move the BSV

Restoring the legacy phrase through a compatible derivation path does not itself move the BSV.

The tokens remain at the same BSV Blockchain addresses.

The recovery process reconstructs the private keys needed to control those addresses.

That distinction matters because a wallet application is not the location of the asset.

RockWallet’s own recovery documentation states that assets remain on their respective blockchain and can be accessed from compatible wallet software when the correct recovery material and derivation rules are available. RockWallet Help Center

Once Kallubi identifies the corresponding addresses, the user can restore access and then decide whether to retain the wallet there or send the BSV to another address.

Kallubi 1.0.3 Is Now the Public Desktop Release

The RockWallet guidance also arrives alongside a change in Kallubi Wallet’s own release status.

Earlier this month, Kallubi asked BSV TIMES to describe versions 1.0.1 and 1.0.2 as public testing releases, rather than finished general releases.

That classification has now changed.

Kallubi has confirmed directly to BSV TIMES that version 1.0.3 is the current public desktop release and should no longer be described as a public-testing build in the 1.0.2 sense.

The current version is distributed for:

Linux as an AppImage
Windows as a portable executable
macOS for Apple Silicon

Kallubi continues to recommend that users verify the published SHA256 hash of their downloaded file and initially test the wallet with a small amount.

The developer also reiterates that Kallubi is independent software, is non-custodial and carries no warranty.

An Android application is in development but is not part of the 1.0.3 release.

Wallet Source Is Now Public

Another significant change from BSV TIMES’ earlier Kallubi coverage is source availability.

When BSV TIMES contacted Kallubi following the 1.0.2 release, the developer confirmed that the Kallubi BSV Explorer source was public but the wallet source was not.

The developer said the wallet repository would be published after the remaining restore and save issues were cleaned up so that the first public code corresponded more closely to the software users were actually downloading.

That repository has now been published:

github.com/Kallubi/kallubi-bsv-wallet

The release therefore closes one of the open questions from the earlier report.

Kallubi Wallet can now be inspected as publicly available source rather than only through distributed binaries and published hashes.

That is particularly relevant for recovery software, where users may want to inspect—or have others inspect—how seed material, derivation paths, key storage and transaction construction are handled before using the application with existing wallet credentials.

Independent From RockWallet

The relationship between the projects should remain clear.

Kallubi is not affiliated with RockWallet.

RockWallet has not endorsed Kallubi as its official BSV migration tool, and RockWallet’s documentation explicitly tells users to independently verify any third-party recovery software before entering a recovery phrase. RockWallet Help Center

Kallubi similarly describes itself as independent software.

Its RockWallet guidance is therefore best understood as an additional compatibility route built from publicly documented wallet standards.

This is also why Kallubi recommends transferring BSV normally from the legacy RockWallet whenever that remains possible.

Direct seed recovery is the fallback for users who need to reconstruct wallet access rather than simply send their balance elsewhere.

Particularly Relevant Outside the United States

The timing matters most for legacy RockWallet users who cannot use the new application.

RockWallet’s current support documentation states that the rebuilt application is not available outside the United States because of regulatory restrictions. RockWallet Help Center

That creates a different migration problem from the one facing an eligible U.S. user.

A U.S. user can generally install the replacement RockWallet, create a new wallet and send BSV into it before the legacy application retires.

A user outside the supported region may need to move the BSV to another independent wallet instead.

If the legacy application remains operational, an ordinary send is still the simpler path.

If direct access becomes unavailable afterward, possession of the original recovery phrase and knowledge of the corresponding derivation path become the continuity mechanism.

Kallubi’s new guide is aimed at that second situation.

BSV TIMES Read

This development demonstrates why wallet interoperability is not merely a developer convenience.

Wallet applications have lifecycles.

They are launched, redesigned, restricted to particular jurisdictions, replaced by new architectures or eventually retired.

The keys and outputs they once controlled can outlive the software.

That is where standards such as deterministic recovery become practically important.

RockWallet’s legacy BSV wallet used a documented BIP32 path.

Kallubi does not need access to RockWallet’s internal systems or user accounts to reconstruct addresses created under that convention.

It needs the recovery material held by the user and the derivation rules that explain how that material was transformed into keys.

That is one of the central properties of self-custody.

The wallet application can disappear while the user’s ability to reconstruct control survives.

But the process works smoothly only when enough technical information remains available.

The recovery phrase is one part.

The derivation path is another.

Kallubi’s multi-path work has been aimed at preserving that second piece of historical knowledge inside new wallet software rather than requiring users to reconstruct it themselves.

RockWallet’s September 30 retirement now provides a concrete example of why that matters.

There is no need to portray the situation as a conflict between the two wallets.

RockWallet has built a new application and documented how users should migrate. It has also published the derivation path used by the legacy BSV wallet and acknowledges independent recovery as an option where direct migration is unavailable. RockWallet Help Center

Kallubi is taking that documented information and providing another implementation capable of using it.

The publication of the Kallubi Wallet source strengthens that continuity story further.

Users are no longer being asked only to trust a downloadable recovery executable.

The implementation itself is now available for inspection.

With the legacy RockWallet application scheduled to retire on September 30, the immediate advice remains simple: users who can still access and send their BSV should move it while the original application remains available.

For those who later need to rely on the recovery phrase instead, compatibility with the original derivation path is what preserves access.