Topic: Armory 0.94 is out - page 6. (Read 7138 times)
I'm running Windows 10 - how do I get them to you?
I take back what I said earlier about this working. It's not working for me... hanging after the last block...
Been at 0 blocks for about 12 hours now.
Been at 0 blocks for about 12 hours now.
Let's see some logs.
I take back what I said earlier about this working. It's not working for me... hanging after the last block...
Been at 0 blocks for about 12 hours now.
Been at 0 blocks for about 12 hours now.
What file should I use from the old database to recover my transaction and addresses details and comments?
You don't need anything from the old DB. You need your WO wallets from the datadir though. I'll post a new Windows build to fix bitcoind auto management later tonight.
Struggling a bit to update my Windows 10 online machine, but so far so good. Ran into some issues already addressed around here, so here's my experience so far, hope it helps people:
1. Install 0.94
2. Rename your old Armory dir and make another one
3. Boot up Armory, say yes to the agreements, deactivate auto bitcoind management
4. Close Armory
5. Start bitcoind manually, let it sync
6. When it's synced, boot up Armory and let it work.
7. Import your wallet
I got crashes on step 6 (when it finished building the database) and step 7 (after adding my watch-only wallet)
It's now scanning my transaction history.
What file should I use from the old database to recover my transaction and addresses details and comments?
1. Install 0.94
2. Rename your old Armory dir and make another one
3. Boot up Armory, say yes to the agreements, deactivate auto bitcoind management
4. Close Armory
5. Start bitcoind manually, let it sync
6. When it's synced, boot up Armory and let it work.
7. Import your wallet
I got crashes on step 6 (when it finished building the database) and step 7 (after adding my watch-only wallet)
It's now scanning my transaction history.
What file should I use from the old database to recover my transaction and addresses details and comments?
Now, can we get a goatpig donation address? I'd like to test my first 0.94 transaction with it. 
In due time.
Now, can we get a goatpig donation address? I'd like to test my first 0.94 transaction with it.
Ok, so I get problems installing over 0.93.3
No such problems if I simply install the 0.94 package without 0.93.3 previously installed. I suspect that the error is a kind of false positive, i.e. possibly there is no system menu directory in the Debian 8 template used for Qubes (I know that many significant elements, e.g. the main desktop package, are excised from the OS template). Uninstalling 0.94 yields the same xdg error.
Code:
sub-process installed post-removal script exited with error 3: xdg-desktop-menu: No writable system menu directory found
No such problems if I simply install the 0.94 package without 0.93.3 previously installed. I suspect that the error is a kind of false positive, i.e. possibly there is no system menu directory in the Debian 8 template used for Qubes (I know that many significant elements, e.g. the main desktop package, are excised from the OS template). Uninstalling 0.94 yields the same xdg error.
The dpkg script is dated now, it probably needs some work. I'll look at that sometimes before 0.95
I expect it would work in less peculiar configurations/forks of Debian, almost certainly specific to the Qubes template. I should have reported the bug about two releases ago, strictly speaking, it just manifests itself in a much less forgiving way this time around (last time I had to uninstall 0.93.2 to let 0.93.3 install correctly, but even that trick wouldn't work for 93.3 > 94.0)
On a fresh install in a fresh VM (no previous Armory installs), all is well.
Ok, so I get problems installing over 0.93.3
No such problems if I simply install the 0.94 package without 0.93.3 previously installed. I suspect that the error is a kind of false positive, i.e. possibly there is no system menu directory in the Debian 8 template used for Qubes (I know that many significant elements, e.g. the main desktop package, are excised from the OS template). Uninstalling 0.94 yields the same xdg error.
Code:
sub-process installed post-removal script exited with error 3: xdg-desktop-menu: No writable system menu directory found
No such problems if I simply install the 0.94 package without 0.93.3 previously installed. I suspect that the error is a kind of false positive, i.e. possibly there is no system menu directory in the Debian 8 template used for Qubes (I know that many significant elements, e.g. the main desktop package, are excised from the OS template). Uninstalling 0.94 yields the same xdg error.
The dpkg script is dated now, it probably needs some work. I'll look at that sometimes before 0.95
Running fresh copy of .94 and it's purring along.
Thank you again
Thank you again
Ok, so I get problems installing over 0.93.3
No such problems if I simply install the 0.94 package without 0.93.3 previously installed. I suspect that the error is a kind of false positive, i.e. possibly there is no system menu directory in the Debian 8 template used for Qubes (I know that many significant elements, e.g. the main desktop package, are excised from the OS template). Uninstalling 0.94 yields the same xdg error.
Code:
sub-process installed post-removal script exited with error 3: xdg-desktop-menu: No writable system menu directory found
No such problems if I simply install the 0.94 package without 0.93.3 previously installed. I suspect that the error is a kind of false positive, i.e. possibly there is no system menu directory in the Debian 8 template used for Qubes (I know that many significant elements, e.g. the main desktop package, are excised from the OS template). Uninstalling 0.94 yields the same xdg error.
figured it out, just DL & install, loads, but keeps on initializing bitcoin engine ... wallet has been fully synced not it says 99% 4 blocks to go
thx goatpig & others that contributed
did not workout for me, revert back to 0.93.3 any tips appreciated.
TIA
Start BitcoinQt manually, let it sync. Give Armory another database folder (use --dbdir), start it and let it do its thing.
Where/how would one acquire the PGP public key being used for the goatpig Armory releases? The ATI keys are definitely not verfiying the hash txt file.
It should be the one here: https://github.com/goatpig/BitcoinArmory/blob/master/PublicKeys/goatpig-signing-key.asc
Where/how would one acquire the PGP public key being used for the goatpig Armory releases? The ATI keys are definitely not verfiying the hash txt file.
figured it out, just DL & install, loads, but keeps on initializing bitcoin engine ... wallet has been fully synced not it says 99% 4 blocks to go
thx goatpig & others that contributed
did not workout for me, revert back to 0.93.3 any tips appreciated.
TIA
To goatpig and all who contributed: you're warmly appreciated over here at Banks Towers. Big win for the Open Source community, and Bitcoin.
Thank you so much, goatpig!
Thank you very much! This is a pretty substancial update. I'll be upgrading my online machine later today. It will be nice to have a smaller database
Get your builds here:
https://github.com/goatpig/BitcoinArmory/releases/tag/v0.94.0
There won't be offline builds for this release, as nothing was modified on the offline signing part. You can keep on using 0.92-93 to sign transactions created with 0.94.
----------------------
You can find the list of changes in changelog.txt, but here it is too for the good measure:
-------------------------------------
Thank you to all the contributors:
https://github.com/goatpig/BitcoinArmory/graphs/contributors
and the testers:
https://bitcointalksearch.org/topic/094-testing-build-1385530
https://bitcointalk.org/index.php?topic=1372471.40
***************************************************************
Known bugs:
- Will crash on new blocks if there is no wallet loaded
- Sweeping doesn't work
- DB format is different from 0.93, do not use your default settings when upgrading (change the database folder using --dbdir="someotherfolder")
Will be fixed in 0.94.1, stay tuned
https://github.com/goatpig/BitcoinArmory/releases/tag/v0.94.0
There won't be offline builds for this release, as nothing was modified on the offline signing part. You can keep on using 0.92-93 to sign transactions created with 0.94.
----------------------
You can find the list of changes in changelog.txt, but here it is too for the good measure:
Quote
== Added ==
- New database format: DB shrinked from 60GB to sub 200MB, >10x initial setup and startup speed.
- New DB corruption detection and auto repair code. Bad block issues should be mostly gone.
- Detection and GUI flagging of RBF enabled zero confirmation transactions.
- Fixed ZC chain handling and replacement. All ZC spending ZC outputs are now flagged as replaceable,
regardless of TxIn sequence or parent Tx state.
- Added new GUI option to add additional entropy at wallet creation using a deck of cards.
- After the change in lead, all new code is now developed under the MIT license (was AGPL3).
== Removed ==
- No more phone home code. There are no plans to reintroduce any code of that nature.
- As a result, the announce tab code is gone.
- No more torrent code. Seedboxes were hosted by ATI and are now down. Also, IBD improvements in
Core 0.10-12 make this code obsolete.
- As a result of the new light weight DB, the TxHint set has been shrinked to the bare minimum. This means
Armory cannot resolve arbitrary TxHash to data in block anymore. The main symptom is the inability to
resolve TxIn data in the "Transcation Details" dialog. This feature will be reintroduced as part of an
intermediarry DB format inbetween fullnode and supernode.
- No more supernode. Will be reintroduced in a later version.
- New database format: DB shrinked from 60GB to sub 200MB, >10x initial setup and startup speed.
- New DB corruption detection and auto repair code. Bad block issues should be mostly gone.
- Detection and GUI flagging of RBF enabled zero confirmation transactions.
- Fixed ZC chain handling and replacement. All ZC spending ZC outputs are now flagged as replaceable,
regardless of TxIn sequence or parent Tx state.
- Added new GUI option to add additional entropy at wallet creation using a deck of cards.
- After the change in lead, all new code is now developed under the MIT license (was AGPL3).
== Removed ==
- No more phone home code. There are no plans to reintroduce any code of that nature.
- As a result, the announce tab code is gone.
- No more torrent code. Seedboxes were hosted by ATI and are now down. Also, IBD improvements in
Core 0.10-12 make this code obsolete.
- As a result of the new light weight DB, the TxHint set has been shrinked to the bare minimum. This means
Armory cannot resolve arbitrary TxHash to data in block anymore. The main symptom is the inability to
resolve TxIn data in the "Transcation Details" dialog. This feature will be reintroduced as part of an
intermediarry DB format inbetween fullnode and supernode.
- No more supernode. Will be reintroduced in a later version.
-------------------------------------
Thank you to all the contributors:
https://github.com/goatpig/BitcoinArmory/graphs/contributors
and the testers:
https://bitcointalksearch.org/topic/094-testing-build-1385530
https://bitcointalk.org/index.php?topic=1372471.40
***************************************************************
Known bugs:
- Will crash on new blocks if there is no wallet loaded
- Sweeping doesn't work
- DB format is different from 0.93, do not use your default settings when upgrading (change the database folder using --dbdir="someotherfolder")
Will be fixed in 0.94.1, stay tuned
Jump to: