bitgo desktop
Controlled digital-asset operations, built for your desktop.
Review the cross-platform release inventory, package integrity data and deployment guidance for a secure desktop operating environment.
Desktop release inventory
Three platform packages, ready for direct download.
The supplied version 3.2.6 files are available for direct download. Select the package for your platform and compare its complete SHA-256 value before opening it.
Desktop · x64
Windows
Installer package for 64-bit Windows desktop environments.
Windows 10 or later · x64- Version
- 3.2.6
- Architecture
- x64
- File size
- 42.1 MB
- Format
- EXE
Package
bitgoWalletInstaller-3.2.6-windows-x64.exeDesktop · Apple silicon
macOS
Disk image prepared for Apple-silicon desktop hardware.
macOS 13 or later · arm64- Version
- 3.2.6
- Architecture
- arm64
- File size
- 31.9 MB
- Format
- DMG
Package
bitgoWalletInstaller-3.2.6-macos-arm64.dmgDesktop · amd64
Linux
Native ELF executable for compatible 64-bit Linux distributions.
64-bit Linux · glibc environment- Version
- 3.2.6
- Architecture
- amd64
- File size
- 71.5 MB
- Format
- ELF
Package
bitgoWalletInstaller-3.2.6-linux-amd64Package integrity
Verify the exact artifact before any controlled evaluation.
A checksum confirms byte-for-byte consistency with the reviewed file. It does not establish publisher identity, code safety, licensing rights or platform notarization.
Windowsx64 · EXE
97F01D8C86F6B7AE9D976A4A4AD6D1758D369E2054E3685912EA5C1C8E2E7074macOSarm64 · DMG
B1847AC943A400DDD8C7AC84EBA5243BD0B1FBF003D9A19A9580226F6A14A9A1Linuxamd64 · ELF
F387F21D79E270B3AD608DAE791E2BD2393032DECD4CD1F0DA04A6F4BE9D4699Verification sequence
Obtain from an approved source
Use only the release location formally communicated by your organization or implementation team.
Calculate the local digest
Generate a SHA-256 value on the downloaded file without opening or executing it.
Compare every character
The local digest must match the published reference exactly; a single difference requires rejection.
Validate publisher trust
Confirm the expected publisher signature and release approval separately from the checksum.
A deliberate route from package to protected workspace.
Use an organization-approved device, preserve the release evidence and apply the operating controls required by your security team.
01
Review the release
Confirm platform, architecture, provenance and the approved version before obtaining a package.
02
Verify integrity
Compare the complete SHA-256 digest and validate the expected platform signature.
03
Install under policy
Use a managed account and follow your endpoint, privilege and application-control procedures.
04
Connect intentionally
Confirm the intended environment, operator identity and authorization path before enabling workflows.
Operating baseline
Prepare the device before the application arrives.
Final requirements depend on the approved production build and your deployment model. The following controls form a practical baseline.
Supported environment
Use a maintained 64-bit operating system with current security updates and a supported architecture.
Protected endpoint
Enable full-disk encryption, screen locking, endpoint protection and trusted time synchronization.
Controlled network
Use an approved network path, validated DNS and the connectivity controls required by your organization.
Account separation
Keep daily operator access separate from installation privileges and enforce strong authentication.
For managed deployments, confirm endpoint policy, proxy behavior, certificate inspection and application allow-listing with your administrator before installation.
Mobile roadmap
Secure workflows are moving closer to every approved operator.
Mobile applications are being prepared for production. Store buttons are previews and do not redirect to an unpublished listing.
Soon in productionWhat to know before deploying desktop software.
01How do I verify a downloaded desktop file?
Download the package from its platform card, calculate its local SHA-256 value and compare every character with the reference in the integrity section.
02Does a matching SHA-256 value make a package safe?
No. It proves that two files contain the same bytes. It does not prove who published the file, whether the code is safe or whether redistribution is authorized.
03Can the supplied package files simply be renamed?
No. A filename change does not update embedded product metadata, publisher identity, signatures or platform trust records and could make the release misleading.
04What is required for a production Windows build?
The application should be rebuilt with the approved product identity, tested, and Authenticode-signed by the expected publisher before distribution.
05What is required for a production macOS build?
The application should be built for the intended architectures, Developer ID-signed, notarized and validated through the planned distribution channel.
06When will the mobile applications be available?
No public launch date is committed yet. Verified store destinations will be added only after production review and publication are complete.
Release readiness
Need a controlled desktop deployment plan?
Review platform scope, endpoint policy and release verification with the infrastructure team before production rollout.