Skip to content

Add bearby wallet#4671

Closed
hicaru wants to merge 13 commits intobitcoin-dot-org:masterfrom
hicaru:add_bearby_wallet
Closed

Add bearby wallet#4671
hicaru wants to merge 13 commits intobitcoin-dot-org:masterfrom
hicaru:add_bearby_wallet

Conversation

@hicaru
Copy link
Copy Markdown

@hicaru hicaru commented Apr 18, 2026

Hi, i want to add Bearby wallet to the list.

Bearby is a non-custodial bitcoin wallet written in Rust. It has post-quantum key storage which i think is pretty unique compared to other wallets here. Available on Android, iOS, macOS and Linux.

What i added:

  • wallet entry file with mobile and desktop platforms
  • icon (144x144)
  • 4 screenshots for each platform (250x350)
  • translations for all locales

Some details about the wallet:

let me know if something is missing or needs to be changed

Rinat added 13 commits April 19, 2026 03:32
Bearby is a free open source Bitcoin wallet with full private key control.
Runs on Android, iOS, macOS and Linux. Supports bech32 native segwit
addresses, legacy addresses and hardware wallets via Ledger (USB and
Bluetooth).

Source code under GPL-3 at https://github.com/bearbywallet/Bearby

Android: https://play.google.com/store/apps/details?id=com.zilpaymobile
Huawei AppGallery: https://appgallery.huawei.com/app/C113872161
Direct APK: https://github.com/bearbywallet/zilpay-mobile/releases/latest/download/app-release.apk
iOS: https://apps.apple.com/app/bearby-wallet/id1547105860
macOS and Linux: https://bearby.io
…scription

- Add missing titleshort field so wallet name displays in listing
- Replace icon with new pink/purple gradient paw design
- Replace mac/linux screenshots with desktop UI image
- Replace android/ios screenshots with mobile UI image
- Fix description: "written in Rust" instead of "memory-safe Rust cryptography"
- Remove Trezor from supported hardware wallets (not supported)
Remove redundant platform sentence from walletbearby description in
en.yml, reducing length from 320 to 279 chars after the YAML colon.
@crwatkins
Copy link
Copy Markdown
Contributor

Thanks for your submission.

I installed the wallet on two iOS devices and spent just a few minutes with the app. When trying to restore a wallet I got an error Unsupported operation: Cannot clear a fixed-length list. Trying again I got background Error: BIP39 error: Invalid word count:0. When I tried to restore a SeedQR code, the app read the QR code and silently did nothing. I finally got it to take a 12 word seed, yet it didn't display any of the funds in the wallet even after leaving it for many minutes and performing many refreshes.

I later asked the wallet for an address, sent funds to that address, and asked the wallet for another address and it did not give me a new address (as required for listing).

On the Send screen, the app asked me to "Edit gas" and gave me a screen including Max Priority Fee, Gas Limit and Nonce which are not Bitcoin terminology (at least in this context).

I will be candid here: The errors and inability to restore funds I encountered while trying to restore a wallet, and the general UI issues and cryptic error messages I encountered while using the app for only a few minutes along with disregard for Bitcoin terminology/concepts do not reflect a wallet which is at the level required for a bitcoin.org review. While other members of the community may be willing to proceed with such a review, I feel I should let you know that I personally will not be available for that review.

@hicaru hicaru closed this Apr 20, 2026
@hicaru
Copy link
Copy Markdown
Author

hicaru commented Apr 20, 2026

Thank you for the detailed review. The issues you identified are real and
not acceptable for a bitcoin.org listing. I'm closing this PR to address
them properly rather than patching in place. Specifically I will fix:

  • Restore wallet flow (the Cannot clear a fixed-length list and
    Invalid word count:0 errors indicate broken state handling in the
    restore path)
  • SeedQR support with proper user feedback on failure
    Balance fetch and address subscription for restored wallets
  • Address rotation on the receive screen — a new address per request,
    never reuse
  • Separate the Bitcoin Send flow from the EVM one: no gas / nonce /
    priority fee on Bitcoin, replace with fee rate in sat/vB, RBF toggle
    if supported, etc.
  • Audit error surfaces so users see actionable messages instead of
    raw Dart/Rust errors

I'll resubmit once these are fixed and I have a public release with at
least 3 months of user feedback confirming the fixes work.

@crwatkins
Copy link
Copy Markdown
Contributor

@hicaru Sounds good! Thanks!

Be sure to carefully review the listing requirements. Some are fairly terse, so please feel free to reach out for any help or clarification. You can open a new issue, or actually just ask right here.

Since you seem receptive to input, I'll provide some extra comments here that are very subjective and not directly related to the listing criteria and thus I would not normally mention. The general UX seemed very confusing compared to most other wallets. The three icons across the bottom meant absolutely nothing to me as well as the scattered UI elements on the page other than the Send and Receive buttons (and only because they were labeled in English) and the gear icon. Every other UI element/icon on the page was a total "whack-a-mole" and on more than half, when selected and a page popped up, I wasn't sure what I was supposed to do on it or what it was telling me. There is sufficient obfuscation in the UI such that the few times I went looking for something I had already found once (such as changing the address type) I had absolutely no idea where to look again. There is definitely some room for usability improvements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants