How are the new builds coming? Itching to get started using SegWit, and compiling for windows is a pain.
Sometimes today maybe. Creating offline packages is a pain.
Topic: 0.96.2 RC2 (Read 5398 times)
Sometimes today maybe. Creating offline packages is a pain.
How are the new builds coming? Itching to get started using SegWit, and compiling for windows is a pain.
Doing the builds atm.
awesome thx! Armory is (at least for me) most trusted wallet for years! Always on top of The game!
Doing the builds atm.
The new segwit-script address type P2SH-P2WPKH is still grayed-out in the settings dialoge window. Is this hardcoded or does ArmoryQt check for segwit activation?
Hardcoded atm, you can only use it on the testnet. Will enable in 0.96.2.
any ETA? days/weeks/months? thanks a lot
Best stability and cpu usage so far. Used to have rare random crashes every few days. And even rarer, sometimes the UI'd lock up in the background eating up a full core. Never got why it was happening but it's no longer happening.
OS: Windows 10 Pro x64 Creators Update + all updates.
OS: Windows 10 Pro x64 Creators Update + all updates.
Couldn't agree more. 0.96.1.x had frozen some times while closing but the latest 0.96.2 works as it should be.
The new segwit-script address type P2SH-P2WPKH is still grayed-out in the settings dialoge window. Is this hardcoded or does ArmoryQt check for segwit activation?
Hardcoded atm, you can only use it on the testnet. Will enable in 0.96.2.
The new segwit-script address type P2SH-P2WPKH is still grayed-out in the settings dialoge window. Is this hardcoded or does ArmoryQt check for segwit activation?
Is this the only version working with BCH chain?
Yes.Thank you!
Is this the only version working with BCH chain?
Yes.
Is this the only version working with BCH chain?
Best stability and cpu usage so far. Used to have rare random crashes every few days. And even rarer, sometimes the UI'd lock up in the background eating up a full core. Never got why it was happening but it's no longer happening.
OS: Windows 10 Pro x64 Creators Update + all updates.
OS: Windows 10 Pro x64 Creators Update + all updates.
Any chance for a 32-bit Debian-compatible binary?
Build it yourself, fairly easy.
Any chance for a 32-bit Debian-compatible binary?
The above mentioned bug probably isn't a bug. Because when you are too many blocks behind, Armory seems to wait until it is nearly fully synced before it starts to initialize, now. This is good, because it can not happen anymore that Armory is loaded and Bitcoin Core isn't synched, so when you broadcast a transaction it gets rejected. But some kind of label would be nice, that indicates if Armory is waiting for Core.
If you have the RPC enabled, Armory will check the node status through that before initializing its DB, as you guessed. The progress GUI for that is borked however. I'll go over it at some point.
Bug Report
Subject: ArmoryDB loading issue
Priority level: Normal
Bug description:
ArmoryDB runs in this testing version into a state, where it doesn't load it's own database during startup. Although no exceptions are thrown and it has worked well for the first couple of times. Sometimes there is also a RPC connection loop, that causes Armory to push multiple "connection to bitcoin node established" notifications.
Work-around:
I have downgraded to Armory 0.96.1, started ArmoryQt again, quitted after initialization and upgraded again to Armory 0.96.2-RC1-testing and now Armory can load it's database again.
Armory's dbLog.txt
Subject: ArmoryDB loading issue
Priority level: Normal
Bug description:
ArmoryDB runs in this testing version into a state, where it doesn't load it's own database during startup. Although no exceptions are thrown and it has worked well for the first couple of times. Sometimes there is also a RPC connection loop, that causes Armory to push multiple "connection to bitcoin node established" notifications.
Work-around:
I have downgraded to Armory 0.96.1, started ArmoryQt again, quitted after initialization and upgraded again to Armory 0.96.2-RC1-testing and now Armory can load it's database again.
Armory's dbLog.txt
Code:
Log file opened at 18:10:05.000: C:\Users\***\AppData\Roaming\ArmoryBTC/dbLog.txt
-INFO - 18:10:05.000: (..\main.cpp:32) Running on 4 threads
-INFO - 18:10:05.000: (..\main.cpp:33) Ram usage level: 4
-INFO - 18:10:05.000: (..\BlockUtils.cpp:914) blkfile dir: C:\Users\***\AppData\Roaming\BitcoinCore\blocks
-INFO - 18:10:05.000: (..\BlockUtils.cpp:915) lmdb dir: C:\Users\***\AppData\Roaming\ArmoryBTC\databases
-INFO - 18:10:05.000: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 18:10:05.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:257) Listening on port 54717
-INFO - 18:10:06.047: (..\BDM_Server.cpp:1114) registered bdv: ddbfb02bcbb53ceb27f0
-INFO - 18:11:00.187: (..\nodeRPC.cpp:57) RPC connection established
-INFO - 18:11:00.187: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 18:13:46.859: (..\nodeRPC.cpp:415) Bitcoin server stopping
-ERROR - 18:13:57.906: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO - 18:13:57.906: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-INFO - 18:10:05.000: (..\main.cpp:32) Running on 4 threads
-INFO - 18:10:05.000: (..\main.cpp:33) Ram usage level: 4
-INFO - 18:10:05.000: (..\BlockUtils.cpp:914) blkfile dir: C:\Users\***\AppData\Roaming\BitcoinCore\blocks
-INFO - 18:10:05.000: (..\BlockUtils.cpp:915) lmdb dir: C:\Users\***\AppData\Roaming\ArmoryBTC\databases
-INFO - 18:10:05.000: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 18:10:05.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:257) Listening on port 54717
-INFO - 18:10:06.047: (..\BDM_Server.cpp:1114) registered bdv: ddbfb02bcbb53ceb27f0
-INFO - 18:11:00.187: (..\nodeRPC.cpp:57) RPC connection established
-INFO - 18:11:00.187: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 18:13:46.859: (..\nodeRPC.cpp:415) Bitcoin server stopping
-ERROR - 18:13:57.906: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO - 18:13:57.906: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
The above mentioned bug probably isn't a bug. Because when you are too many blocks behind, Armory seems to wait until it is nearly fully synced before it starts to initialize, now. This is good, because it can not happen anymore that Armory is loaded and Bitcoin Core isn't synched, so when you broadcast a transaction it gets rejected. But some kind of label would be nice, that indicates if Armory is waiting for Core.
That's for supernode only, min req for fullnode is ~1GB RAM and 2c/4t on a HDD. It'll be slow, but it'll work.
Just create a DB with --db-type=DB_SUPER
Quote
rough explanation of its resource requirements?
minimum reqs are:
1.5~2x blockchain size of storage space
8+ Cores
1000MB/s read and 300MB/s sequential disk I/O
32GB RAM
8+ Cores
Are they real cores or do you mean 4 cores with hyper-threading?Are the requirements lower if I will not implement DB_SUPER mode? I have only 16 RAM and 4 core wth hyper-threading.
I'm seeing it now on another wallet. Were you using P2PKH or P2SH addresses?
P2PKH. I didn't touch the address type defaults. I cannot reproduce this. Try to rescan your DB.
Yep, that fixed it, thank you. Sorry for the noise.I'm seeing it now on another wallet. Were you using P2PKH or P2SH addresses?
I cannot reproduce this. Try to rescan your DB.
Yep, that fixed it, thank you. Sorry for the noise. I'm new to Armory, so it's quite likely I'm mistaken, but the Wallet Properties of my OW (as seen from the online box) seem strange to me:
* It shows None in the category Addresses Used, even though there are multiple addresses that have received and sent -- doesn't get more used than that. The addresses in question are shown under Unused Addresses. They do have the correct Address Activity and balance in Address Information, and the total for Addresses Used is plausible.
* Tx Count is shown as 0 for any and all listed addresses, both in Wallet Properties and Address Information.
I could've sworn this used to work (in 0.96.1, at least).
* It shows None in the category Addresses Used, even though there are multiple addresses that have received and sent -- doesn't get more used than that. The addresses in question are shown under Unused Addresses. They do have the correct Address Activity and balance in Address Information, and the total for Addresses Used is plausible.
* Tx Count is shown as 0 for any and all listed addresses, both in Wallet Properties and Address Information.
I could've sworn this used to work (in 0.96.1, at least).
I cannot reproduce this. Try to rescan your DB.
I'm new to Armory, so it's quite likely I'm mistaken, but the Wallet Properties of my OW (as seen from the online box) seem strange to me:
* It shows None in the category Addresses Used, even though there are multiple addresses that have received and sent -- doesn't get more used than that. The addresses in question are shown under Unused Addresses. They do have the correct Address Activity and balance in Address Information, and the total for Addresses Used is plausible.
* Tx Count is shown as 0 for any and all listed addresses, both in Wallet Properties and Address Information.
I could've sworn this used to work (in 0.96.1, at least).
* It shows None in the category Addresses Used, even though there are multiple addresses that have received and sent -- doesn't get more used than that. The addresses in question are shown under Unused Addresses. They do have the correct Address Activity and balance in Address Information, and the total for Addresses Used is plausible.
* Tx Count is shown as 0 for any and all listed addresses, both in Wallet Properties and Address Information.
I could've sworn this used to work (in 0.96.1, at least).
I had to spend a bunch of time on the BCH miner and I have very little time to dedicate to 0.96.2 for the next 2 weeks or so. Keep the bug reports coming, I'll be keeping an eye out for them.
That's not a problem. You really don't have to hurry, there aren't any major issues so far that I've recognized.
I had to spend a bunch of time on the BCH miner and I have very little time to dedicate to 0.96.2 for the next 2 weeks or so. Keep the bug reports coming, I'll be keeping an eye out for them.
Bug Report
Subject: ArmoryDB loading issue
Priority level: Normal
Bug description:
ArmoryDB runs in this testing version into a state, where it doesn't load it's own database during startup. Although no exceptions are thrown and it has worked well for the first couple of times. Sometimes there is also a RPC connection loop, that causes Armory to push multiple "connection to bitcoin node established" notifications.
Work-around:
I have downgraded to Armory 0.96.1, started ArmoryQt again, quitted after initialization and upgraded again to Armory 0.96.2-RC1-testing and now Armory can load it's database again.
Armory's dbLog.txt
Subject: ArmoryDB loading issue
Priority level: Normal
Bug description:
ArmoryDB runs in this testing version into a state, where it doesn't load it's own database during startup. Although no exceptions are thrown and it has worked well for the first couple of times. Sometimes there is also a RPC connection loop, that causes Armory to push multiple "connection to bitcoin node established" notifications.
Work-around:
I have downgraded to Armory 0.96.1, started ArmoryQt again, quitted after initialization and upgraded again to Armory 0.96.2-RC1-testing and now Armory can load it's database again.
Armory's dbLog.txt
Code:
Log file opened at 18:10:05.000: C:\Users\***\AppData\Roaming\ArmoryBTC/dbLog.txt
-INFO - 18:10:05.000: (..\main.cpp:32) Running on 4 threads
-INFO - 18:10:05.000: (..\main.cpp:33) Ram usage level: 4
-INFO - 18:10:05.000: (..\BlockUtils.cpp:914) blkfile dir: C:\Users\***\AppData\Roaming\BitcoinCore\blocks
-INFO - 18:10:05.000: (..\BlockUtils.cpp:915) lmdb dir: C:\Users\***\AppData\Roaming\ArmoryBTC\databases
-INFO - 18:10:05.000: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 18:10:05.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:257) Listening on port 54717
-INFO - 18:10:06.047: (..\BDM_Server.cpp:1114) registered bdv: ddbfb02bcbb53ceb27f0
-INFO - 18:11:00.187: (..\nodeRPC.cpp:57) RPC connection established
-INFO - 18:11:00.187: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 18:13:46.859: (..\nodeRPC.cpp:415) Bitcoin server stopping
-ERROR - 18:13:57.906: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO - 18:13:57.906: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-INFO - 18:10:05.000: (..\main.cpp:32) Running on 4 threads
-INFO - 18:10:05.000: (..\main.cpp:33) Ram usage level: 4
-INFO - 18:10:05.000: (..\BlockUtils.cpp:914) blkfile dir: C:\Users\***\AppData\Roaming\BitcoinCore\blocks
-INFO - 18:10:05.000: (..\BlockUtils.cpp:915) lmdb dir: C:\Users\***\AppData\Roaming\ArmoryBTC\databases
-INFO - 18:10:05.000: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 18:10:05.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:257) Listening on port 54717
-INFO - 18:10:06.047: (..\BDM_Server.cpp:1114) registered bdv: ddbfb02bcbb53ceb27f0
-INFO - 18:11:00.187: (..\nodeRPC.cpp:57) RPC connection established
-INFO - 18:11:00.187: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 18:13:46.859: (..\nodeRPC.cpp:415) Bitcoin server stopping
-ERROR - 18:13:57.906: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO - 18:13:57.906: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
minimum reqs are:
1.5~2x blockchain size of storage space
8+ Cores
1000MB/s read and 300MB/s sequential disk I/O
32GB RAM
1.5~2x blockchain size of storage space
8+ Cores
1000MB/s read and 300MB/s sequential disk I/O
32GB RAM
With some pretty substantial VM re-allocation and re-partitioning, I've got one machine that _mostly_ meets that.
I presume the advantage of this is that you can throw any wallet or any private key at it and not have to wait to re-scan the blockchain to find any txs?
Quote
Can you elaborate on "Supernode DB mode"?
Tracks history for all addresses on chain.
Quote
how to enable and configure it
Just create a DB with --db-type=DB_SUPER
Quote
rough explanation of its resource requirements?
minimum reqs are:
1.5~2x blockchain size of storage space
8+ Cores
1000MB/s read and 300MB/s sequential disk I/O
32GB RAM
Can you elaborate on "Supernode DB mode"? What it does, how to enable and configure it, and a rough explanation of its resource requirements?
Time to test 0.96.2:
https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.1.2
Changes:
BCH miner howto: https://bitcointalksearch.org/topic/using-armory-on-the-bch-chain-2070058
Happy testing =)
https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.1.2
Changes:
Quote
v0.96.2
== Added ==
- Improved DB scan speed (~80% faster) and stability.
- Reduced DB memory usage (~20% less).
- Supernode DB mode. This isn't optimized for consumer grade computers, use at your own risk.
- The MAX button in the Send dialog has been changed to a checkbox, effect is now binding.
Maximum value will be calculated on any change.
- You can now create OP_RETURN outputs from the Send dialog. This feature is only available in Expert mode.
- You can now pick the signer of your choosing in Expert mode.
- Added BCH on top of the legacy and 0.96 C++ signer.
== Fixed ==
- Fixed benchmark timers on POSIX systems.
- Fixed several Linux build configure bugs.
- Properly update RPC state in GUI on connect/disconnect events.
== Removed ==
- Removed armoryd from the repository. armoryd was moved to its own repository (https://github.com/goatpig/armoryd)
== Added ==
- Improved DB scan speed (~80% faster) and stability.
- Reduced DB memory usage (~20% less).
- Supernode DB mode. This isn't optimized for consumer grade computers, use at your own risk.
- The MAX button in the Send dialog has been changed to a checkbox, effect is now binding.
Maximum value will be calculated on any change.
- You can now create OP_RETURN outputs from the Send dialog. This feature is only available in Expert mode.
- You can now pick the signer of your choosing in Expert mode.
- Added BCH on top of the legacy and 0.96 C++ signer.
== Fixed ==
- Fixed benchmark timers on POSIX systems.
- Fixed several Linux build configure bugs.
- Properly update RPC state in GUI on connect/disconnect events.
== Removed ==
- Removed armoryd from the repository. armoryd was moved to its own repository (https://github.com/goatpig/armoryd)
BCH miner howto: https://bitcointalksearch.org/topic/using-armory-on-the-bch-chain-2070058
Happy testing =)
Jump to: