"Status: 0/unconfirmed, in memory pool".

[BillyBobZorton]

I made a transaction while syncing a full client and it seems to be stuck at "Status: 0/unconfirmed, in memory pool".

This is an altcoin im dealing with, but since the full client is basically a fork of Core 0.14.2 I can still get technical help here.

The coins I sent were confirmed and spendable, they are old transactions. I thought that you could make transactions without syncing the blockchain as long as the coins you are attempting to spend are confirmed, which is the case here. In fact I think I have done this before in Bitcoin Core and the transaction got some confirmations before I was fully synced, but with this wallet im stuck.

Any help?? should I just wait for it to sync and hope it gets broadcasted?

[1715377421]

1715377421

[1715377421]

1715377421

[1715377421]

1715377421

[ICOs]

If the blockchain is not synced, how are you going to see any confirmations? You don't have data for the current network status yet.

[BillyBobZorton]

If the blockchain is not synced, how are you going to see any confirmations? You don't have data for the current network status yet.

I don't think that's how it works. You should be able to send coins if the coins you are sending are spendable (enough confirmations).

I have confirmed something is wrong because the node is now fully synced and the transaction still has a "?" icon and has the "Status: 0/unconfirmed, in memory pool" message when double clicked. Nothing happened when looking at the explorer too.

The fee was the recommend one by the wallet.

I could try -zapwallettxes (which is annoying since it takes a long time) and try sending it again but I don't get what went wrong.

[HCP]

Yes, your wallet knows that those coins are "confirmed and spendable" at the date the wallet is synced up to... but how does your wallet know that those coins have not already been spent between the time it is synced to, until the current block?

Have you tried using "getrawtransaction TRANSACTIONID" and then copy paste the HEX output into "sendrawtransaction HEX" in "Help -> Debug Window -> Console" ?

It might just need a rebroadcast... or you may see the error that is stopping it from being accepted by the network.