Attention: the current version is NOT supported in Mac OS Catalina (currently in public beta). We will fix the issue in the next version.
- [cli wallet] Atomic Swap with BTC and LTC: please read the tutorial here.
- [desktop wallet] During wallet upgrade, the latest wallet database is selected automatically (manual mode is still available for advanced users)
- [desktop wallet] If Caps Lock is on when entering the password, dedicated notification is shown
- [desktop wallet] Address names can be edited
- [desktop wallet] QR code can be shown for any address
- [desktop wallet] "Where to buy BEAM?" button is introduced (this handy feature should be used with care - opening a browser from the wallet carries some privacy risks, hence explicit approval will be required before accessing the external web server)
- [cli wallet] Transaction history shows transaction types
- [desktop wallet] When the user disables mandatory password submission for every outgoing transaction he will be asked to enter the current password to confirm
- [desktop wallet] Address can be copied directly from Edit Address dialog
- [desktop wallet] During rescan procedure some blocked UTXO were marked as available
- [desktop wallet] Wallet looks as pretty as expected when its window is maximized
- Inconsistent transaction statuses when running two or more wallets that use the same
wallet.dbfile 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 the 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: https://github.com/BeamMW/beam/projects/14
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 the signature using PGP Suite or any other PGP verification tools
- The work on hardware wallets integration is well in the process