BadPath: Invalid blockdata path
This is your issue, it doesn't know where to look for your block data. Did you install Core? Have you let it run? Are you trying to use a custom blockchain data path? |
|
|
|
git submodules init
git submodules update
make clean
make distclean
sh autogen.sh
./configure
make -j8
|
|
|
|
|
I see what the issue is. Will fix it for the next testing build.
|
|
|
|
Is there something you want me to test?
Can you compare bitcoind vs manual node stability? How often does the bitcoind method screw up out of 10? |
|
|
|
|
Haven't looked at it yet, try the testing builds for yourself.
|
|
|
|
|
Post armorylog.txt from your offline machine. Use pastebin.
|
|
|
|
|
What version are you using?
|
|
|
|
|
Will look into it before the next testing build.
|
|
|
|
2 Export encrypted wallet file (or import private keys) from offline Bitcoin-qt wallet to the hot (online) Botcoin-qt wallet.
You can offline sign with Core if you're willing to go the extra step. 4 When confirmed in Armory, delete all Bitcoin-qt wallets and paper wallet backups.
Don't delete the old wallet. Always keep a copy of your old wallets, you could need these keys in 10/20/30 years. Issue receiving address from the offline Armory wallet.
...
Make a paper wallet backup of Armory private keys.
Semi right steps, wrong order. This is the proper way to go about it: 1) Create wallet on an air gapped, never been online machine.
2) Create backup of said wallet.
3) Test the backup.
4) Test the backup again
5) Once more for the good measure
6.a) Create WO wallet and export it to your online machine, then sync it with the network. Grab the address from your WO wallet. This prevents address reuse if you intent to give the wallet some traffic, while letting you keep an eye on your funds.
or
6.b) If this is a long term cold storage wallet and you don't intent to sync it for a while, grab the receive address straight from the offline wallet.
7) Did I mention testing your backup?
|
|
|
|
|
Start Armory without Core running, what do you get?
|
|
|
|
Should have worked that one out myself  I really like git, but the submodule stuff is so user-unfriendly that I decided to do something else in one of my own projects (a bit more work for me, but people who clone it have a chance). That turned out to be much worse than what I had expected. I'll prolly move to git subtree instead. |
|
|
|
|
It's easy enough. Where do you get stuck to begin with?
|
|
|
|
|
Delete C:\Users\Bernd\AppData\Roaming\Armory\databases. Also upgrade to the testing builds for 0.96.1
|
|
|
|
|
Yeah so you are some 350k blocks behind. Start Bitcoin-qt. How many blocks does it show?
|
|
|
|
Hi. I have used Armory for years, and I really like it.! Thanks for maintaining it The latest builds (since 0.96, and including this latest 0.96.02 test build), do not output the comments when the transaction lists are exported via the "Export Transactions" to CSV menu. For instance: 2014-Apr-21 12:58pm,9eb...,738339,3AznXg8eo,MyWallet (Watch),0.01,,, 0.01000000, 0.01000000,"" In previous versions, this was output as: 2014-Apr-21 12:58pm,9eb...,738339,3AznXg8eo,MyWallet (Watch),0.01,,, 0.01000000, 0.01000000,"InputTest" So you can see that the comment (which is still visible in the Armory UI) is missing from the Exported Transactions. Can you advise / fix? I really need this comment information to maintain my records of transactions... Thanks Dave I can't reproduce. Are the missing comments address or tx comments? Address comments are created in the wallet properties dialog, tx comments are made in the main ledger. |
|
|
|
|
Show Posts
