After 24 hours it got to only January 2017! Still running. This is insane lol. I've got a 2.6GHz Intel Core i7. Is this normal? What a painful experience...
Oh but by all means, let's raise that block limit! Do I need to do steps 3 and 4 if all my coins are unmoved since August 1st? I've got Armory 0.96.2 synced against the BTC blockchain up to today. Can I use my current setup?
You're fine as long as you don't move coins on the BTC side that you have not moved on the BCH side. |
|
|
|
|
Start BitcoinQt manually and let it sync the chain first.
|
|
|
|
paste...bin
pastebin.com edit/ hmmmmm, so I deleted those log files and restarted like you said, and now it is building databases, which it was not doing before
Let it go as long as it can, then report here. If it fails, I need these logs. |
|
|
|
|
1) Delete your logs, start Armory and post the fresh logs.
2) Post dbLog.txt as well
3) Use pastebin to post the logs, not the forum itself.
|
|
|
|
|
It should work out of the box, Armory does not care about Core's DB, just the block data on disk. If there's something that affects Armory, I'll look at it ASAP.
|
|
|
|
|
1) Delete the 2 log files your posted
2) Start BitcoinQt manually, let it sync
3) Start Armory.
4) Describe how far it went and post the fresh logs.
|
|
|
|
Gotcha; that's gonna be a little difficult on an offline machine for a Linux noob like me. Guess I'll use Windows instead - thanks for your help + development time!
I'll fix the CPU fuckery for the next version if you wanna revisit this in ~1 month. |
|
|
|
Ok, I see. If there is a interface that is capable of unicode, it should cover most of the locales supported by Armory.
This is more of a python2 thing than Qt4 really. The solution would be python3, but at this rate might as well do Qt5, which is a task on its own and pretty much at the bottom of the list atm. The wallet used index is increment only, regardless of what address type you request. |
|
|
|
It's a Celeron from 2007.
That's your issue, you can't run my builds cause your CPU lacks the registers for it. You have to build from source against that machine. |
|
|
|
Yes. That's pretty strange. When I'm using german locale settings I can't select addresses via button in the address book, because Armory can't copy it in ASCII character format. As a work-around you can right-klick and copy the address and paste it into the field. When you do this Armory can identify which wallet this address belongs to. So probabbly the clipboard stores non ASCII chars and when you paste them into the text field Armory converts them back into ASCII?
Armory uses the pyQt4 clipboard interface which is pretty buggy actually. I'm guessing that what can't handle non ASCII data. |
|
|
|
Followup: I guess this means the developers could perhaps make a release for Mac. Please.  For 0.96.3. Got a bunch of fixes coming up and SW support for lockboxes, so I'll delay OSX builds until then. |
|
|
|
|
Auto-fee gets the fee/byte dynamically from your node. That would mean you would depend on Core's fee estimate. It's up to you whether you prefer 21.co's or Core's fee estimate.
If you want to default to SegWit addresses, use P2SH-P2WPKH instead of P2SH-P2PK.
|
|
|
|
This issue can be tagged as soleved. Even though I've deinstalled McAfee AV a long time ago this piece of software still hurts my neck. Because I've found out that it isn't enough to just deinstall it. In order to completely remove every "service" that is linked to it, you'll have to download a tool called "MCPR.exe" from the official McAfee website that is able to remove everything that still recides on your PC. This tool can be found under this link: http://us.mcafee.com/apps/supporttools/mcpr/mcpr.aspThat address book issues also had been related to the german locale settings. When you're using it then you're unable to select addresses (especially when using multisig lockboxes). So after switching to English (us) everything works like it should. That would explain why you haven't encountered any of this issues. So the take home is copy to clipboard is botched with non ASCII character sets? As for McAfee, was it messing with your blockchain data or Armory's DB? |
|
|
|
|
In your Armory datadir, grab armorylog.txt and dblog.txt and post these here. Then give me a brief summary of what your issue is and how far you've got.
|
|
|
|
Files: blocks/rev*.dat
Folder: blocks/index
Folder: chainstate
Everything here but the blk files are created on the fly during sync. That stuff will be overwritten if it doesn't match the state of the blk files. For instance, just deleting blocks/blk*.dat files from 930 and onwards, and then launching "./bitcoind -datadir=<new dir with deleted files>" of Bitcoin Classic UAHF gives me "Error loading block database, Do you want to rebuild the block database now?"
Same thing goes with the chainstate db. It's the processed state of the blk files. If you change the blk files, you need to reindex the chainstate. Files: banlist.dat, db.log, debug.log, fee_estimates.dat, mempool.dat, peers.dat, wallet.dat
These are not relate to the blockchain, you can ignore them. |
|
|
|
|
I don't get what you are asking for. You want to know if these settings are acceptable or are you asking what the defaults are?
|
|
|
|
How do I spend the remaining 2.0 BCH? Can I safely follow the same steps except with 2.0 BCH instead of 10.0 BCH
You screwed yourself here. You basically need a fully validated BCH chain now for Armory to be able to see the tx that created that 2 BCH output, for you to be able to now spend it. I'm probably stretching it now, but any chance you could zip and upload somewhere the BCH blk files from 950 until today? I tried running Bitcoin Classic (it's supposed to be able to re-use Bitcoin Core blocks from before Aug 1) but unfortunately it failed... so I may have to download the entire 150 GB chain :S Copy your BTC chain, delete block files up to the fork point and let a BCH node sync against that. |
|
|
|
How do I spend the remaining 2.0 BCH? Can I safely follow the same steps except with 2.0 BCH instead of 10.0 BCH
You screwed yourself here. You basically need a fully validated BCH chain now for Armory to be able to see the tx that created that 2 BCH output, for you to be able to now spend it. |
|
|
|
|
Show Posts
