Topic: Armory 0.96 is out - page 7. (Read 13833 times)
Turn on your node RPC.
quite a lot to it, going through it looks like this is where Im getting an error when I try to send after updating to the beta edition
2017-06-07 10:21:52 (INFO) -- ArmoryQt.py:3099 - Sending Tx, 7fc06e76fa56988078b52575391fb98472fbdcd6796567399df6728d739f9d36
2017-06-07 10:21:58 (ERROR) -- Traceback (most recent call last):
File "ui\QtExecuteSignal.pyc", line 31, in methodSlot
File "ArmoryQt.py", line 5036, in handleCppNotification
File "ArmoryQt.py", line 3114, in zcBroadcastError
File "CppBlockUtils.pyc", line 3012, in broadcastThroughRPC
DbErrorMsg: >
Let me know if you need more info, I can post all of today but it's a ton of text.
2017-06-07 10:21:52 (INFO) -- ArmoryQt.py:3099 - Sending Tx, 7fc06e76fa56988078b52575391fb98472fbdcd6796567399df6728d739f9d36
2017-06-07 10:21:58 (ERROR) -- Traceback (most recent call last):
File "ui\QtExecuteSignal.pyc", line 31, in methodSlot
File "ArmoryQt.py", line 5036, in handleCppNotification
File "ArmoryQt.py", line 3114, in zcBroadcastError
File "CppBlockUtils.pyc", line 3012, in broadcastThroughRPC
DbErrorMsg:
Let me know if you need more info, I can post all of today but it's a ton of text.
post armorylog.txt
No, use the testing build for 0.96.1
Just loaded it, clicked send with a higher fee this time and nothing happened after the passphrase window closed. Armory behaving as if I never tried to send any BTC, never had this happen before and it's kinda scary...
No, use the testing build for 0.96.1
If there's change, you should CPFP. Otherwise clear unconfirmed and push again.
It showed as the only transaction, no returning change.
I cleared unconfirmed and am trying again but now getting the "tx timeout" error, guessing I need to rebuild and rescan now?
If there's change, you should CPFP. Otherwise clear unconfirmed and push again.
Chances are you didn't push a proper fee.
Clicked send max, reading now there is a potential bug where Armory puts too small a fee when using the Max button?
Can I just clear unconfirmed and try again or am I risking a double spend and more issues?
Thanks for the quick reply.
Chances are you didn't push a proper fee.
Mine's working great. I sent a transaction and the comment says chained zc. Does that mean anything?
Means your tx is spending an unconfirmed txout.
I don't see any further replies on this issue. I just had the same comment on my transaction and it's still showing unconfirmed after 12 hours when the previous transaction only took about 1 hour. Do I need to do anything to have this transaction work or do I just wait for it to confirm>
Thanks.
I am still using 0.93.3 version for both online and offline wallets of Armory in conjuction with bitcoin core 0.11.2 and would appreciate any recomendations for smooth migration from 0.93.3 to 0.96 on Win 10 machine
I am also a returning user upgrading from 0.93.3. My version of bitcoin core was of a similar vintage. I updated both. When I ran Armory it ran bitcoin-qt for me, but that process quit and Armory didn't seem to notice. From the core logs I found I had to run bitcoin-qt directly and tell it to re-index the database. I'm currently doing this, and it seems to be going OK, but I thought you might want to know the process wasn't as smooth and automatic as one might wish and required this manual intervention.Also, bitcoinarmory.com is not our website. The website is https://btcarmory.com/
Eeek. Bitcoinarmory.com is what a Google search found for me. This post is what made me realise it was old.Still, I'm very pleased to learn Armory is back under active development. I was actually Googling "Armory replacement" and expecting to have to find a new wallet to spend my coins. In other good news, my offline computer still boots.
Thanks!
I'm having trouble verifying the PGP Signature of the 0.96 hash with the Offline Signing Key. I've imported the Offline Signing Key from the Armory website (0x98832223) into Kleopatra , but when I try to verify the signature, I get the message:
"Signed on 2017-04-30 20:20 with unknown certificate 0x8C5211764922589A.
The signature is invalid: No public certificate to verify the signature"
The hash of the installer matches the one provided on the Armory website for the win64.exe file
(fce84bd0964a43a677b1be689e321c562c10a202a35fd052975f3c3536055dd7)
What am I doing wrong?
"Signed on 2017-04-30 20:20 with unknown certificate 0x8C5211764922589A.
The signature is invalid: No public certificate to verify the signature"
The hash of the installer matches the one provided on the Armory website for the win64.exe file
(fce84bd0964a43a677b1be689e321c562c10a202a35fd052975f3c3536055dd7)
What am I doing wrong?
Botched translation patch changes, easy fix on my end. Wait for the next testing build, sometimes this week.
Quote
0.96 is the release that got me past the "offline" phase in which you can't "do" anything such as restore backups... so pleased with that!
There is no such thing. Offline mode is basically what you should be using to restore backups. If you're having issues, post your logs. Use pastebin.
Thanks goatpig, here's the partial armorylog.txt at the time of my first attempt to restore from the fragmented paper backup,
during which the "Restore from fragments" button remained greyed so I couldn't click it after typing in the codes:
2017-05-21 21:54 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-21 21:54 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-21 22:13 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 0
2017-05-21 22:13 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 11718, in dataEnter
File "qtdialogs.pyc", line 11898, in addFragToTable
File "qtdialogs.pyc", line 11803, in checkRestoreParams
AttributeError: 'QString' object has no attribute 'ags'
2017-05-21 22:16 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 1
2017-05-21 22:16 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 11718, in dataEnter
File "qtdialogs.pyc", line 11898, in addFragToTable
File "qtdialogs.pyc", line 11803, in checkRestoreParams
AttributeError: 'QString' object has no attribute 'ags'
2017-05-21 22:25 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 0
2017-05-21 22:25 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 11718, in dataEnter
File "qtdialogs.pyc", line 11898, in addFragToTable
File "qtdialogs.pyc", line 11803, in checkRestoreParams
AttributeError: 'QString' object has no attribute 'ags'
2017-05-21 22:27 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 1
2017-05-21 22:28 (INFO) -- ArmoryQt.py:4876 - New Block! : 467495
2017-05-21 22:28 (INFO) -- ArmoryQt.py:4884 - Current block number: 467495
2017-05-21 22:29 (INFO) -- ArmoryQt.py:4876 - New Block! : 467496
2017-05-21 22:29 (INFO) -- ArmoryQt.py:4884 - Current block number: 467496
2017-05-21 22:31 (INFO) -- qtdialogs.pyc:11716 - Good data from enter_one_frag exec! 1
2017-05-21 22:31 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 11718, in dataEnter
File "qtdialogs.pyc", line 11898, in addFragToTable
File "qtdialogs.pyc", line 11803, in checkRestoreParams
AttributeError: 'QString' object has no attribute 'ags'
2017-05-21 22:33 (INFO) -- ArmoryQt.py:5400 - BDM is safe for clean shutdown
2017-05-21 22:33 (INFO) -- SDM.pyc:457 - Called stopBitcoind
2017-05-21 22:33 (INFO) -- ArmoryQt.py:5414 - Attempting to close the main window!
2017-05-21 22:33 (INFO) -- ArmoryQt.py:5400 - BDM is safe for clean shutdown
2017-05-21 22:33 (INFO) -- SDM.pyc:457 - Called stopBitcoind
2017-05-21 22:33 (INFO) -- SDM.pyc:463 - ...but bitcoind is not running, to be able to stop
2017-05-21 22:33 (INFO) -- ArmoryQt.py:5414 - Attempting to close the main window!
2017-05-21 22:33 (ERROR) -- Traceback (most recent call last):
File "ArmoryQt.py", line 5328, in closeEvent
File "ArmoryQt.py", line 5415, in closeForReal
File "twisted\internet\base.pyc", line 580, in stop
ReactorNotRunning: Can't stop reactor that isn't running.
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1255 -
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1256 -
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1257 -
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-05-21 22:33 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
Thanks for any suggestions!
Quote
0.96 is the release that got me past the "offline" phase in which you can't "do" anything such as restore backups... so pleased with that!
There is no such thing. Offline mode is basically what you should be using to restore backups. If you're having issues, post your logs. Use pastebin.
Binaries:
https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96
changelog
https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt
Notable changes:
1) SegWit
2) RBF & CPFP
3) Translations
4) Compressed public keys
5) Reworked coin control and address tree UI
6) Fleshed out fee and privacy features
Better description on the webpage: https://btcarmory.com/0.96.0-release/
Notes:
Only putting out Windows x64 and Linux x64 builds atm. Offline bundles, RPi and OSX builds for 0.96.1, once I get rid of the twisted/openssl dependency. Eta 1-2 weeks.
Thanks:
achow101 for the support and translation PR, droark for the OSX support and the testers for helping tiddy things up.
Enjoy =)
https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96
changelog
https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt
Notable changes:
1) SegWit
2) RBF & CPFP
3) Translations
4) Compressed public keys
5) Reworked coin control and address tree UI
6) Fleshed out fee and privacy features
Better description on the webpage: https://btcarmory.com/0.96.0-release/
Notes:
Only putting out Windows x64 and Linux x64 builds atm. Offline bundles, RPi and OSX builds for 0.96.1, once I get rid of the twisted/openssl dependency. Eta 1-2 weeks.
Thanks:
achow101 for the support and translation PR, droark for the OSX support and the testers for helping tiddy things up.
Enjoy =)
Happy to see Armory still moving forward, efforts are much appreciated here!
Has anyone successfully restored from a fragmented two of three paper backup with 0.96?
0.96 is the release that got me past the "offline" phase in which you can't "do" anything such as restore backups... so pleased with that!
I'm trying to restore from a 2 of 3 fragmented paper backup, wallet version 1.35c with a SecurePrint code.
I type in my two fragments, but the "Restore from fragments" button remains disabled bottom right.
Am I doing something wrong, or is this a bug with a workaround perhaps?
Getting a little nervous as now running low on options for accessing my funds... A Windows update destroyed the PC holding my bitcoins!
Thanks for any help :-)
- when clicking a wallet, I get four categories (used, unused, change, imported), and inside of those again three categories (p2pkh etc). Only then I actually get to see the individual addresses. I liked it more as it was earlier, with one large list as soon as I open the wallet. Back then, "imported" was a field in the long list, for example. It's not too bad yet, as I only have coins in the "used - p2pkh" category.
I'm not sure what you want to see changed there. Maybe pre-expending a section?Maybe merging all four categories and three subcategories into one large list, with sortable fields? It was more like that when there were only "regular" and "imported" addresses. Of course it wouldn't make sense to have 12 more rows though.
Quote
Quote
- in coin control, I don't see the comment I wrote to an address. This would make coin control close to useless for me. My workaround is to click through the wallet the regular way, mentally choose the inputs I would want to use, and choose the corresponding bitcoin-amount-address in coin control.
That's a miss on my part, will add for .1Cheers,
Ente
- when clicking a wallet, I get four categories (used, unused, change, imported), and inside of those again three categories (p2pkh etc). Only then I actually get to see the individual addresses. I liked it more as it was earlier, with one large list as soon as I open the wallet. Back then, "imported" was a field in the long list, for example. It's not too bad yet, as I only have coins in the "used - p2pkh" category.
I'm not sure what you want to see changed there. Maybe pre-expending a section?
Quote
- in coin control, I don't see the comment I wrote to an address. This would make coin control close to useless for me. My workaround is to click through the wallet the regular way, mentally choose the inputs I would want to use, and choose the corresponding bitcoin-amount-address in coin control.
That's a miss on my part, will add for .1
Jump to: