The new segwit-script address type P2SH-P2WPKH is still grayed-out in the settings dialoge window. Is this hardcoded or does ArmoryQt check for segwit activation?
Hardcoded atm, you can only use it on the testnet. Will enable in 0.96.2. |
|
|
|
The second point for which I'll provide a pastebin link, is I can't use the Bump Fee function.
It would appear there's not enough funds left on your output to support a fee bump. You'll have to do this manually. |
|
|
|
Is there a way to pre generate those addresses already in Armory?
Would be nice to have them already in our DB and enable them once Segwit is activated.
All public keys in your wallet are already instantiated under all possible script variations in the DB. |
|
|
|
Well then your issue is 2 fold: Your node tends to kick you out, and you don't have the RPC enabled. Find your bitoin.conf file (create it if it's missing) in the Bitcoin datadir, and add these 2 lines in there: addnode=127.0.0.1
server=1
|
|
|
|
OK, it worked over night. Now I am actually seeing one confirmation for a tx which was done a few days after the split. I think I have to remove more block data still and remove it... Quite strange, so split must be well before file 949.... I may have to experiment a little with that then....
If your coins have not moved months prior to the split, you can afford to overshoot. Actually, you are better off overshooting and reintroducing files later, as the DB can append forward but needs rescanned backwards. |
|
|
|
It then seems to do pretty much nothing.
Your DB shows it's scanning. The wallet check runs in parallel and is unrelated to the DB or the init process. |
|
|
|
Sent a PM
Did you modify your wallets offline before going back online? Looks like it's scanning your wallets atm, and 0.96.2 RC2 has this issue where it won't show DB progress under certain circumstances. I've fixed that but I haven't pushed the fix in a build yet. At any rate, confirm by starting ArmoryDB from the command line, you should see it scanning. Also you can get rid of thread-count=1, you're just gimping the scan unnecessarily. |
|
|
|
|
Start BitcoinQt with -disablewallet. Then start Armory the usual way. Once you get a new block, check the peer tab on BitcoinQt, do you see an instance of ArmoryDB connected?
|
|
|
|
Using that new cert works. I didn't realize there was a company change. I hadn't kept up with the development.
Another question... For 0.96.1, does it not give you the option to secure download the bitcoin client within armory?
There's no other company, just me and a couple other volunteers basically. The secure download feature ran on the ATI servers (former maintainer LLC). They discontinued this and I don't have access to the signing keys so the chain of updates would have been broken with my taking over anyways. As for the code itself, it involved a lot of phoning home, so I got rid of it as a whole. |
|
|
|
Yes I did, should I try to put Armory and Bitcoin into the D: root directory?
No, that's irrelevant, just double checking. |
|
|
|
It's an either or thing kinda, you either use the shortcut cli option or the .conf. The cli option overrides the .confs. At any rate, this pathing is very odd, did you create that folder manually? |
|
|
|
Geeze, its finally there. Thank you so much for your help. Sorry for any inconveniences due to stupidity  So, I turned off auto bitcoind, how do I proceed in the future? Just turn on Bitcoin Core before I start Armory? Or turn auto bitcoind back on, let it sync then turn off/restart again? Cheers again for the help! Edit: All good, I turned auto bitcond on again and everything seems to be fine now. Thanks guys, much appreciated!  Your autobitcoind does work atm as it doesn't know where to find bitcoind. You'd have to either give it the path your binary folder or disable it or you'll run into more issues. |
|
|
|
|
Turn off auto bitcoind in Files > Settings and restart Armory.
|
|
|
|
|
What's the issue exactly?
|
|
|
|
@HPC:
Correct, block count is now increasing. Just the scanning thing at the top seems to be stuck. Would a balance rescan help?
No, that doesn't affect the chain length. Post a fresh log. |
|
|
|
|
Show Posts
