|
Bumping for the new testing builds.
|
|
|
|
|
Did you init the git submodules?
|
|
|
|
|
A proper cold storage setup is preferable to a HW wallet. These are better suited for daily spending purposes.
You can't import your Multibit seed in Armory as is. If you want to migrate your funds to Armory, should create a wallet in Armory, grab a recipient address and send your coins to that from Multibit. You can also reveal the private keys in Multibit and sweep them in Armory, but that's a whole let more prone to error.
You can run the blockchain data in an external drive. If you have another machine, you can set the node + database on that machine and run the client on your regular PC if you feel so inclined. Your biggest limitation is bootstrapping the node, which demands a lot of bandwidth and disk space.
As for August 1st, all pre fork coins will be present on both side of the fork. Anything you spend past that point can and will be mimicked on both sides, unless you taint your coins to be valid on only a given side. If you are dead set on which side you want to be in, you can go down that path. Otherwise you are better off just sitting it out.
|
|
|
|
I can now add BTC to that wallet, and Armory backup will still be valid, right?
Yes. |
|
|
|
Do I have to run a full node? Got 5gb left.
I'm trying to retrieve a seed from a multibit HD wallet that I've been using since 2 years... Dunno what happened, but the password doesn't work.
Anyway just money ey!
Armory can't make sense of that seed. From what I'm being told, no other wallet currently can besides Multibit itself. And yes, Armory requires a full node. |
|
|
|
Don't see this posted yet. Windows 7 Pro new install 64 bit, plenty of HD space. Installed Bitcoin Core 14.1, fully synched chain; installed Armory 0.96. Run Armory in Admin mode, starts building database. Gets however far, errors out during "parsed block file #XXX). Most recent:
ERROR – 14973716-40..\SocketObject.cpp:134: (..\SocketObject.cpp) :285) POLLERR in writeToSocket
-ERROR – 1497371641: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038
-ERROR – 1497371641: (..\BitcoinidP2P.cppL1027( caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread
-INFO - 1497371641: (..\BitcoindP2P.cpp969) Disconnected from Bitcoin node
Appears to keep losing connection with Bicoin Core database. I reset Armory to factory settings deleting Armory database and settings but keeping Bitcoin Core database, restart Armory. Keeps getting error at different level of database build. Directory paths are correct. Is there another option besides deleting the entire Bitcoin Core database, uninstalling both programs, deleting all appdata for both programs and starting the blockchain build all over in Bitcoin Core and burning another 10 days? I previously also tried building the chain with only Armory 0.96 installed without Bitcoin Core and it would not even start the database build.
This is fixed in the testing builds. |
|
|
|
That's for 0.97 Now, I need to change the "Path" that is wrong apparently!
Which path? You can set the blockchain path with --satoshi-datadir, the db path with --dbdir. You can create armorydb.conf in your datadir's folder and set the args there if you don't want to bother with them every run. |
|
|
|
|
Make sure there isn't an instance of ArmoryDB running. Then start the DB yourself with your command line arg.
|
|
|
|
|
Your blockchain data is incomplete and you are not running a bitcoin node.
|
|
|
|
How are you trying to build from source without setting up the git to get the source?
You publish the source code together with the binaries on your release pages. (Could it be that the submodules are missing there?) I don't publish that, git does it automatically. Maybe that's the issue... How are you trying to build from source without setting up the git to get the source?
Pick a top folder for the repo then do the following: Then follow the build instructions from within that folder. |
|
|
|
|
How are you trying to build from source without setting up the git to get the source?
|
|
|
|
Can I now safely delete the old wallet files from my online machine? (I'm still running an older Armory with the old wallet format on my offline machine.)
No you can't, these are still the main wallets. The new ones are only proxies for the new scripts types and SegWit. They are only WO so there's no point in characterizing them. You can delete the lmdb wallets all you want however, but they'll be recreated on each start if missing. |
|
|
|
BTW, how to clear armory's log?
Delete armorylog.txt and dbLog.txt in your Armory datadir.
|
|
|
|
|
Try with 0.96.0.2 and post armorylog.txt as well. Use pastebin.
|
|
|
|
|
This is an OSX specific bug, I'd have to look at it directly on that platform. Maybe you can try to narrow down the issue.
|
|
|
|
|
Show your log files in full. Use pastebin.
|
|
|
|
|
Show Posts
