Quote from: ScubaFuz on October 01, 2017, 07:12:05 PM

Quote from: SuperClam on October 01, 2017, 12:41:51 AM

Quote from: blackcheese on September 30, 2017, 09:19:19 PM

Quote from: chilly2k on September 30, 2017, 09:10:51 PM

Quote from: blackcheese on September 30, 2017, 08:51:57 PM

Quote from: ScubaFuz on September 30, 2017, 08:44:50 PM

Quote from: blackcheese on September 30, 2017, 07:54:51 PM

Anyone having any issues with getting transactions through? I sent one earlier today took about ~10-15 mins for first transaction. Now I've been sitting at 40 minutes still not one confirmation and the transaction ID doesn't show up in the block explorer?

You can do an easy test at freebitcoins.com and get a small payment from the faucet. If that shows up in your wallet, the network is working fine.

Thanks I'll try. Original transaction still hasn't got a single confirmation..

Where are you sending from? If it's not in the block explorer, there is a good chance it hasn't been broadcast to the network. In which case something is going on at the sender.

I sent it from the qt like I did earlier today. But just this one isn't confirming, I've tried restarting it and nothing is working. Worried about losing the coins now.

chilly2k is basically spot on with his advice.
Ensure you have connections to some peers, so that the transaction has a means to get out to the network.
If the CLAM shows as still attributed to your pubkey/address, then there should be nothing to be concerned about.
Worst case, you have to rescan and/or resync and send again (assuming the above).

So basically it is possible to create a private fork and lose sync with the network by staking while you are still syncing. Can you go a (few) block(s) back and resync or do you have to reload the entire blockchain?
Shouldn't there be a safety buildin that if the block you created isn't accepted by the network that it is discarded and you keep syncing with blocks that have been accepted? That way you cannot create your own fork.

Simply prevent your mature blocks from staking while the wallet syncs.

Go to console and type

reservebalance true and a number bigger than the number of CLAM you have

i.e.
reservebalance true 99999

Console response

{
"reserve" : true,
"amount" : 99999.00000000
}

Now the wallet will not stake mature blocks until

reservebalance false

is entered, or the wallet is restarted.