BlackOak Wallet Release Notes
Posted: Sun Jul 05, 2026 11:26 pm
BlackOak Wallet Release Notes
This thread tracks BlackOak wallet releases, hashes, platform status, and upgrade notes.
Do not download BlackOak wallet binaries from random mirrors, reposted archives, social media attachments, or unofficial file hosts.
Use the official release page and verify the published checksum before running a wallet.
Current Preview Version
Each public wallet release should include:
Before using a wallet with funds:
Final paths should be confirmed during platform QA, but Bitcoin-family wallets commonly use OS-specific application data directories.
Users should not delete wallet data unless they understand exactly what they are removing.
Upgrade Policy
A wallet release should be marked as one of:
BlackOak wallet releases should be boring, verifiable, and signed whenever possible. That is the standard.
This thread tracks BlackOak wallet releases, hashes, platform status, and upgrade notes.
Do not download BlackOak wallet binaries from random mirrors, reposted archives, social media attachments, or unofficial file hosts.
Use the official release page and verify the published checksum before running a wallet.
Current Preview Version
- Client version: v31.99.0-0d4d152278bd
- Project: BlackOak Coin
- Ticker: OAK / ØAK
- Daemon:
Code: Select all
blackoakd - CLI:
Code: Select all
blackoak-cli - GUI wallet:
Code: Select all
blackoak-qt
- macOS: active build target
- Linux: planned / QA pending
- Windows: planned / QA pending
Each public wallet release should include:
- version number
- release date
- operating system
- architecture
- SHA256 checksum
- signature file where available
- known issues
- upgrade instructions
- data directory notes
- bootstrap or sync notes if needed
Before using a wallet with funds:
- Encrypt the wallet.
- Back up .
Code: Select all
wallet.dat - Store backups offline.
- Keep more than one backup.
- Never share private keys.
- Never run unsigned binaries from strangers.
- Verify hashes before launch.
- Test small transactions first.
Final paths should be confirmed during platform QA, but Bitcoin-family wallets commonly use OS-specific application data directories.
Users should not delete wallet data unless they understand exactly what they are removing.
Upgrade Policy
A wallet release should be marked as one of:
- preview
- testnet
- mainnet
- mandatory upgrade
- optional upgrade
- security release
BlackOak wallet releases should be boring, verifiable, and signed whenever possible. That is the standard.