Repository navigation
v0.4.2
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.2
Highlights
- The Wallets page and net worth now show the same current balance as the
account page, including for wallets whose transaction history stopped
syncing at the plan limit. - Stopping, restarting, or updating BitGarth in Docker or on Umbrel now
finishes within seconds instead of waiting to be forcibly stopped.
Fixed
- A wallet whose transaction history stopped syncing at the plan limit could
show a wrong balance on the Wallets page, such as 0 ETH, and be left out of
net worth, while its account page showed the correct balance. The Wallets
page now uses the account's latest current balance. - A balance BitGarth has not been able to fetch, such as an Ethereum balance
before an Etherscan API key is added, no longer shows as 0. It now shows as
Not available, and net worth says how many assets it leaves out because
they have no balance or price. - BitGarth now shuts down cleanly when Docker or Umbrel asks it to stop. It
gives open requests up to five seconds to finish, then exits. Previously it
ignored the request until it was forcibly stopped, which on Umbrel could
take a full minute.