BitShares Forum
Main => Technical Support => Topic started by: julian1 on November 20, 2014, 11:42:03 am
-
xxxx (unlocked) >>> blockchain_is_synced
true
wallet_transfer 90 BTS xxx xxx
> wallet_account_balance
shows account less 90 bts ,
> wallet_account_transaction_history
doesn't show the transaction
I was testing voting approval and the votes did register. Only the bts didn't come back to me!
-
- did you get any command reply to the "wallet_transfer"? it should have contained the transactionID
- try restarting the client
-
Thanks xeroc. I did get a response, but it's no longer in my command history. It's only a token amount. I did try restarting the client.
I've reproduced again. Sending 1 bts, which gets lost + the 0.5 fee.
walletxxx (locked) >>> wallet_unlock 999 OK
walletxxx (unlocked) >>> wallet_account_balance
ACCOUNT BALANCE
============================================================
xxxx 6.68812 BTS
walletxxx (unlocked) >>> wallet_transfer 1 BTS xxxx xxxx
TIMESTAMP BLOCK FROM TO AMOUNT MEMO FEE ID
======================================================================================================================================================================
2014-11-20T11:56:52 PENDING xxxx xxxx 1.00000 BTS 0.50000 BTS 595ce3bd
Email bb622c02e7a24b9537811389f827c1dbea9f496a sent successfully, and is now known as 0007b2a486a46f471b941046c0f9e78344aa801a.
walletxxx (unlocked) >>>
walletxxx (unlocked) >>> wallet_account_balance
ACCOUNT BALANCE
============================================================
xxxx 5.18812 BTS
walletxxx (unlocked) >>>
--- there are now 15 active connections to the p2p network
I should add, I'm running HEAD revision (probably silly)
walletxxx (unlocked) >>> about
{
"blockchain_name": "BitShares",
"blockchain_description": "The Future of Banking",
"client_version": "v0.4.24-248-g5ea07f6",
"bitshares_toolkit_revision": "5ea07f645693debbac9e343ad8b2aa05c87b89ec",
"bitshares_toolkit_revision_age": "14 hours ago",
"fc_revision": "5dbab6ba11e711b762d3e8dcaf924f2254266c32",
"fc_revision_age": "17 hours ago",
"compile_date": "compiled on Nov 20 2014 at 09:49:51",
"boost_version": "1.55",
"openssl_version": "OpenSSL 1.0.1f 6 Jan 2014",
"build": "linux 64-bit"
}
-
do you have a delegate in your wallet?
if so issue the following command
wallet_set_transaction_scanning true
-
Haha :) :) Great! All funds recovered.
Yes, I was attempting to set up a delegate account. What is the effect of that flag?
-
Yes, I was attempting to set up a delegate account. What is the effect of that flag?
beeing delegate is a very time-sensitive task .. in contrast .. scanning for TITAN (anonymous) transaction is very CPU intensive ..
the devs figured out that in early times that doing both might make your delegate miss blocks .. thus the disabled scanning transactions if a delegate is in the wallet ..
the CLI warns about that .. the GUI obviously does not ..
That's btw, the reason why you cannot register a delegate in the GUI anymore :)
Glad to see you recovered your funds.
I'll add this to the wiki page .. it's about time!
http://wiki.bitshares.org/index.php/Best_Practices/RecoverFunds#Activating_transaction_scanning