Sent ZEC. Didn't arrive. -1 confirmations?

Hi. recently started using ZEC Wallet full node. Imported private keys from Jaxx Liberty. Wallet shows balance. Tried to send to my Kraken account 2 days ago and it never arrived. Transaction status shows (-1 Confirmations). Transaction ID shows data hasn’t been mined? Are my coins lost? Does it really take this long?

Thanks

Was the node fully synced when you tried to send the transaction?

I tried to check that txID on an few explorers and nothing shows up. My guess is there was some kind of error when you sent and the transaction was never broadcast, so the funds are probably still in the wallet somewhere. If you could post the debug.log that may give a clue.
2efc1b1f9a766bb4b4a59cb32654d0f5ca6f05457aadf703f53c21ca7db62c8a

You may want to restart the node with a -rescan to check, and if that doesn’t work try a -reindex

1 Like

Hi. Thanks for the reply. It was fully synced when I did. It almost immediately gave me the notification that transaction was broadcast. I’ve done a rescan. To be honest I don’t know how to get to the debug log. I’m using the “Windows .MSI” download version. I didn’t try the other download version. Not sure if that one is more of CMD prompt application?

Hi. Is there any way to retrieve my “lost” coins? Coins seem to be in limbo. I still show them in balance on my Jaxx Wallet. If I import private keys to ZEC wallet it shows balance there. However, transaction data still shows -1 confirmations?

Your debug.log file by default is in /Users/yourUsernameHere/AppData/Roaming/Zcash

Your -1 conf transaction failed for whatever reason. We might figure it out from debug.log. But if you see the funds in your wallet, there’s really nothing wrong with trying it again, and I bet it works.

If a Zcash transaction fails, the coins aren’t in limbo. It failed, the coins are still yours, in the same address.

4 Likes

OK so I removed ZEC Full node wallet and chain files. Downloaded app again and let the chain fully sync. I then imported my private keys from Jaxx Liberty and ZEC Wallet shows a balance. So I then tried to send coins again to Kraken address and it showed transaction broadcast successfully. However, I still go back to Confirmation -1? How or where can I upload or send my debug file to see if someone can figure this out?

You can open the debug file in notepad and copy/paste the last several lines here.

Look for any lines that say error or timeout, etc…

There’s too much to paste here. First ERROR I can see is this:

Feb 17 10:00:22.681 ERROR main: AcceptToMemoryPool(): shielded requirements not met txid=a368b01a45691912d92b289100ae7130fd8847c1e1f52e7642e6b7cafaeb114c reason=bad-txns-sapling-unknown-anchor

This several hours before my send transaction.

Then later ALOT of this:

Feb 17 10:11:25.872 ERROR main: ContextualCheckBlockHeader: block at height 1150629, timestamp 1613563897 is too far ahead of local time, limit is 1613563885
Feb 17 10:11:25.872 ERROR main: invalid header received
Feb 17 10:11:25.872 INFO main: ProcessMessages(headers, 238081 bytes) FAILED peer=46
Feb 17 10:11:25.971 ERROR main: ContextualCheckBlockHeader: block at height 1150629, timestamp 1613563897 is too far ahead of local time, limit is 1613563885
Feb 17 10:11:25.971 ERROR main: invalid header received
Feb 17 10:11:25.971 INFO main: ProcessMessages(headers, 238081 bytes) FAILED peer=20
Feb 17 10:11:25.991 ERROR main: ContextualCheckBlockHeader: block at height 1150629, timestamp 1613563897 is too far ahead of local time, limit is 1613563885
Feb 17 10:11:25.991 ERROR main: invalid header received
Feb 17 10:11:25.991 INFO main: ProcessMessages(headers, 238081 bytes) FAILED peer=47
Feb 17 10:11:26.121 ERROR main: ContextualCheckBlockHeader: block at height 1150629, timestamp 1613563897 is too far ahead of local time, limit is 1613563886
Feb 17 10:11:26.121 ERROR main: invalid header received

1 Like

Here is debug file around the send transaction.

Feb 17 20:13:09.169 INFO main: keypool keep 2
Feb 17 20:13:09.169 INFO main: AddToWallet d61a6ca3405adbc23634a3f87cada2ca8577b7db61708176ae779aa221b0d0a3 new
Feb 17 20:13:09.201 INFO main: Relaying wtx d61a6ca3405adbc23634a3f87cada2ca8577b7db61708176ae779aa221b0d0a3
Feb 17 20:13:09.201 INFO main: opid-6d450803-319b-46b5-9729-5c9478224d95: z_sendmany finished (status=success, txid=d61a6ca3405adbc23634a3f87cada2ca8577b7db61708176ae779aa221b0d0a3)
Feb 17 20:13:10.016 INFO main: AddToWallet d61a6ca3405adbc23634a3f87cada2ca8577b7db61708176ae779aa221b0d0a3
Feb 17 20:13:11.086 INFO main: keypool added key 103, size=101
Feb 17 20:13:11.094 INFO main: keypool reserve 3
Feb 17 20:13:11.094 INFO main: keypool return 3
Feb 17 20:13:12.676 ERROR main: ContextualCheckBlockHeader: block at height 1151111, timestamp 1613600163 is too far ahead of local time, limit is 1613599992
Feb 17 20:13:12.676 ERROR main: invalid header received
Feb 17 20:13:12.676 INFO main: ProcessMessages(headers, 238081 bytes) FAILED peer=8
Feb 17 20:13:12.676 ERROR ProcessNewBlock: main: AcceptBlockHeader: prev block not found
Feb 17 20:13:12.676 ERROR ProcessNewBlock: main: ProcessNewBlock: AcceptBlock FAILED
Feb 17 20:13:12.676 INFO main: Misbehaving: 119.23.30.242:8233 (0 → 10)
Feb 17 20:13:29.752 INFO main: keypool reserve 3
Feb 17 20:13:29.752 INFO main: keypool return 3
Feb 17 20:13:45.535 INFO main: keypool reserve 3
Feb 17 20:13:45.535 INFO main: CommitTransaction:
CTransaction(hash=f136cd3a4e, ver=4, fOverwintered=1, nVersionGroupId=892f2085, vin.size=1, vout.size=1, nLockTime=0, nExpiryHeight=1151115, valueBalance=0, vShieldedSpend.size=0, vShieldedOutput.size=0)
CTxIn(COutPoint(2cfa5aba82, 1), scriptSig=473044022048d4ede9ec7600)
CTxOut(nValue=0.00814744, scriptPubKey=76a914f0b2adf7a9dbba619677b3ff)

@adityapk00 Any idea what would cause this timestamp drift? Or how to fix it?

I think your local time is off. Either the clock is off or your timezone is set incorrectly. This is causing the blockchain to reject some valid blocks, which maybe causing your problems with sending.

Can you check if the time on your machine is correct? What OS are you running?

1 Like

Thank you @adityapk00 and @Shawn. Apparently it was a time issue on my PC. I had set local time manually and not to Central time zone. After I changed the time setting, I re-sync’d and she worked!!

6 Likes