Skip to content

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 20 Sep 12:21
· 6 commits to main since this release

The bitgarth-web downloads contain the BitGarth web server and its required browser assets and asset catalog. Extract the entire archive and run bitgarth-web (bitgarth-web.exe on Windows) from the extracted directory. The bitgarth-cli downloads contain the companion command-line client for a BitGarth server. See the web server download instructions for runtime requirements and the installation options for other ways to run BitGarth.

Important

Do not double-click the macOS downloads in Finder — run them from
your terminal.
These are command-line programs, not app bundles, so
Finder refuses them with "Apple could not verify" and offers no way to
continue. Instead, in your terminal, cd to the extracted directory and
run ./bitgarth (or ./bitgarth-web). macOS shows a one-time
"downloaded from the Internet" prompt: click Open. After that the
binary runs normally from anywhere, including from Finder. Both macOS
downloads are signed and notarized by FernTrail B.V.; Finder refuses
every bare command-line binary regardless of notarization.

BitGarth 0.4.0

Highlights

  • The free tier now syncs balances for up to 50 supported accounts and includes
    transaction history for your first three eligible accounts.
  • Ready-to-run downloads of the BitGarth web server for Linux, macOS, and
    Windows are attached to each release, so you can run BitGarth without Docker
    and without building it yourself.

New

  • Transaction history is part of the free tier. Until now the free tier tracked
    balances only, and syncing any history required an upgrade.
  • Accounts that support automatic syncing show their mode — Transaction
    syncing
    , Balance only, or Inactive — with a short note explaining
    why, so a current balance is never presented as if its history were complete.
  • Each transaction-syncing account has a sync threshold, 1,000 transactions on
    the free tier. Once an account reaches it, the batch already in progress
    finishes, so the stored count can end up somewhat above the threshold.
    Transaction syncing then pauses and balances keep updating on their own.
  • Accounts with existing sync priority keep their place. New accounts join in
    the order you add them. Deleting an account frees its place for the next one;
    reaching a threshold or a temporary provider outage does not.
  • Each release now carries web server downloads for Linux (x86-64), macOS
    (Apple Silicon), and Windows (x86-64), alongside the command-line client.
    Each archive holds the bitgarth-web server, the web assets, and the asset
    catalog it needs at startup. The README has the platform requirements.
  • Installs that previously showed no update notice — desktop builds, and
    anything packaged outside Docker and Umbrel — now see one when a newer
    version is published, with links to the installation instructions and to the
    release. Docker and Umbrel keep the upgrade guidance written for them, and
    hosted accounts still see nothing, because updates are not yours to run there.
  • Harvest tracks balances and transactions for up to 200 supported accounts
    and raises the transaction sync threshold to 3,000 per account. The
    Upgrade page shows the current offer, as does
    https://bitgarth.app/#pricing

Fixed

  • A Bitcoin account whose history had been verified only up to an older block
    could still be labelled "Complete" after newer blocks arrived. The account now
    shows the block its history was verified through, and where no boundary can be
    proven, BitGarth says the coverage boundary is unknown rather than claiming
    complete history.
  • Reports and balances for a Bitcoin account are now marked provisional when
    they depend on blocks beyond the point its history was verified to, instead of
    being presented as settled.
  • Ethereum balance checks no longer count as completed transaction history.
    When transaction syncing becomes available, BitGarth can fetch transactions
    missed while only balances were updating.
  • Balance assertions in accounting journals readable by hledger and ledger-cli
    now use the time the balance was observed, rather than when the sync run
    finished.
  • An account with more than one address, such as a Bitcoin account created from
    an xpub, could export a balance assertion that added up balances observed at
    different moments. Those assertions are now left out rather than exported as
    something you could check.

Notes

  • Requests to BitGarth's servers now also state the operating system and
    processor architecture the app was built for, alongside the app version and
    install channel they already carried. That describes the binary making the
    request, not the device you browse from. The privacy notice, updated
    19 September 2026, covers what these requests contain and how it is used.
  • Existing accounts and their data remain in place. On the free tier, up to 50
    supported accounts sync balances, and the first three eligible among them
    sync transactions. Additional accounts remain viewable and exportable even
    when inactive.
  • Restoring a wallet data backup now preserves account priority for balance and
    transaction syncing. Backups from earlier versions still import.