Sounds like you may have lost connectivity to other Qtum peers (needs TCP in/out on port 3888), is it possible that you made this configuration in the past and somehow lot this setup in the upgrade?
The wallet should be able to make connections to at least a few peers, up to 8 active connections after running for an hour.
Make sure you have some good backups of your wallet.dat file, then try deleting the local copy of the blockchain, With the wallet stopped, delete the blockchain (folders blocks, chainstate, database, and stateQtum), these folders will be in the Qtum folder that also holds the wallet.dat file. Reboot your computer. Run the wallet again. Good luck!
@jester78, in order to send tokens, you must hold enough QTUM in the Q address that is tied to that token. You would typically need 0.1 QTUM or so, but it depends on your Gas Price and Gas Limit settings. Bottom line, send some QTUM to that Q address that is tied to that token.
Your wallet may have problems connecting to other nodes. You should have a few peer connections, up to 8. Sometimes the "addnode" command will help get the connections established. Please see this blog for more information https://medium.com/@jb395official/qtum-peer-connections-may-21-2018-ba12bda71e4f
Hello chilllerfunk, for this situation (where the wallet gets stuck with the synchronization) I recommend deleting the local copy of the blockchain and starting over. The whole sequence is given in Question 6 step 5 of this blog (https://medium.com/@jb395official/top-10-qtum-new-user-questions-april-22-2018-307a65dad83f):
Do this next step only if you have good wallet.dat backups. With the wallet stopped, delete the blockchain (folders: blocks, chainstate, database, and stateQtum — in the same “Qtum” folder as the wallet.dat file). This will cause your wallet to reload the entire blockchain when you restart. Don’t worry, the blockchain holds your coin/token balance, with 7,000+ copies worldwide. This step is effective if your wallet gets stuck syncing part way through the blockchain.
I may have talked with you on Telegram (as Jackson). If so, you found this problem was caused by an old "Reserve" setting in the wallet, set higher than the coins available. Reserve allows the wallet to hold back a quantity of coins from staking, and seems to interfere with sending tokens in this case. I will file an issue with the wallet developers to add an appropriate error message.
If that wasn't you, and you still have a problem sending tokens, please revert and we can take a look.
It is rarely possible for the wallet to lose track of a stake that is made for an orphan block. An orphan block happens when a wallet publishes a new block at the same time with another wallet. One block, the orphan block, must be cancelled out. Normally, the stake from the orphan block is returned to that wallet, and you don't even notice what happened.
Occasionally there is some disruption in returning the orphan block, and an additional tool can be used to recover the missing stake. This is discussed in the this blog about Orphan Blocks https://medium.com/@jb395official/orphan-blocks-june-16-2018-a8f4799dcc2c
I would also encourage you to seek Qtum tech support on our Telegram channel at https://t.me/qtumofficial, which allows for more interactive troubleshooting.