From our visit to NC for Cryptolina.  Brief mention of BitShares.

http://www.usatoday.com/story/money/business/2014/09/02/baverman-bitcoin/14728425/

 

Quote from: Xeldal on September 11, 2014, 04:29:35 pm

Quote from: bytemaster on September 11, 2014, 03:32:22 pm

Quote from: MeTHoDx on September 11, 2014, 03:25:00 pm

The balance that displays when I send or receive a transaction (to the right of fees) is different than the balance that displays in the blue banner at the top (next to estimated yield). There is about a 20% difference.

An earlier version of the client had a bug that corrupted some of the meta-data associated with some of your transactions.   Look through your transaction history for transactions where the amount transferred was "0" then use "wallet_scan_transaction TRX_ID true"   to correct it.

I have the same issue, although this did not fix it for me.

I have many "TO UNKNOWN" transactions that remove from my balance. using "wallet_scan_transaction TRX_ID true" doesn't fix.
I presume these are market orders that were placed, canceled, but never returned?

transaction detail:

Code: [Select]

{"type":"short_op_type","data":{"amount":xxxxxxx,"short_index":{"order_price":{"ratio":"0.00303030303030303","quote_asset_id":22,"base_asset_id":0}

Yeah it never resolved for me either. Which balance is the correct one for you? The one in transaction history or the main balance in the upper right?

for me neither of the balances is correct...
xeroc posted this under github https://github.com/BitShares/bitshares_toolkit/issues/769  not yet resolved but devs know...

lets first start the bitEUR and get it liquid .. say a few 100kEUR or so .. before that it does not make any sense to market it towards a bank :-)

oh sure, this is in a somewhat distant future

Quote from: kisa0145 on September 14, 2014, 04:53:14 pm

could someone point to a simple explanation of steps for seamless client upgrade to a new version please?

Windows, Linux or god forbid OSX ?

Windows 7 - 64bit

guys hello... not sure where to post this, perhaps have a look if that could be of interest to btsx team? apparently XRP is going up today because there is a speculation that City National Bank of US is playing with Ripple - look at the Golbal Strategy Session page 4

https://alliance.nacha.org/sites/alliance.nacha.org/files/files/Meetings%20website%20page/Agenda%20Structure%20for%20website.pdf

i was just thinking those banks who start rippling first could be the ones who become interested in building first bitUSD/bitEUR bridges into fiat...

Quote from: kisa0145 on September 13, 2014, 10:22:47 am

now reading that BM warned here https://bitsharestalk.org/index.php?topic=8156.0 that attempts to restore from older back-ups, and market activity in particular, would cause problems at this stage. i must admit that i didn't read through best practices thread early enough due to wrong prioritization of time allocation. so i discovered that appying certain practices which worked fine with other cryptos to BTSX can easily be wrong, and for a non-tech person even more so. as the system crash during trading, and the older wallet backup is used, then unfortunately issues arise...

but still ... theses "issues" do not make you loose funds ... the issues he is basically talking about is "loosing" of memo and recipient information ..
The keys for the exchange/market are still derived deterministically and can always be recovered from the account private key ..
It's just an inconvenience for the user

yeah i know, just feel somewhat embarassed that both myself and user support + devs have to take time and effort to address issues which could have been avoided if I was more aware and attentive. well, this is a learning process for all of us - and learning never ends and in the end the winning platform will likely be the fool-proof one *lol*

now reading that BM warned here https://bitsharestalk.org/index.php?topic=8156.0 that attempts to restore from older back-ups, and market activity in particular, would cause problems at this stage. i must admit that i didn't read through best practices thread early enough due to wrong prioritization of time allocation. so i discovered that appying certain practices which worked fine with other cryptos to BTSX can easily be wrong, and for a non-tech person even more so. as the system crash during trading, and the older wallet backup is used, then unfortunately issues arise...

Quote from: kisa0145 on September 12, 2014, 07:12:07 pm

"wallet_scan_progress": "37.44 %", no transaction in the history yet...

markets were not enabled yet .. at 30% .. i'd say ..
let's wait

okay here we go xeroc

"wallet_scan_progress": "100.00 %"

wallet_account_transaction_history

RECEIVED            BLOCK            FROM                TO                  AMOUNT             .....  ID     

2014-07-19T00:00:00 0             GENESIS            kisa0145         xxxxxxx                     xxxx
...                               
2014-09-12T18:29:40 433157    kisa0145            UNKNOWN     12,250.00000 BTSX     7b893f41
2014-09-12T18:29:40 433172    kisa0145            UNKNOWN     13,000.00000 BTSX     b6e4dbd1
2014-09-12T18:29:40 433186    kisa0145            UNKNOWN     13,500.00000 BTSX     d37cf834
2014-09-12T18:29:40 433192    kisa0145            UNKNOWN     13,625.00000 BTSX     86bbd08d
2014-09-12T18:29:40 433246    kisa0145            UNKNOWN     12,500.00000 BTSX     44f1cb99
2014-09-12T18:29:40 433261    kisa0145            UNKNOWN     12,925.00000 BTSX     f39e8978
2014-09-12T18:29:40 433494    kisa0145            UNKNOWN     12,858.00000 BTSX     fec7cc45
2014-09-12T18:29:40 433552    kisa0145            UNKNOWN     12,857.60999 BTSX     3bcea812
2014-09-12T18:29:40 433603    kisa0145            UNKNOWN     13,200.00000 BTSX     9b771d45
2014-09-12T18:29:40 433618    kisa0145            UNKNOWN     13,445.00000 BTSX     b29df527

>> wallet_recover_transaction 7b893f41 (each of the above IDs yields the same output):

10 assert_exception: Assert Exception
has_deposit:
    {}
    bitshares  wallet.cpp:3315 bts::wallet::wallet::recover_transaction

    {}
    bitshares  wallet.cpp:3374 bts::wallet::wallet::recover_transaction

    {}
    bitshares  common_api_client.cpp:1763 bts::rpc_stubs::common_api_client::wallet_recover_transaction

    {"command":"wallet_recover_transaction"}
    bitshares  cli.cpp:537 bts::cli::detail::cli_impl::execute_command