Releases: BeamMW/beam
Testnet Bright Boson 2.0.4740
General notes
- This Testnet release includes further improvements in the fast sync mechanism and a bug fix in desktop wallet
Fixes
Testnet Bright Boson 2.0.4721
General notes
- This Testnet release solves 3 bugs found in desktop wallet
Fixes
- [desktop wallet] Wallet crashes when deleting transaction (didn’t happen on Mainnet) (#552)
- [desktop wallet] Deleted transaction re-appears with “receiving” status and always expires later (#554)
- [cli wallet, node] Fixed inconsistent params names (#249)
Misc
- The work on Atomic Swap is well in the process
Testnet Bright Boson 2.0.4707
Features
- [desktop wallet, node] Аfter being offline node sync will be lightning-fast, for both standalone node and integrated into the desktop wallet (#454), see technical documentation
- [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
- [cli wallet] Fixed incorrect amounts in transaction history for certain locales (#480)
For a more comprehensive list of the tasks accomplished please read here: https://github.com/BeamMW/beam/projects/10
Known issues and workarounds
- [node] When starting a standalone node, node.db and macroblock files should be manually removed
Misc
- The work on Atomic Swap is well in the process
Node Explorer API Bright Boson 2.0.4431 (hotfix)
General notes:
- Hotfix release
Fixes:
- When returning block data after rollback the cache was not reset and old data was returned. A fix to reset the cache was applied. (#508)
PGP key added: "A6C6 2C9F 5593 1860 AFF8 3BBB 997E AB9F 3DF7 F375"
Verifying release binaries
- 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
Wallet API and Node Explorer API 2.0.4429
General notes
-
The release includes new features - Authentication, Whitelist and API Read only mode
-
Bug Fixes
See also detailed Wallet API protocol here. -
The Node Explorer provides information about current chain state and blocks.
See also detailed Node Explorer API protocol here.
Features
- [wallet-api, explorer-node] Whitelist for API and explorer-node API #497
- [wallet-api] API Access Control List (ACL) and Transport Layer Security (TLS) protocol #488 #489
- [explorer-node] Gets current blockchain status
- [explorer-node] Gets block info for a specified height
Improvements
- [wallet-api] Pagination to get_utxo and tx_list API calls #323
- [wallet-api, explorer-node] Updated cfg templates #499, #500
- [explorer-node] New parameters are added to the explorer-node "--key_owner" and "--pass" #484
Fixes
- [wallet-api] API hanging "EXCEPTION: sqlite error code=14, unable to open database file" #466
- [wallet-api] Bug with validate_address API for own addresses #481
- [explorer-node] Can't get a block info without requesting of the status #501
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
- 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
agile-atom-1.2.4421 (hotfix)
General notes:
- Hotfix release
- The fix is relevant only for wallet-api
Features:
PGP key added: "A6C6 2C9F 5593 1860 AFF8 3BBB 997E AB9F 3DF7 F375"
Verifying release binaries
- 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
Testnet 1.2.4412
General
These are the Release Notes regarding the Testnet Environment we've been working on and on which the Android Beta Wallet is working.
In order to clarify the coexistence system between all Beam's environments, please have a look below.
The following networks exist in Beam realm:
- Mainnet: the network with real money and actual transactions.
- Testnet: staging environments for trying new features and helping to find the early bugs in our wallet, node, and miner software. For advanced users only.
- Masternet: new features in the daily development cycle, if you find yourself on this network it means that you are either very early adopter or Beam code contributor.
Hence, sometimes you wanna play with the new features on Testnet while sending the “real money” over the Mainnet. It’s easy as most features work out-of-the-box and slight visual differentiations such as backgrounds or special messages will always hint whether you are on Mainnet or Testnet. In case you’d like to get a bit deeper into the tech details, here’s what you need to know:
Desktop wallet app and CLI wallet
- Testnet binaries will always include “testnet” in the filename, e.g. Beam-Wallet-Testnet-x.y.zzz.dmg
- In case desktop wallets run integrated nodes, make sure that they use different ports. By default, the Mainnet node will use 10005 port, while Testnet will use 11005 port.
- For desktop wallet, the port of the integrated node can be set in the Settings screen.
- Mainnet wallet files and logs are kept in the Beam Wallet folder, Testnet wallet files are in Beam Wallet Testnet folder by default.
- Desktop wallet and download pages on Testnet will have a dark violet background, Mainnet background will remain the same.
Node
- Mainnet node will use 10000 port, while Testnet will use 11000 port by default.
- Mainnet node will reject a connection request from a Testnet wallet, same applies for the Testnet node, rejecting a connection from a Mainnet wallet.
Miner
Currently, the miner is “just” a pure PoW calculation software. Hence, any Beam miner can work with either Mainnet or Testnet node. When configuring the miner-to-node connection, make sure your miner is connected to the network as intended.
agile-atom-1.2.4419
General notes
This is the second maintenance release for Agile Atom which includes user requested features, maintenance optimizations and bug fixes
See also: Upgrading desktop wallet app from a previous version
Features
- [cli wallet] Can import and export addresses (#346)
- [cli wallet] Can specify which UTXO should be sent for any outgoing transaction (#339)
Improvements
- [desktop wallet] Added reasons for failed transactions (#328)
- [node, wallet] Logs rotation mechanism will automatically remove less recent logs (#254)
- [desktop wallet] Improved wallet synchronization indication (#206)
- [desktop wallet, cli wallet] Revised transaction statuses will give a better indication on what’s going on at any time (#19)
- [desktop wallet] Miner removed from the integrated node (#448)
- [node] Use NoFastSync cli option to skip the fast sync when synchronising with the blockchain (#432)
- [cli wallet] Upon creation, the new password should be submitted twice (#137)
- [wallet API] Added JSON RPC over HTTP (#423)
Fixes
- [desktop wallet] Error on missing peer when switching to local node (#271)
- [desktop wallet] Fixed issues when switching back from the lock screen (#347)
- [desktop wallet, cli wallet] Resolved compatibility issues when transaction was wired across specific sets of wallet versions (#416)
- [desktop wallet, cli wallet] Fixed issues when transactions could be stuck because of a height lag when working with a remote node (#340)
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
- 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
agile-atom-1.1.4202 (hotfix)
General notes:
- Hotfix release
- The fix is relevant for all types of nodes (standalone or integrated in the wallet application)
See also: Upgrading from previous version
Features:
- The rare scenario resulted from the untypical (yet valid) wallet usage pattern which caused the nodes to fail to mine the next block after height 25709. The fix was applied to the flaw in the block construction code, which generated a wrong commitment to the UTXO state. #386
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
- 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
agile-atom-1.1.4201 (hotfix)
General notes:
- Hotfix for Agile Atom 1.1.4194
- Upgrading from previous version
Features:
- [desktop wallet, cli wallet] Added rescan function in the Settings screen to sync transaction and UTXO data with the latest information on the blockchain. #345 (Rescan wallet)
Fixes:
- [desktop wallet, cli wallet] Fixed issue with completed transactions becoming Failed and balance invalid on network rollback #367, #368
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
- 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