BitBox02

shiftcrypto.ch
BitBox02

Open source hardware wallet, supporting secure multisig with the option for making encrypted backups on a MicroSD card.

Open Source

BitBox02 Source Code

Author

BitBoxSwiss

Description

The BitBoxApp for desktop and mobile.

#bech32#bitcoin#hardware-wallet#litecoin#segwit#wallet

Homepage

https://bitbox.swiss/app

Repository

  • LicenseApache-2.0
  • Created02 Aug 18
  • Primary languageGo
  • Size1,459,673 KB
  • Stars334
  • Forks134
  • Watchers334

Language Usage

Language Usage

Project Health

  • Last commit1 day ago
  • Open issues143
  • Latest releasev4.52.0

Recent Commits

  • thisconnect(16 Oct 26)

    Merge branch 'frontend-wouter'

  • thisconnect(15 Oct 26)

    frontend: allow public domain (unlicense) Wouter uses unlicense (public domain): - https://github.com/molefrog/wouter/blob/main/LICENSE

  • thisconnect(15 Oct 26)

    frontend: fix license-check not running on make buildweb Fixed license check in case .npmrc has ignore-scripts = true

  • thisconnect(08 Oct 26)

    frontend: migrate react-router to wouter Wouter provides a lightweight routing solution that covers our existing routing needs without the additional complexity and dependencies of react-router. Co-authored-by: sl <[email protected]>

  • thisconnect(15 Oct 26)

    Merge remote-tracking branch 'tom/wallet-connect-license'

  • benma(15 Oct 26)

    Merge pull request #4500 from benma-agent/benma-agent/account-utxos-result handlers: return result from /utxos

  • thisconnect(14 Oct 26)

    Merge branch 'changelog-fix'

  • thisconnect(14 Oct 26)

    docs: fix unreleased changelog entry Was added in commit: - 62a89ebcba282c85c265f9af7116e2ef04276fb0 But is not part of v4.52.0, moved to unreleased section.

  • strmci(14 Oct 26)

    Merge branch 'update_claim_topup_tests'

  • strmci(14 Oct 26)

    Merge branch 'update_claim_topup_tests'

  • benma(14 Oct 26)

    Merge pull request #4501 from benma-agent/benma-agent/account-tx-proposal-result handlers: return result from /tx-proposal

  • strmci(14 Oct 26)

    frontend: fix claim top-up test setup Provide active accounts through AppStateContext in the claim and refund tests to fix the TypeScript errors blocking CI builds.

  • beerosagos(14 Oct 26)

    Merge branch 'bump-breez-sdk-0.26.0'

  • benma's agent(21 Sept 26)

    handlers: return result from /tx-proposal Include unexpected proposal errors in the result and display them on the send screen. Preserve validation error codes.

  • benma's agent(21 Sept 26)

    handlers: return result from /utxos Return UTXO loading failures in a result struct and display them in its callers. Extracted from BitBoxSwiss/bitbox-wallet-app#4449. Coin-control dialog with a simulated UTXO loading error: | Desktop | Mobile | | --- | --- | | ![Desktop][desktop] | ![Mobile][mobile] | [desktop]: https://raw.githubusercontent.com/benma-agent/bitbox-wallet-app/b67c3d3d/utxos-error.png [mobile]: https://raw.githubusercontent.com/benma-agent/bitbox-wallet-app/b67c3d3d/utxos-mobile.png

  • Marko Bencun(14 Oct 26)

    Merge remote-tracking branch 'agent/benma-agent/ignore-stale-account-responses'

  • sl(14 Oct 26)

    Merge branch 'frontend-explorer-native-link'

  • sl(07 Oct 26)

    frontend: enable native explorer link copying

  • Tomas Vrba(21 Jul 26)

    frontend: check production dependency licenses Add a generic license check. Record expected licenses to flag changes, including between allowed licenses, and support package-specific exceptions. Run the check before builds and in CI. Add regression tests and document how to review and resolve failures.

  • sl(13 Oct 26)

    Merge branch 'frontend-showhide-passphrase'

  • sl(08 Oct 26)

    frontend: add reusable password visibility toggle

  • thisconnect(12 Oct 26)

    Merge branch 'frontend-gap-in-form'

  • sl(11 Oct 26)

    Merge remote-tracking branch 'upstream/frontend-edit-ln-invoice'

  • sl(07 Oct 26)

    frontend: preserve invoice details when going back

  • benma's agent(02 Oct 26)

    frontend: ignore stale account responses The account-code and transaction-ID comparisons used values captured from the same render, so they could not detect later prop changes. Unsubscribing only stopped future events; pending requests could still display an old transaction, overwrite balances, or report an obsolete account error. mounted.current also allowed these updates while the component remained mounted. Give each effect an active flag that cleanup invalidates when its dependencies change or the component unmounts. Check the flag before starting work and before using transaction, status, or balance responses. Pass isActive into shared loaders so transaction details and the account summary keep their separate effects. Use one effect for the UTXO load and subscription. Keep account and Lightning subscriptions in separate effects so a Lightning account change does not discard valid pending account updates. Extracted from #4449.

  • thisconnect(08 Oct 26)

    Merge branch 'frontend-refactor-app'

  • thisconnect(07 Oct 26)

    frontend: refactor and separate route props and params Ensure route components read URL parameters directly so routing state stays consistent and does not have to be threaded through props.

  • thisconnect(06 Oct 26)

    frontend: refactor routing and new-tx logic into dedicated components The main App component in app.tsx was handling multiple unrelated responsibilities: setting up application layout/providers, executing complex navigation guard redirects, and subscribing to background transaction notifications. Extracted these side-effects into dedicated headless components.

  • thisconnect(06 Oct 26)

    frontend: refactor devices-key into its own hook Encapsulate the device-derived remount key so components can derive it directly from app state, removing the remaining devicesKey prop plumbing.

  • thisconnect(06 Oct 26)

    frontend: refactor accounts and devices into app-state-context Make accounts, devices and Lightning state available through a shared context so routes and app components can consume the state directly without passing it through the component tree.

BitBox02 Security

4.6/10

Repo Security Summary

Updated 24 Aug 26

  • Code-Review10/10
  • Maintained10/10
  • CII-Best-Practices0/10
  • Dangerous-Workflow10/10
  • PackagingN/A
  • Token-Permissions0/10
  • Security-Policy0/10
  • License10/10
  • Branch-ProtectionN/A
  • Signed-Releases8/10
  • Binary-Artifacts0/10
  • Fuzzing0/10
  • SAST0/10
  • Pinned-Dependencies0/10

BitBox02 Website

Website

301 Moved Permanently

Redirects

Redirects to https://bitbox.swiss/

Security Checks

3 security checks failed (62 passed)

  • External Redirect Detected
  • Domain Recently Created
  • Domain Very Recently Created

Server Details

  • IP Address104.21.8.130
  • LocationSan Francisco,California,United States of America,NA
  • ISPCloudFlare Inc.
  • ASNAS13335

Associated Countries

  • USUS
  • CACA
  • JPJP

Safety Score

Website marked as safe

100%

Blacklist Check

shiftcrypto.ch was found on 0 blacklists

  • AntiSocial Blacklist
  • Artists Against 419
  • Badbitcoin
  • Bambenek Consulting
  • CERT Polska
  • CoinBlockerLists
  • CRDF
  • CryptoScamDB
  • EtherAddressLookup
  • EtherScamDB
  • Fake Website Buster
  • MetaMask EthPhishing
  • NABP Not Recommended Sites
  • OpenPhish
  • PetScams
  • PhishFeed
  • PhishFort
  • Phishing.Database
  • PhishStats
  • PhishTank
  • Phishunt
  • RPiList Not Serious
  • Scam.Directory
  • SecureReload Phishing List
  • Spam404
  • StopGunScams
  • Suspicious Hosting IP
  • ThreatFox
  • ThreatLog
  • TweetFeed
  • URLhaus
  • ViriBack C2 Tracker

Website Preview

Website preview

BitBox02 Reviews

More Crypto Wallets

  • A steel plate, with engraved letters which can be permanently screwed - CryptoSteel is a good fire-proof, shock-proof, water-proof, and stainless cryptocurrency backup solution.

  • Long-standing Python-based Bitcoin wallet with good security features. Private keys are encrypted and do not touch the internet and balance is checked with a watch-only wallet. Compatible with other wallets, so there is no tie-in, and funds can be recovered with your secret seed. It supports proof-checking to verify transactions using SPV, multi-sig, and add-ons for compatibility with hardware wallets. A decentralized server indexes ledger transactions, meaning it's fast and doesn't require much disk space. The potential security issue here would not be with the wallet, but rather your PC - you must ensure your computer is secure and your wallet has a long, strong passphrase to encrypt it with.

  • Sparrow is a Bitcoin wallet for those who value financial self-sovereignty. Sparrow’s emphasis is on security, privacy, and usability. Sparrow does not hide information from you - on the contrary, it attempts to provide as much detail as possible about your transactions and UTXOs, but in a way that is manageable and usable.

  • Trezor

    Trezor

    trezor.io

    Open source, cross-platform, offline, crypto wallet, compatible with 1000+ coins. Your private key is generated on the device, and never leaves it, all transactions are signed by the Trezor, which ensures your wallet is safe from theft. There are native apps for Windows, Linux, MacOS, Android, and iOS, but Trezor is also compatible with other wallets, such as Wasabi. You can back the Trezor up, either by writing down the seed, or by duplicating it to another device. It is simple and intuitive to use, but also incredibly customizable with a large range of advanced features.

  • An open source, native desktop wallet for Windows, Linux, and MacOS. Wasabi implements trustless CoinJoins over the Tor network. Neither an observer nor the participants can determine which output belongs to which input. This makes it difficult for outside parties to trace where a particular coin originated from and where it was sent to, which greatly improves privacy. Since it's trustless, the CoinJoin coordinator cannot breach the privacy of the participants. Wasabi is compatible with cold storage and hardware wallets, including OpenCard and Trezor.

About the Data: BitBox02

Edit BitBox02 Data

You can edit BitBox02's entry in this section of awesome-privacy.yml by submitting a PR to our GitHub repo.
Note that some of the information shown above has been aggregated from external sources, a list of these can be found data documentation.

Origin Data

Modify Data

API

You can access BitBox02's data programmatically via our API. Simply make a GET request to:

https://api.awesome-privacy.xyz/v1/services/bitbox02

The REST API is free, no-auth and CORS-enabled. To learn more, view the API Docs or read the API Usage Guide.

Share BitBox02

Help your friends compare Crypto Wallets, and pick privacy-respecting software and services.
Share BitBox02 and Awesome Privacy with your network!