Release Date: May 15th, 2019
- [desktop wallet] If a user forgot his wallet password he can restore his funds using the seed phrase (no need to manually delete the wallet database anymore) #165
- [cli wallet] Transactions can be deleted #604
- [desktop wallet] Optionally, submitting a password will be required to approve every outgoing transaction. Again, this optional behavior can be switched on/off in Settings #146
- [desktop wallet] Transaction ID is shown in extended transaction details #596
- [desktop wallet] QR code format is more robust and allows to embed data pieces beyond the receiver’s address: an amount to transfer is the first step, more parameters will be added later #617
- [desktop wallet] Groundwork was done to enable the app to speak many languages in the near future. #544
- [desktop wallet] User can change address expiration from never to 24h #560
- [desktop wallet, cli wallet] Wallet was receiving transactions while being in sync. These transactions were received on the wrong height, hence they were quickly becoming expired. Not anymore. #602
- [desktop wallet] Displaying a friendly error when timezone settings on a user’s machine are out of sync #578
- Inconsistent transaction statuses when running two or more wallets that use the same wallet.db file, cloned manually
- If multiple wallets are restored from the same seed phrase, transaction history and addresses will not be shared among the wallets
Points to mention
- In case a mobile wallet is connected to a random node and the user has both mobile and desktop wallets which are using the same seed phrase, the funds sent to the desktop wallet won’t appear on the mobile wallet. If the desktop wallet is running a local node, it will see funds sent to both wallets. The reason is that the local node (integrated into desktop wallet) always monitors the blockchain for UTXOs related to the seed of the wallet. The mobile wallet does not run a local node and thus can only monitor transactions sent to its specific SBBS addresses. Of course, no funds will be lost in any event.
For a more comprehensive list of the tasks accomplished please read here.
Verifying release binaries
PGP key: “A6C6 2C9F 5593 1860 AFF8 3BBB 997E AB9F 3DF7 F375”
- Go to https://keybase.io/beammw and get the Public PGP key.
- Download the signed binary file (with extension .asc) you want to verify.
- Verify signature using PGP Suite or any other PGP verification tools
- Atomic Swap — in progress
Download Beam Android Wallet on Google Play
Download Beam iOS Wallet on App Store
Download Beam Desktop Wallets on Beam’s website
Become a Beam Ambassador: Submit your application
QQ Beam 中国官方社区: https://jq.qq.com/?_wv=1027&k=5Mbs8N4