Skip to content

Commit

Permalink
update changelog and bump version
Browse files Browse the repository at this point in the history
  • Loading branch information
goatpig committed Nov 15, 2018
1 parent 1682b19 commit eaa2cb6
Show file tree
Hide file tree
Showing 4 changed files with 30 additions and 3 deletions.
2 changes: 1 addition & 1 deletion armoryengine/ArmoryUtils.py
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@
LEVELDB_HEADERS = 'leveldb_headers'

# Version Numbers
BTCARMORY_VERSION = (0, 96, 4, 0) # (Major, Minor, Bugfix, AutoIncrement)
BTCARMORY_VERSION = (0, 96, 4, 99) # (Major, Minor, Bugfix, AutoIncrement)
PYBTCWALLET_VERSION = (1, 35, 0, 0) # (Major, Minor, Bugfix, AutoIncrement)

# ARMORY_DONATION_ADDR = '1ArmoryXcfq7TnCSuZa9fQjRYwJ4bkRKfv'
Expand Down
27 changes: 27 additions & 0 deletions changelog.txt
Original file line number Diff line number Diff line change
@@ -1,3 +1,30 @@
v0.96.5
== Added ==
- You can now set the database path from the Settings menu.
- You can now spend to bech32 addresses.
- Added support for satoshi-port CLI argument in ArmoryDB.

== Fixes ==
- Improved bitcoind path detection.
- Properly carry thread-count and ram-usage command line arguments from client to automated db process.
- Custom paths set in the GUI will now properly overrule custom paths from armoryqt.conf.
- Fixed spending from lockboxes.
- Fixed deleting lockboxes.
- Fixed Simulfund promisory note creation and signing.
- Fixed preview dialog for unconfirmed transactions.
- Fixed previewing unsigned transactions in offline mode.
- Fixed SecurePrint decryption on Windows.

- Recent updates to the MSVC compiler resulted in invalid decryption of AES-CBC packets. This issue only
affects the decryption of SecurePrint encrypted backups. Encryption still operates as expected, no
SecurePrint backups created with the incriminated builds are faulty. Wallets are not concerned, as they
use AES-CFB.

The solution was to turn off all optimizations in MSVC when buidling CryptoPP. This may impact DB boostrapping
performance.

This issue affects all Windows builds of 0.96.4.

v0.96.4, released March 30th 2018
== Added ==
- Updated fee estimate query from node to improve estimateSmartFee call introduced in Bitcoin Core 0.15.
Expand Down
2 changes: 1 addition & 1 deletion configure.ac
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
AC_PREREQ(2.60)
AC_INIT([BitcoinArmory], [0.96.4], [[email protected]])
AC_INIT([BitcoinArmory], [0.96.4.99], [[email protected]])

AM_INIT_AUTOMAKE([1.10 subdir-objects foreign -Wall -Werror])

Expand Down
2 changes: 1 addition & 1 deletion cppForSwig/BitcoinP2P.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -936,7 +936,7 @@ void BitcoinP2P::connectLoop(void)
version.setVersionHeaderIPv4(70012, services, timestamp,
node_addr_, clientsocketaddr);

version.userAgent_ = "Armory:0.96.4";
version.userAgent_ = "Armory:0.96.4.99";
version.startHeight_ = -1;

sendMessage(move(version));
Expand Down

0 comments on commit eaa2cb6

Please sign in to comment.