DocsGetting StartedmacOS Installation
macOS Installation
Install bervice on macOS using the signed and notarized DMG. The build is universal (Apple silicon + Intel), with local-first encryption and a zero-knowledge architecture.
Prerequisites. macOS 12 (Monterey) or later, 4 GB RAM, ~300 MB free disk. Optional: a supported wallet (browser or hardware) for activating your on-chain subscription.
Step-by-step
- Download. Get the latest
.dmg
from the macOS release page. - Open the DMG. Double-click the file, then drag bervice to Applications.
- First Launch. Open bervice from Applications. If Gatekeeper shows a security prompt, see Allow from System Settings below.
- Create or Restore. Choose Create a new vault or Restore existing. Set a strong master password; keys are generated locally and never leave your Mac.
- Recovery. Securely save your recovery seed or key file (offline/USB).
- Subscription. Connect your wallet and activate your plan. The app confirms when the on-chain transaction finalizes.
Allow from System Settings (Gatekeeper)
If macOS blocks the app on first run, go to System Settings → Privacy & Security, click Open Anyway, then relaunch. This only appears the first time.
Verifying the Download (optional)
Releases are signed and notarized. To verify locally:
- Checksum:
shasum -a 256 bervice-x.y.z-universal.dmg
and compare with the value on the release page. - Code signature:
codesign --verify --deep --strict --verbose /Applications/bervice.app
- Notarization:
spctl --assess --type execute -v /Applications/bervice.app
Updates
Auto-update is enabled by default. You can disable it in Settings → Updates and update manually by downloading the latest DMG. Your vault remains intact during upgrades.
Troubleshooting
- “App is damaged or can’t be opened”. Re-download from the official page and verify checksum; avoid third-party mirrors.
- Wallet not detected. Ensure your browser wallet is unlocked, or connect a supported hardware wallet. Then retry subscription activation.
- No network / proxy. bervice uses system proxy/CA settings. If on a corporate Mac, confirm your proxy allows app traffic.