My zec-qt-wallet 0.5.6 is stuck at block 468824 (Ready! Syncing (467724/100%) Green-checkmark) with ‘Some transactions are not yet confirmed’ since January 23,2019 10:02:04 AM EST.
I opened a Zcash-based store on OpenBazaar on January 15th. I did not enable a Tor connection.
Before getting stuck in this situation, I was receiving the following error: “Authentication failed. The username / password you specified was not accepted by zcashd. Try changing it in the Edit->Settings menu”. Username and password were blank in the Settings menu. Update wallet to latest version and still experienced the same error. I did not see the ‘zcashd’ tab during this time, up until Jan 22. Updated to OB version 2.3. @zec-qt-wallet told me “Some other app (probably openbazar) is running on port 8232 on your machine, which is the zcashd port. zec-qt-wallet thinks it’s talking to zcashd, but actually it’s something else, gets confused and throws an error”. " On Jan 23 10:26 AM @brianchoffman said “You no longer need a full node to buy and sell with #zcash on @openbazaar.”
No error message. However, I’m stuck at block 468824 (Ready! Syncing (467724/100%) Green-checkmark) with ‘Some transactions are not yet confirmed’.
Uninstalled Open Bazaar. Re-opened wallet. Still stuck at block 468824 (Ready! Syncing (467724/100%) Green-checkmark) with ‘Some transactions are not yet confirmed’.
2019-01-08 15:17:07 ERROR: AcceptToMemoryPool: inputs already spent
2019-01-08 15:19:07 ERROR: AcceptToMemoryPool: inputs already spent
…
2019-01-08 15:53:52 ERROR: AcceptToMemoryPool: joinsplit requirements not met
…
2019-01-13 04:19:58 socket send error An operation was attempted on something that is not a socket. (10038)
2019-01-13 04:20:31 socket send error An established connection was aborted by the software in your host machine. (10053)
…
2019-01-13 04:20:56 socket recv error An established connection was aborted by the software in your host machine. (10053)
…
2019-01-13 04:32:36 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2019-01-13 04:32:37 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2019-01-13 04:32:37 ERROR: AcceptToMemoryPool: joinsplit requirements not met
…
2019-01-13 21:31:47 socket recv error An existing connection was forcibly closed by the remote host. (10054)
2019-01-13 21:31:50 socket recv error An existing connection was forcibly closed by the remote host. (10054)
…
2019-01-15 05:15:54 tor: Error parsing socket address 127.0.0.1:0
2019-01-15 05:15:54 tor: Initiating connection to Tor control port 127.0.0.1:0 failed
…
2019-01-23 17:33:03 ERROR: CScriptCheck(): e194f65e94e8708af7928f4c8fa9032a2272480f72efe34cfabd892ae17abce7:19 VerifySignature failed: Script evaluated without error but finished with a false/empty top stack element
2019-01-23 17:33:03 Misbehaving: 46.4.33.85:8233 (0 → 100) BAN THRESHOLD EXCEEDED
2019-01-23 17:33:03 InvalidChainFound: invalid block=000000000174bfafff67079ca0bea2f21f7fb2137eba636cdbf88f01a2a9429f height=468825 log2_work=55.258736 date=2019-01-23 15:04:23
2019-01-23 17:33:03 InvalidChainFound: current best=00000000003c10b34e4c2e979fc9e1a99078a411a6038900ccdaacad9adbd779 height=468824 log2_work=55.258722 date=2019-01-23 15:02:04
2019-01-23 17:33:03 ERROR: ConnectTip(): ConnectBlock 000000000174bfafff67079ca0bea2f21f7fb2137eba636cdbf88f01a2a9429f failed
2019-01-23 17:33:03 InvalidChainFound: invalid block=000000000174bfafff67079ca0bea2f21f7fb2137eba636cdbf88f01a2a9429f height=468825 log2_work=55.258736 date=2019-01-23 15:04:23
2019-01-23 17:33:03 InvalidChainFound: current best=00000000003c10b34e4c2e979fc9e1a99078a411a6038900ccdaacad9adbd779 height=468824 log2_work=55.258722 date=2019-01-23 15:02:04
2019-01-23 17:33:05 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2019-01-23 17:33:05 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2019-01-23 17:33:05 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2019-01-23 17:33:06 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2019-01-23 17:33:15 ProcessMessages: advertizing address 68.80.49.10:8233
2019-01-23 17:33:15 receive version message: /MagicBean:2.0.1/: version 170007, blocks=468889, us=68.80.49.10:49308, peer=147
2019-01-23 17:39:41 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2019-01-23 17:40:28 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2019-01-23 17:47:34 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2019-01-23 17:52:14 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2019-01-23 17:55:34 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2019-01-23 17:56:35 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2019-01-23 17:56:43 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2019-01-23 17:57:45 ERROR: CheckInputs(): tried to spend coinbase at depth 28
2019-01-23 17:57:45 ERROR: AcceptToMemoryPool: ConnectInputs failed
…
2019-01-25 03:14:37 ERROR: AcceptToMemoryPool: joinsplit requirements not met
Actually, I don’t find that in my zcash.conf file… I attempted the Tor connection, once, with no success. It is possible that the log line you are referring to is a one-off error that occurred during this try, only.
OK, so we can rule that out. From the other errors, I can see that your node is banning peers, that’s why it can’t sync. I remember there was a bug like this in zcashd a while ago. Can you print out your zcashd version number?
It’ll be in zcash.log or you can run zcash-cli getinfo. (There’s a zcash-cli executable in the zec-qt-wallet installation folder.
I double-cliked “zcash-cli” in the zec-qt-qallet-v0.5.7 installation folder and a window popped up and closed. I did not determine the zcashd version number this way.
But, I right-clicked zcashd > Properties > Details and notice that the file an dproduct version is both 2.0.1.50, last modified 1/3/2019.
Go to Windows->Command Prompt, cd to the directory with zcash-cli, and then run zcash-cli.exe getinfo .
Alternately, I just released a new version of zec-qt-wallet (v0.5.8), that will show the zcashd version when you hover over the green checkmark. I’d recommend upgrading to it (it also contains other bug fixes).
Lastly, can you paste a screenshot of your zcashd tab in zec-qt-wallet? It’ll be the last tab (After the Transactions tab)? There’s no personal info on this tab, so you should be fine pasting it here.
If you are not seeing the zcashd tab, then you are running an external zcashd, which is outdated. Are you running it in an external window? From WinZEC?
You might need to stop all external zcashd (Look at the task manager to make sure), and then start zec-qt-wallet, to enable the embedded zcashd (and see the zcashd tab)
One last thing I can think of is to just try to resync. Backup your %APPDATA%/Zcash folder, delete it, and then start zec-qt-wallet again to see if the blockchain syncs properly from scratch.
The bug was fixed before I first got ZEC QT? Maybe I used WinZec before the bug was fixed? I thought zecqt came with ‘embedded zcashd’. Anyways, how can I ensure that I am using an updated version of zcashd? I think OpenBazaar is also utilizing (the same?) zcashd? Thank you all so much. Sincerely, n00b
I would recommend you delete the Zcash folder (backup your wallet.dat first!) and resync with the latest zec-qt-wallet with no other instances of zcashd running.
Okay, I performed the uninstall operation using the 0.5.8 version software, making sure no isntances of zcashd are open. then, downloaded the 0.5.9 .msi release from github, Installed it and, now, opened 0.5.9. Hope to report back with success very soon…
