maybe because of this *very informative* release: https://github.com/bitshares/bitshares-2/releases/tag/2.0.160128

Quote from: xeroc on December 16, 2015, 03:52:02 PM

Quote from: monsterer on December 16, 2015, 03:42:12 PM
Wow. Just wow. So, all the unique id's which exchanges have been diligently filing and storing are now worthless? Or worse still after exchanges upgrade they can be subject to double spends against users deposits since the the original deposit txid is now totally different?

The amount of affected operation IDs is (as per my understanding) limited to only a few hours worth of transactions .. definitely not all of them ..

definitely not "only a few hours worth of transactions"

in my case: 

oldest tx: 1.11.13306 (dated  16-Oct-15) changed to  1.11.13305
latest tx:  1.11.356893 (dated  21-Nov-15 ) changed to  1.11.356892

we got no deposit after 21-Nov-15

I've just upgraded and all tx id changed? anyone can confirm?

For example tx id was 1.11.13306 , now it is changed to 1.11.13305.

My system rely on this tx id, as the result i get a lot of duplicate deposits recently, and forced to roll back our bts deposits.

I assume this tx id is not reliable for identifying a transaction? Are we doing it wrong?

Thank you

same issue on ubuntu 14.04 box

anyone know what is the equivalent of old wallet_account_transaction_history command for RPC API? this command is for querying latest transactions of an account.

Hi,

What is the equivalent of wallet_account_transaction_history in BitShares 2.0? I need to get incoming transactions periodically.

I found get_account_history can be called inside command prompt, but unable to call it with RPC request.

Thanks

sorry wrong forum, i move this discussion to Help & Technical Support : https://bitsharestalk.org/index.php/topic,19066.0.html

Hi,

What is the equivalent of wallet_account_transaction_history in BitShares 2.0? I need to get incoming transactions periodically.

I found get_account_history can be called inside command prompt, but unable to call it with RPC request.

Thanks

"this can take a long time" <- how long is this? any estimation for specific hardware e.g. "mine installed on amazon ec2 2 cpu it takes x days"

is the faucet fixed?

nmv it is a log issue.

solved.

How large disk space required for running bitshares_client?

I use 40gb vps and it full in 1-2 days.

Thanks

pc, thanks for your answer.

1 more question:

what is the max length of a memo message in a transaction?

I have few questions about balance API:

1. When calling wallet_account_transaction_history it returns is_market and is_market_cancel, what do they mean?

2. How to find reference for bitshares asset_id, i know BTS is 0, what is asset_id for USD?

3. Calling wallet_account_balance will return:

QuoteArray
(
    [ 0 ] => Array
        (
            [ 0 ] => accountname
            [ 1 ] => Array
                (
                    [ 0 ] => Array
                        (
                            [ 0 ] => 0
                            [ 1 ] => 889000
                        )

                )

        )

)

which 0 represents asset_id? red, blue, or green?

Thank you

I might be a very stupid question, but I cannot find it everywhere (maybe i searched with wrong keyword)

What is the smallest unit of BTS? Is it 0.00000001 just like Bitcoin?

Other important question, what is the default fee for BTS transfer?

Thanks

Quote from: xeroc ¯\_(ツ)_/¯ on March 25, 2015, 09:18:09 AM
you are running 0.8.*???

yes

{
  "id": 0,
  "result": {
    "blockchain_name": "BitShares",
    "blockchain_description": "Decentralized Exchange",
    "client_version": "0.8.0",
    "bitshares_revision": "1a71a01b0fe057df486ea5691ba6e26b20e15d7a",
    "bitshares_revision_age": "36 hours ago",
    "fc_revision": "374f141f0a31fb362a2eb3fc982acf57107cc5bc",
    "fc_revision_age": "30 days ago",
    "compile_date": "compiled on Mar 24 2015 at 02:39:55",
    "boost_version": "1.54",
    "openssl_version": "OpenSSL 1.0.1f 6 Jan 2014",
    "build": "linux 64-bit"
  }
}