BitShares Forum
Main => Technical Support => Topic started by: monsterer on January 25, 2015, 06:53:42 pm
-
I've sent a transaction to an address I own BTSCixaFfbFsBJELLP7PnyP4WNswn2ifGKtB:
TXID = 6c149b3cab10453d579ebd09806dfe6587e67505
{
"hex": "03cac3d59751a89e1ab401ff21cb672d914b0fa189730383307f91cec880b0a161",
"native_pubkey": "BTS8NXtXmPu1T2BZjZbTjZF3FfVvUA6yiDGREjLmMJYKVMMmAyiPw",
"native_address": "BTSCixaFfbFsBJELLP7PnyP4WNswn2ifGKtB",
"pts_normal_address": "Potgd2UFu8uLgvm3BE5RMHLZ5vGcGF66LZ",
"pts_compressed_address": "PqGVZjcmibwbdYBtUkFUWHfHR91vgbE5EK",
"btc_normal_address": "1GxuUwn892xGtexBojRaCG6VqfqnSQ8cko",
"btc_compressed_address": "1JLiRevdxVzXqGP37FbdMGREAtb6tr2BLd"
}
But this is not shown by wallet_account_transaction_history, and doesn't appear in the GUI either.
Furthermore, calling wallet_verify_titan_deposit on the txid results in an assert:
wallet_verify_titan_deposit 6c149b3cab10453d579ebd09806dfe6587e67505
10 assert_exception: Assert Exception
withdraw_condition.memo.valid():
{}
bitshares wallet.cpp:2516 bts::wallet::wallet::verify_titan_deposit
{}
bitshares wallet.cpp:2557 bts::wallet::wallet::verify_titan_deposit
{}
bitshares common_api_client.cpp:6240 bts::rpc_stubs::common_api_client::wallet_verify_titan_deposit
{"command":"wallet_verify_titan_deposit"}
bitshares cli.cpp:629 bts::cli::detail::cli_impl::execute_command
This is a bit of a problem for the website version of the gateway I'm working on because my new workflow is to generate a BTS deposit address for each customer, but if transactions cannot be detected on arrival, this isn't going to be workable :(
-
Transfers to "addresses" do not show in the history .. your funds should appear in "balance" though ..
Devs are working on a rewrite of the "history" code (known issue)
-
Interestingly:
(wallet closed) >>> blockchain_get_balance BTSCixaFfbFsBJELLP7PnyP4WNswn2ifGKtB
10 assert_exception: Assert Exception
balance_record.valid():
{}
th_a blockchain_api.cpp:152 blockchain_get_balance
{}
th_a common_api_client.cpp:1787 blockchain_get_balance
{"command":"blockchain_get_balance"}
th_a cli.cpp:629 execute_command
and
(wallet closed) >>> blockchain_list_address_transactions BTSCixaFfbFsBJELLP7PnyP4WNswn2ifGKtB
13 N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_9gregorian16bad_day_of_monthEEEEE: Day of month value is out of range 1..31
Day of month value is out of range 1..31: unable to convert ISO-formatted string to fc::time_point_sec
{"what":"Day of month value is out of range 1..31"}
th_a time.cpp:45 from_iso_string
unable to convert ISO-formatted string to fc::time_point
{}
th_a time.cpp:55 from_iso_string
{"command":"blockchain_list_address_transactions"}
th_a cli.cpp:629 execute_command
(wallet closed) >>> blockchain_list_address_transactions BTSCixaFfbFsBJELLP7PnyP4WNswn2ifGKtB "2016-01-28T10:23:00"
[]
with a deposit OP:
},{
"type": "deposit_op_type",
"data": {
"amount": 10000,
"condition": {
"asset_id": 4,
"slate_id": 0,
"type": "withdraw_signature_type",
"data": {
"owner": "BTSCixaFfbFsBJELLP7PnyP4WNswn2ifGKtB",
"memo": null
}
}
}
-
Wow, what a lot of errors associated with this transaction! That should give the core devs some good test cases :)
-
(wallet closed) >>> blockchain_list_address_transactions BTSCixaFfbFsBJELLP7PnyP4WNswn2ifGKtB
13 N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_9gregorian16bad_day_of_monthEEEEE: Day of month value is out of range 1..31
Day of month value is out of range 1..31: unable to convert ISO-formatted string to fc::time_point_sec
{"what":"Day of month value is out of range 1..31"}
th_a time.cpp:45 from_iso_string
unable to convert ISO-formatted string to fc::time_point
{}
th_a time.cpp:55 from_iso_string
{"command":"blockchain_list_address_transactions"}
th_a cli.cpp:629 execute_command
0.6.1 version (DVS) seems to have sorted this: it uses blockchain height to filter (the default value works too).
-
Transfers to "addresses" do not show in the history .. your funds should appear in "balance" though ..
Devs are working on a rewrite of the "history" code (known issue)
xeroc is right. monsterer what command did you use to transfer to address?
How important is this feature for your system and how soon do you need it?
-
Transfers to "addresses" do not show in the history .. your funds should appear in "balance" though ..
Devs are working on a rewrite of the "history" code (known issue)
xeroc is right. monsterer what command did you use to transfer to address?
How important is this feature for your system and how soon do you need it?
Hi Vikram,
I used wallet_transfer_to_address from the command line of the sending client (since the GUI cannot send to address yet).
Currently the core of the gateway is reliant on wallet_account_transaction_history, which was working fine when we had clients sending to our account address, but moving forward we want to have them send to a unique BTS address which we generate for them and this is causing us problems.
I suppose I could re-write the core of the gateway to manually scan all transactions in each block, but I don't really like that idea, especially if a real fix is coming soon (as soon as possible), which would be great. Any idea on when this might be ready? :)
Cheers, Paul.