Bright Boson 2.2.5635

Attention: the current version is NOT supported in Mac OS Catalina (currently in public beta). We will fix the issue in the next version.

Features:

• [cli wallet] Atomic Swap with BTC and LTC: please read the tutorial here.

Improvements:

• [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

Fixes:

• [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

Known limitations:

• 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 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"

1. Go to https://keybase.io/beammw and get the Public PGP key.
2. Download the signed binary file (with extension .asc) you want to verify.
3. Verify the signature using PGP Suite or any other PGP verification tools

Misc

• The work on hardware wallets integration is well in the process

Testnet - Bright Boson 2.2.5648

Attention: the current version is NOT supported in Mac OS Catalina (currently in public beta). We will fix the issue in the next version.

Features:

• [cli wallet] Atomic Swap with BTC and LTC

Improvements:

• [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

Fixes:

• [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

Known limitations:

• 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 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

Hotfix - Bright Boson 2.1.4919

Fixes:

• [cli wallet, desktop wallet] Mining key generation scheme fix

Known limitations:

• 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 a 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.

Verifying release binaries:

PGP key: "A6C6 2C9F 5593 1860 AFF8 3BBB 997E AB9F 3DF7 F375"

1. Go to https://keybase.io/beammw and get the Public PGP key.
2. Download the signed binary file (with extension .asc) you want to verify.
3. Verify signature using PGP Suite or any other PGP verification tools

Testnet - Cold Wallet

Features:

• [cli wallet] Cold wallet technique allows to protect your private key it from network attacks by storing it on a "cold" air-gapped machine, separately from the rest of the data. Read into the details in our Documentation #593

Known limitations:

• 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 a 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: https://github.com/BeamMW/beam/projects/14

Misc

• The work on Atomic Swap is well in the process

Cold Wallet 2.1.4915

Fixes:

• [installer] GUI wallet for Windows is packed with https://www.advancedinstaller.com/ to prevent Bitdefender antivirus blocking

Features:

• [cli wallet] Cold wallet technique allows to protect your private key it from network attacks by storing it on a "cold" air-gapped machine, separately from the rest of the data. Read into the details in our Documentation #593

Known limitations:

• 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 a 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: https://github.com/BeamMW/beam/projects/14

Verifying release binaries
PGP key: "A6C6 2C9F 5593 1860 AFF8 3BBB 997E AB9F 3DF7 F375"

1. Go to https://keybase.io/beammw and get the Public PGP key.
2. Download the signed binary file (with extension .asc) you want to verify.
3. Verify signature using PGP Suite or any other PGP verification tools

Misc

• The work on Atomic Swap is well in the process

Hotfix - Bright Boson 2.1.4914

Fixes:

• [desktop wallet] The wallet crashes on rescan in rare cases while processing specific transactions from wallet.db file #647

Known limitations:

• 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 a 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.

Verifying release binaries:

PGP key: "A6C6 2C9F 5593 1860 AFF8 3BBB 997E AB9F 3DF7 F375"

1. Go to https://keybase.io/beammw and get the Public PGP key.
2. Download the signed binary file (with extension .asc) you want to verify.
3. Verify signature using PGP Suite or any other PGP verification tools

Bright Boson 2.1.4910

Features:

• [desktop wallet] If 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 behaviour can be switched on/off in Settings #146

Improvements:

• [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] Ground work 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

Fixes:

• [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 user's machine are out of sync #578

Known limitations

• 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 a 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: https://github.com/BeamMW/beam/projects/12

Verifying release binaries
PGP key: "A6C6 2C9F 5593 1860 AFF8 3BBB 997E AB9F 3DF7 F375"

1. Go to https://keybase.io/beammw and get the Public PGP key.
2. Download the signed binary file (with extension .asc) you want to verify.
3. Verify signature using PGP Suite or any other PGP verification tools

Misc

• The work on Atomic Swap is well in the process

Testnet Bright Boson 2.1.4920

Features:

• [desktop wallet] If 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 behaviour can be switched on/off in Settings #146

Improvements:

• [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] Ground work 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

Fixes:

• [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 user's machine are out of sync #578

Known limitations

• 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 a 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.

Bright Boson 2.0.4739

Update procedure

• [node] New version of node.db is not compatible with previous version.
  Before running new standalone node please remove old node.db and macroblock files manually.

ATTENTION!

Previous versions of node and wallet may take a REALLY long time to synchronise with new nodes.

Features

• [desktop wallet, node] Аfter being offline node sync will be lightning-fast, for both standalone node and integrated into the desktop wallet, see technical documentation (#454)
• [desktop wallet, cli wallet] For desktop wallet, upon successful transaction completion a sender will receive a proof, signed by the receiver, for cli wallet, the proof will be generated once а handshake between the wallets has been accomplished, see user manual and technical documentation (#415)

Improvements

• [desktop wallet] When sending beams, the Sender’s wallet will wait longer for Receiver to come online, namely 12 hours instead of 2 (#473)
• [desktop wallet] No more security warnings. The apps are signed now on both Mac and Windows (#37)
• [cli wallet] Transaction history will display Kernel ID from now on (#418)
• [wallet] Wallet application and Wallet API became much more responsive due to reworked request service architecture (#407)

Fixes

• [desktop wallet] Deleted transaction re-appears with “receiving” status (#554)
• [cli wallet] Fixed incorrect amounts in transaction history for certain locales (#480)
• [cli wallet, node] Fixed inconsistent params names (#249)
• [desktop wallet] Fixed crash, happened in rare cases when wallet was switched from remote to local node and restarted (#573)

For a more comprehensive list of the tasks accomplished please read here: https://github.com/BeamMW/beam/projects/10

Verifying release binaries
PGP key: "A6C6 2C9F 5593 1860 AFF8 3BBB 997E AB9F 3DF7 F375"

1. Go to https://keybase.io/beammw and get the Public PGP key.
2. Download the signed binary file (with extension .asc) you want to verify.
3. Verify signature using PGP Suite or any other PGP verification tools

Misc

• The work on Atomic Swap is well in the process

Wallet API and Node Explorer API 2.0.4739

General notes

• New methods added for transactions' list, addresses, sending specific UTXO,

• Improvements and bug Fixes
  See also detailed Wallet API protocol here.

• The Node Explorer got ability to search block by hash and kernel ID
  See also detailed Node Explorer API protocol here.

Features

• [wallet-api] Added api methods for: date of a transaction to tx_list, status to get_utxo, addr_list(own), delete_address(id), edit_address(id), get contacts list, use delete_address(id), income field to the tx_status (#528)
• [wallet-api] Added 'coins' array parameter to tx_send api (for sending specific UTXO) (#502)
• [explorer-node] Add api functions to search block by Kernel ID and Hash (#495)

Improvements

• [wallet-api] Check for unknown commands is added to Wallet API (#548)
• [wallet-api] tx-status method - Zero kernels' lines are removed for failed and canceled transactions (#537)
• [wallet-api] Added status_string and failure_reason fields to the tx_status api (#519)
• [explorer-node] Logs were moved to "logs" folder (#514)
• [explorer-node] Old logs auto-delete was implemented (#515)

Fixes

• [wallet-api, explorer-node] Added rules options to wallet and explorer api (#536)

Known limitations

• Inconsistent transaction statuses when running two or more wallets that use the same wallet.db file, cloned manually.

PGP key added: "A6C6 2C9F 5593 1860 AFF8 3BBB 997E AB9F 3DF7 F375"

Verifying release binaries

1. Go to https://keybase.io/beammw and get the Public PGP key.
2. Download the signed binary file (with extension .asc) you want to verify.
3. Verify signature using PGP Suite or any other PGP verification tools