Topic: Armory says my transaction is unconfirmed, which is incorrect. (Read 149 times)
Hi. If you're willing to roll your own version, try my patch here and let me know if it works for you. Note that you will need to use brew to install python2 before this will work. (Systems are starting to default to "python" = "python3", so I need to force 2.x usage.)
Ahhh. I'll look into the Qt thing. I think the Qt servers moved stuff around recently. I can't remember if the changes made it back to the 0.96.4 build script.
Your transaction history is probably lagging behind. Post your logs for review.
Does my problem have something to do with running 0.96.3-991? I had to build this from source, and I have problems building 0.96.4 from source because /dupes has been deprecated in Homebrew --- so it would be nice if Doug could update the build instructions.
Last I checked a month ago, the build instructions were fine. You may want to try the notes here. In particular, if you're using brew, python may now be equal to Python 3, which we don't want for now (uggh). You'll have to use brew to install python2 and run the build script using python2.
In any event, a complete overhaul is still on my radar, and will probably be rolled out once we upgrade to Python 3 & Qt 5. I just have other, more pressing issues to deal with, unfortunately.
EDIT: Someone else emailed me and confirmed that the directions for 0.96.4 are no longer valid. I'll update the directions for 0.96.5. For now, using the directions I posted should be fine, but if not, swapping out "Homebrew/dupes/zlib" with "Homebrew/homebrew-core/zlib" should do the trick. (Actually, I should probably just switch to "xz" for 0.97, since it doesn't require this silliness. Harumph harumph.)
As I mentioned to you earlier, I did swap out Homebrew/dupes/zlib with Homebrew/homebrew-core/zlib. Things compiled fine until it hit issues with qt, saying it was unable to open a file.
Anyway, I took goatpig's advice, wiped out the Armory database, and let it rebuild, and this solved the issue -- still in 0.96.3991. Yay!
I don't think I want to risk updating to 0.96.4 until some of these issues seem resovled. I see that a lot of people are having trouble with it, and the version I'm using is working.
I'm on a 2017 MacBook Pro, using Core 0.16.2, in case anyone else is having trouble with a Mac. Armory 0.96.3991 is syncing with the blockchain now, and all my coins are considered confirmed.
Thank you so much, goatpig and droark!
Your transaction history is probably lagging behind. Post your logs for review.
Does my problem have something to do with running 0.96.3-991? I had to build this from source, and I have problems building 0.96.4 from source because /dupes has been deprecated in Homebrew --- so it would be nice if Doug could update the build instructions.
Last I checked a month ago, the build instructions were fine. You may want to try the notes here. In particular, if you're using brew, python may now be equal to Python 3, which we don't want for now (uggh). You'll have to use brew to install python2 and run the build script using python2.
In any event, a complete overhaul is still on my radar, and will probably be rolled out once we upgrade to Python 3 & Qt 5. I just have other, more pressing issues to deal with, unfortunately.
EDIT: Someone else emailed me and confirmed that the directions for 0.96.4 are no longer valid. I'll update the directions for 0.96.5. For now, using the directions I posted should be fine, but if not, swapping out "Homebrew/dupes/zlib" with "Homebrew/homebrew-core/zlib" should do the trick. (Actually, I should probably just switch to "xz" for 0.97, since it doesn't require this silliness. Harumph harumph.)
Quote
Does my problem have something to do with running 0.96.3-991?
Likely but not guaranteed.
Quote
I have problems building 0.96.4 from source because /dupes has been deprecated in Homebrew
Building on OSX is gimped because of the poor Qt4 support. You can go around this by building only the server straight from the configure script. On Linux, it would look like this:
Code:
sh autogen.sh
./configure --without-gui
make -jauto
./configure --without-gui
make -jauto
Once you got the server built, you can setup a Ubuntu VM to run the client from. It's fairly easy to build the client on Ubuntu, the only extra bit of work you need is setting up the networking between the server running on the OSX host and the client in the Ubuntu guest. This way you can keep Core and all your blockchain/database files on OSX, and just operate the GUI and your wallets from the VM.
Your transaction history is probably lagging behind. Post your logs for review.
Does my problem have something to do with running 0.96.3-991? I had to build this from source, and I have problems building 0.96.4 from source because /dupes has been deprecated in Homebrew --- so it would be nice if Doug could update the build instructions.
You read my mind!
Your transaction history is probably lagging behind. Post your logs for review.
Core is running at the same time as Armory, correct? Is Core fully up-to-date?
Yes, I updated to Core 0.16.2, and it is fully up-to-date and running.
I also just noticed that the block height, according to Core, is 536633 (currently), whereas my Armory wallet says at the bottom right that it is connected to 526111 blocks. Blockexplorer.com says it was included in Block 532676. This is past block 526111, so that explains that part. Underneath the information about what block it was included in, it says "LockTime 526111." Although it now has 3958 confirmations. What
is "LockTime"? And why is it at the same block height where my Armory Wallet stopped?OK -- I know what LockTime is now. So the question is why did my Armory wallet stop at this block height?
Core is running at the same time as Armory, correct? Is Core fully up-to-date?
Yes, I updated to Core 0.16.2, and it is fully up-to-date and running.
I also just noticed that the block height, according to Core, is 536633 (currently), whereas my Armory wallet says at the bottom right that it is connected to 526111 blocks. Blockexplorer.com says it was included in Block 532676. This is past block 526111, so that explains that part. Underneath the information about what block it was included in, it says "LockTime 526111." Although it now has 3958 confirmations. What
is "LockTime"? And why is it at the same block height where my Armory Wallet stopped? Core is running at the same time as Armory, correct? Is Core fully up-to-date?
Yes, I updated to Core 0.16.2, and it is fully up-to-date and running.
Core is running at the same time as Armory, correct? Is Core fully up-to-date?
I'm running Bitcoin Core 0.16.0, if that matters.
This might be the reason.
You should make sure to always keep your software up-to-date.
Not that this will only guarantee you compatibility, but newer versions also contain bugfixes and security- or performance-improvements.
Make sure to get Armory 0.96.4 (https://btcarmory.com/0.96.4-release/) and core 0.16.2 (https://bitcoin.org/en/download).
Hi All:
I am running Armory 0.96.3.991 on a 2017 MacBook Pro. The change from a relatively recent (weeks ago) transaction is listed as "unconfirmed", (and hence, not spendable), on my Armory startup page, down at the bottom, where "Maximum Funds," "Spendable Funds," and "Unconfirmed" are listed.
However, just checking this out with a block explorer -- I used blockexplorer.com, if it matters -- shows that the transaction has 3867 confirmations. I'm pretty sure that is enough confirmations to guarantee that the funds are mine, and that I can spend them if I wish, in principle. But I take it my Armory wallet will not allow me to spend the funds until it considers them "confirmed" (?)
Any ideas as to why this transactoin is not seen by my Armory wallet as confirmed, even after 3867 confirmations?
I'm running Bitcoin Core 0.16.0, if that matters.
I am running Armory 0.96.3.991 on a 2017 MacBook Pro. The change from a relatively recent (weeks ago) transaction is listed as "unconfirmed", (and hence, not spendable), on my Armory startup page, down at the bottom, where "Maximum Funds," "Spendable Funds," and "Unconfirmed" are listed.
However, just checking this out with a block explorer -- I used blockexplorer.com, if it matters -- shows that the transaction has 3867 confirmations. I'm pretty sure that is enough confirmations to guarantee that the funds are mine, and that I can spend them if I wish, in principle. But I take it my Armory wallet will not allow me to spend the funds until it considers them "confirmed" (?)
Any ideas as to why this transactoin is not seen by my Armory wallet as confirmed, even after 3867 confirmations?
I'm running Bitcoin Core 0.16.0, if that matters.
Jump to: