BitShares Forum
Main => Technical Support => Topic started by: mlondon on October 01, 2014, 04:48:04 pm
-
About 2 weeks ago I attempted to enter a few bitUSD short positions of which none were executed. Since then I have updated to 0.4.18 and though I see the orders in my transaction history I do not see them in my open orders on the market page where I would just cancel them. I'm assuming these requests must be stuck and there must be some manual way to cancel them..
-
wallet_market_order_list USD BTSX
should show them
in there you will find an 'id'
order can be canceled with
wallet_market_cancel_order <id>
-
I entered wallet_market_order_list USD BTSX in the console and it says No market orders found. The 3 separate transactions all show in my transaction history however they do not appear to have been filled and there has been no credit back to my balance. Here is what it says when I follow the date link from My Accounts tab for those transactions..
Transaction #c9d2a51b
Block #529603 , Transaction #0 , Next #0
TimeStamp: September 19, 2014 at 2:00:40 PM PDT
Transaction #30150985
Block #529583 , Transaction #0 , Next #0
TimeStamp: September 19, 2014 at 1:57:20 PM PDT
Transaction #0f3b754c
Block #529547 , Transaction #0 , Next #0
TimeStamp: September 19, 2014 at 1:51:20 PM PDT
-
Please let me know if there is anything else I can do or add to this thread in order to resolve this issue. I appreciate all the support on these forums and understand that you guys are probably busy with the conference coming up and all. Either way I want to express my gratitude and appreciation to all those who spend time answering questions from noobs like me.
-
I'm having a similar problem. A couple of short orders, about the same age, that are stuck and can't be cancelled.
Using xeroc's method in the console produces an error messages starting like this:
10 assert_exception: Assert Exception
BN_num_bits(n) <= 63:
{}
bitshares bigint.cpp:55 fc::bigint::to_int64
type mismatch multiplying asset {"amount":
Using 0.4.20 64 bit, Win 7
-
I'm having a similar problem. A couple of short orders, about the same age, that are stuck and can't be cancelled.
Using xeroc's method in the console produces an error messages starting like this:
10 assert_exception: Assert Exception
BN_num_bits(n) <= 63:
{}
bitshares bigint.cpp:55 fc::bigint::to_int64
type mismatch multiplying asset {"amount":
Using 0.4.20 64 bit, Win 7
known issue
https://bitsharestalk.org/index.php?topic=6918.msg92326#msg92326
no idea how to fix .. but I have seen them myself already :-\
-
I entered wallet_market_order_list USD BTSX in the console and it says No market orders found. The 3 separate transactions all show in my transaction history however they do not appear to have been filled and there has been no credit back to my balance. Here is what it says when I follow the date link from My Accounts tab for those transactions..
Transaction #c9d2a51b
Block #529603 , Transaction #0 , Next #0
TimeStamp: September 19, 2014 at 2:00:40 PM PDT
Transaction #30150985
Block #529583 , Transaction #0 , Next #0
TimeStamp: September 19, 2014 at 1:57:20 PM PDT
Transaction #0f3b754c
Block #529547 , Transaction #0 , Next #0
TimeStamp: September 19, 2014 at 1:51:20 PM PDT
First we lookup those transactions:
(wallet closed) >>> blockchain_get_transaction c9d2a51b
{
"trx": {
"expiration": "20140919T220754",
"delegate_slate_id": null,
"operations": [{
"type": "withdraw_op_type",
"data": {
"balance_id": "BTSXPCSqZuhonKTZUPPyqM439mfwiCvEQXPuh",
"amount": 30050000,
"claim_input_data": ""
}
},{
"type": "short_op_type",
"data": {
"amount": 30000000,
"short_index": {
"order_price": {
"ratio": "0.003333333333333333",
"quote_asset_id": 22,
"base_asset_id": 0
},
"owner": "BTSX6UkApBzXNjdYxcuH8LBx7ebnXa4NiHCez"
}
}
}
],
"signatures": [
"1fc904995e1764c3e7be1bd2f21e2e259f2dd8b713a8db9983b7b08fb036a52074ece3c00b65aac747e9e89426cdafeebbc51c0ab1aa88d76d08fc210108edeadb",
"2076f8b9d39c934f24e543c7756d569ff4ec556958cb75ed1c1a48917c3655f3233db9d0c2a421413cca78309481379242bcf0dd99a4cb0dc27147a9577d9bf4e9"
]
},
"signed_keys": [],
"validation_error": null,
"required_deposits": [],
"provided_deposits": [[
"BTSX111111111111111111113MQ7LD",{
"amount": 30000000,
"asset_id": 0
}
]
],
"deposits": [[
0,{
"amount": 30000000,
"asset_id": 0
}
]
],
"withdraws": [[
0,{
"amount": 30050000,
"asset_id": 0
}
]
],
"yield": [],
"deltas": [[
0,{
"amount": -30050000,
"asset_id": 0
}
],[
1,{
"amount": 30000000,
"asset_id": 0
}
]
],
"required_fees": {
"amount": 0,
"asset_id": 0
},
"alt_fees_paid": {
"amount": 0,
"asset_id": 0
},
"balance": [[
0,
50000
]
],
"net_delegate_votes": [],
"chain_location": {
"block_num": 529603,
"trx_num": 0
}
}
(wallet closed) >>> blockchain_get_transaction 30150985
{
"trx": {
"expiration": "20140919T220432",
"delegate_slate_id": null,
"operations": [{
"type": "withdraw_op_type",
"data": {
"balance_id": "BTSXPCSqZuhonKTZUPPyqM439mfwiCvEQXPuh",
"amount": 30442199,
"claim_input_data": ""
}
},{
"type": "short_op_type",
"data": {
"amount": 30392199,
"short_index": {
"order_price": {
"ratio": "0.003290317910516514",
"quote_asset_id": 22,
"base_asset_id": 0
},
"owner": "BTSX5V4NUkBr5ZVDJdkFPbXTb9DEWsyhxxrYT"
}
}
}
],
"signatures": [
"1fc30779e234dfba61c0b20943876f2b4f57989c893eca89822077a2af1dcefb63a78dc2bb3cce136dbe2f72d8634951c69cf80405002d6f446390fe6b8ed58edf",
"200b8c53ce0d086f66994044bef1d15176dfd0c1f52ee5b4f1731f8d0536df40ae80cf9e460defee583d6e6eeb879ed4721dad7973358d883a7e285c4260314718"
]
},
"signed_keys": [],
"validation_error": null,
"required_deposits": [],
"provided_deposits": [[
"BTSX111111111111111111113MQ7LD",{
"amount": 30392199,
"asset_id": 0
}
]
],
"deposits": [[
0,{
"amount": 30392199,
"asset_id": 0
}
]
],
"withdraws": [[
0,{
"amount": 30442199,
"asset_id": 0
}
]
],
"yield": [],
"deltas": [[
0,{
"amount": -30442199,
"asset_id": 0
}
],[
1,{
"amount": 30392199,
"asset_id": 0
}
]
],
"required_fees": {
"amount": 0,
"asset_id": 0
},
"alt_fees_paid": {
"amount": 0,
"asset_id": 0
},
"balance": [[
0,
50000
]
],
"net_delegate_votes": [],
"chain_location": {
"block_num": 529583,
"trx_num": 0
}
}
(wallet closed) >>> blockchain_get_transaction 0f3b754c
{
"trx": {
"expiration": "20140919T215835",
"delegate_slate_id": null,
"operations": [{
"type": "withdraw_op_type",
"data": {
"balance_id": "BTSXPCSqZuhonKTZUPPyqM439mfwiCvEQXPuh",
"amount": 32950000,
"claim_input_data": ""
}
},{
"type": "short_op_type",
"data": {
"amount": 32900000,
"short_index": {
"order_price": {
"ratio": "0.00303951367781155",
"quote_asset_id": 22,
"base_asset_id": 0
},
"owner": "BTSXCD1BBRAZfbX4fV3ZHapS6E4YkkqSzUNP3"
}
}
}
],
"signatures": [
"206b6b7f856e929e03368c7de97148284e92987de11e03db42d1500aeda2edcff347e6a2f8d9c9589f0e156f2347a904d3e31536744c4ad7651b5c86577dc33182",
"20daec473c04d6d5a42dbd1424b317c407ef1724fa37b52f674f9c1960b2be0e5fb721de7a8e8b1216210122f04bd27c3fbc7ab7a9bd03442a11adab946ce9bc79"
]
},
"signed_keys": [],
"validation_error": null,
"required_deposits": [],
"provided_deposits": [[
"BTSX111111111111111111113MQ7LD",{
"amount": 32900000,
"asset_id": 0
}
]
],
"deposits": [[
0,{
"amount": 32900000,
"asset_id": 0
}
]
],
"withdraws": [[
0,{
"amount": 32950000,
"asset_id": 0
}
]
],
"yield": [],
"deltas": [[
0,{
"amount": -32950000,
"asset_id": 0
}
],[
1,{
"amount": 32900000,
"asset_id": 0
}
]
],
"required_fees": {
"amount": 0,
"asset_id": 0
},
"alt_fees_paid": {
"amount": 0,
"asset_id": 0
},
"balance": [[
0,
50000
]
],
"net_delegate_votes": [],
"chain_location": {
"block_num": 529547,
"trx_num": 0
}
}
There was an automatic cancellation of shorts which occurred as part of one of the hardforks. I manually checked it and found that your shorts were canceled and funds sent to these balances:
(wallet closed) >>> blockchain_get_balance BTSX7Hc4RzjHheEQTD1ww7Tgt2gc7UdvZPPiK
{
"balance": 32900000,
"condition": {
"asset_id": 0,
"delegate_slate_id": 0,
"type": "withdraw_signature_type",
"data": {
"owner": "BTSXCD1BBRAZfbX4fV3ZHapS6E4YkkqSzUNP3",
"memo": null
}
},
"genesis_info": null,
"last_update": "20140925T164520",
"deposit_date": "20140925T164520"
}
(wallet closed) >>> blockchain_get_balance BTSX7pL48qBfQMLu222Tq9zzmhEWb7acHc2nc
{
"balance": 30392199,
"condition": {
"asset_id": 0,
"delegate_slate_id": 0,
"type": "withdraw_signature_type",
"data": {
"owner": "BTSX5V4NUkBr5ZVDJdkFPbXTb9DEWsyhxxrYT",
"memo": null
}
},
"genesis_info": null,
"last_update": "20140925T164520",
"deposit_date": "20140925T164520"
}
(wallet closed) >>> blockchain_get_balance BTSXHkSroRNMfnQu3EcahCfyKSmvMELhy4iCW
{
"balance": 30000000,
"condition": {
"asset_id": 0,
"delegate_slate_id": 0,
"type": "withdraw_signature_type",
"data": {
"owner": "BTSX6UkApBzXNjdYxcuH8LBx7ebnXa4NiHCez",
"memo": null
}
},
"genesis_info": null,
"last_update": "20140925T164520",
"deposit_date": "20140925T164520"
}
The owner addresses of the these balances are the same as the owner addresses used for your original short operations. Unless you restored from an old backup or there was another problem with your wallet, the private keys should be in your wallet and the balances should be showing up as part of the output for the console commands "wallet_account_balance" and "wallet_account_balance_ids".
To be specific, you should see BTSX7Hc4RzjHheEQTD1ww7Tgt2gc7UdvZPPiK, BTSX7pL48qBfQMLu222Tq9zzmhEWb7acHc2nc, and BTSXHkSroRNMfnQu3EcahCfyKSmvMELhy4iCW listed when you do "wallet_account_balance_ids".
If you are absolutely sure the funds are missing, then there may have been a problem with your wallet and you may need to try the "wallet_regenerate_keys" command before the funds show up in your list of balances. Take a look and let me know.
-
Yes I see all the wallet ids however I get the following when entering wallet_regenerate_keys in the console and still do not have the funds showing in my balance..
>> wallet_regenerate_keys
11002 exit_cli_command: exit CLI client requested by user
{}
bitshares cli.cpp:244 get_line
{}
bitshares cli.cpp:377 parse_recognized_interactive_command
Error parsing command "wallet_regenerate_keys": exit CLI client requested by user (11002)
Usage:
wallet_regenerate_keys <account_name> <max_key_number> regenerates private keys as part of wallet recovery
regenerates private keys as part of wallet recovery
Parameters:
account_name (account_name, required): the account the generated keys should be a part of
max_key_number (uint32_t, required): the last key number to regenerate
Returns:
int32_t
-
Yes I see all the wallet ids however I get the following when entering wallet_regenerate_keys in the console and still do not have the funds showing in my balance..
>> wallet_regenerate_keys
11002 exit_cli_command: exit CLI client requested by user
{}
bitshares cli.cpp:244 get_line
{}
bitshares cli.cpp:377 parse_recognized_interactive_command
Error parsing command "wallet_regenerate_keys": exit CLI client requested by user (11002)
Usage:
wallet_regenerate_keys <account_name> <max_key_number> regenerates private keys as part of wallet recovery
regenerates private keys as part of wallet recovery
Parameters:
account_name (account_name, required): the account the generated keys should be a part of
max_key_number (uint32_t, required): the last key number to regenerate
Returns:
int32_t
So the correct addresses show up when you do "wallet_account_balance_ids" ? Then you have the keys and do no need to regenerate them.
If the balance addresses are present, then the amounts should be reflected in the output of wallet_account_balance, because wallet_account_balance internally just uses the output of wallet_account_balance_ids. Are the addresses tied to the correct username when you do wallet_account_balance_ids?
Are you sure it doesn't just look like the balances are not present because there is no record in the transaction history, or are you completely sure that your account balance amount is less than it should be?