Armory 0.96.5

[Aurik]

Armory 0.97: Is this project still being worked on? In this topics first post the eta is Q2 '19.
Can you give some update and background infos about it?

[Ethorsen]

I also wish we can see an update to Armory sooner or later.  I've been sticking with this wallet since I started dealing BTC in early 2013.   It would be nice to continue using it on the long term.

[goatpig]

Can you give some update and background infos about it?

Sometimes this summer. New wallet code is done, migration to LWS + socket encryption is done. Main blocker atm is the migration from p2/qt4 to py3/qt5. Then I need some extra work for the BIP32 wallet GUI. I do have a day job though.

[Masterswarm]

I have an old machine which is still running 0.92!  It runs on my dad's computer so I quite literally haven't toucehd it in years.  Still has a fraction of a BTC on it too!

[giszmo]

What happened to the website? https://btcarmory.com/ down? Git repo has no updates in years?

I'm expanding https://WalletScrutiny.com to Linux wallets and in terms of binary distribution this would be a "defunct" wallet?

[goatpig]

What happened to the website? https://btcarmory.com/ down? Git repo has no updates in years?

I'm expanding https://WalletScrutiny.com to Linux wallets and in terms of binary distribution this would be a "defunct" wallet?

Owned by the former maintainers. I use my repo (goatpig/BitcoinArmory on github). It has a gh-pages branch for btcarmory.com in there. You can look at development in the dev branch. Master only receives signed tags for releases.

[btcArmory user]

I am reindexing bitcoin core from command line on Windows 10.0. Bitcoin Core 0.20.1
The counters are incrementing on lines 2 - 4, but they are static on line 1 of the overview tab.
Number of blocks left: Unknown. Syncing Headers (524490, 79.5%)...

The lines containing date and time, progress, and progress increase per hour are all incrementing or changing.

Is the syncing continuing, or do I need to stop this process and try something else?

[HCP]

I think it's caused by the reindex option... What it is currently doing is going through what you currently have stored on disk (this is why you see progress changing as it reindexs the blocks on disk)... once it finishes that process, it'll then start looking for new blocks after 524490 (at which point the "syncing headers" values should change).

[btcArmory user]

The re-indexing process stopped at 53.29%
Sat
May 26 7:39:09  2018

2 years and 32 weeks behind

It still lists the same values at the top: Syncing Headers (524490, 79.5%)

Which way to go on this? Delete db files and rebuild the database in bitcoin core? It took over 3 weeks to get to the stopping point re-indexing headers.

[HCP]

The only things I can think of that would cause this are:

1. Corrupt data on disk... the easiest (but "longest") fix is to simply delete all the bitcoin core block data and start syncing from scratch again.
2. Out of hard disk space... Bitcoin Core will simply stop syncing if it runs out of harddrive space.
3. Some sort of hardware issue causing data corruption.

So, do you actually have enough free space on the disk for the blockchain? It's well over 350+gigs on total storage now...


What do you see at the end of the debug.log file when Bitcoin Core stops syncing? Any obvious errors? It would be helpful if you posted the last couple of hundred of lines from debug.log (use pastebin.com to avoid post length limits)

[btcArmory user]

Hard Disk
used:  187 GB
free:  278 GB

https://pastebin.com/ciVY7EUW

[btcArmory user]

Could the issue be caused by an intermittent failure in the Internet connection? No new blocks are available?

[HCP]

Something odd going on with your Bitcoin Core...

It got as far as getting the new block at 524491, and then just stopped getting new blocks...

2021-01-09T14:55:25Z UpdateTip: new best=0000000000000000000b6ce14cc39740a42d817ba68382075927555cd707f3e1 height=524491 version=0x20000000 log2_work=88.888701 tx=318642673 date='2018-05-26T14:39:09Z' progress=0.532869 cache=410.4MiB(2884728txo)
2021-01-09T14:55:25Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there
2021-01-09T15:32:10Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2205 seconds ago)
...
2021-01-12T08:53:05Z Potential stale tip detected, will try using extra outbound peer (last tip update: 237460 seconds ago)

Are you actually connected? What is the networkactive value and how many connections do you see if you do:

Code:

bitcoin-cli getnetworkinfo

Or look at the "Window -> Information" screen in Bitcoin Core GUI?

[btcArmory user]

It reached block 524491 previously. I started re-indexing headers about 3 weeks ago. After that, it stopped at a lower percentage, but both values were still displayed in the dialog box.

These two lines were the current status:
The re-indexing process stopped at 53.29%
Sat
May 26 7:39:09  2018

2 years and 32 weeks behind

They were displayed below the block 524491 entry. At the moment, I am updating Windows, having run performance tuning on the system. Windows performance was extremely sluggish.

[btcArmory user]

I currently have 1 active connection to the bitcoin network. That happened after I dropped my personal firewall.
Is there a way to enter IP addresses for bitcoin nodes into the bitcoin.conf file?

[HCP]

I currently have 1 active connection to the bitcoin network. That happened after I dropped my personal firewall.
Is there a way to enter IP addresses for bitcoin nodes into the bitcoin.conf file?

yeah... you can use the addnode command... either with bitcoin-cli, in the console in Bitcoin Core GUI or in the bitcoin.conf file.

As per the examples on the bitcoin github:

Code:

# Use as many addnode= settings as you like to connect to specific peers
addnode=69.164.218.197
addnode=10.0.0.2:8333

[btcArmory user]

Method not found (code -32601)

Attempted addnode and connect commands in the console

[HCP]

Attempted addnode and connect commands in the console

Ahhh ok, you asked about bitcoin.conf... the previous example was bitcoin.conf option.

In the console, the command syntax is different, it should be:

Code:

addnode IPADDRESS add

for example:

Code:

addnode 127.0.0.1 add

[btcArmory user]

I tried a couple of searches, but didn't come up with a list of IP addresses for bitcoin nodes. Is one of those available? What is the maximum number of concurrent peers that can be established?

getnetworkinfo returns a value of connections = 3

Is this a configuration limit on the number of concurrent peer connections? I do have three at the moment, but wouldn't 16 would be better?

[btcArmory user]

Connections are being added automatically now. 7 is the highest number that I've seen displayed. Thank you for the help!