BitShares 0.7.0 Feedback

[zerosum]

1.

there is shorts at feed price, and bids above feed. orders are not matching. I don't understand.

Interest of those shorts are too low. Need to be higher than other shorts.

Ohh...Marvelous! Outstanding! You guys  are on a hot streak  in the last 5-6 mo...streak of novel ideas how to kill the market, that is.




2. Unfortunately I cannot confirm the good reports of improved performance like the guys up the thread.
win7/32 the memory usage starts at ~750MB for me and climbs to ~1500MB in 10-15 min or so, of the client running and opening several markets...Interestingly enough, on the 3rd restart the RAM growth is much slower now....it might take more than an hour to double this time... only 988MB after 45 min.

[abit]

there is shorts at feed price, and bids above feed. orders are not matching. I don't understand.

Interest of those shorts are too low. Need to be higher than other shorts.

[lovejoy]

0.7.0 is smooth like butter!  Faster than ever before, like some ninja was in there assassinating memory leaks or something! ;)

Anyways.. going to take the bitUSD I just bought and go to www.cryptofresh.com and get me a t-shirt now. :)

+5%  -- early indications are that as the client improves, so do sales!   :D  Thanks DSN!

[ag]

there is shorts at feed price, and bids above feed. orders are not matching. I don't understand.

[Brekyrself]

Has anything changed when claiming vested balances?

No I've collected them today using 0.7.0.
Are you using wallet_collect_vested_balances userName ?

Simply restarted the client and it worked, odd.

[yellowecho]

Has anything changed when claiming vested balances?

No I've collected them today using 0.7.0.
Are you using wallet_collect_vested_balances userName ?

[Brekyrself]

*restarted the client and working again*

Has anything changed when claiming vested balances?  I tried it today with no luck and also did a rescan with no vesting balances being unlocked.  The last time I claimed was ~9 days ago on the previous client.

Doing a get_info looks like I am not on a fork:

{
  "blockchain_head_block_num": 2071710,
  "blockchain_head_block_age": "5 seconds old",
  "blockchain_head_block_timestamp": "2015-03-19T20:09:40",
  "blockchain_head_block_id": "4bd660567ed6f9e9f1b2e515355898d870e54388",
  "blockchain_average_delegate_participation": "95.28 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": "2,504,344,286.23687 BTS",
  "blockchain_blocks_left_in_round": 2,
  "blockchain_next_round_time": "at least 15 seconds in the future",
  "blockchain_next_round_timestamp": "2015-03-19T20:10:00",
  "blockchain_random_seed": "3cf904698c9b168440137100371684c9d9791baf",
  "client_data_dir": "C:/Users/Brekyrself/AppData/Roaming/BitShares",
  "client_version": "0.7.0",
  "network_num_connections": 3,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2015-03-19T20:09:45",
  "ntp_time_error": -70.801544000000007,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "2015-03-31T09:57:11",
  "wallet_last_scanned_block_timestamp": "2015-03-19T20:09:40",
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

[yellowecho]

After a reboot I'm get getting connected.  Can someone provide me with a command and some nodes?

[Troglodactyl]

Any idea what the patch to 0.7.0-a does?

I guess it's an updated version to also include the changes made to the web_wallet .. they missed those for 0.7.0 AFAIK

edit: can't find that patch .. where is it?

I believe he's referring to the auto-downloading GUI update: https://github.com/BitShares/web_wallet/releases/tag/0.7.0-a

It added the "Make a payment" button and improved the transfer page, apparently.

[monsterer]

Any idea what the patch to 0.7.0-a does?

I guess it's an updated version to also include the changes made to the web_wallet .. they missed those for 0.7.0 AFAIK

edit: can't find that patch .. where is it?

After you download the win32 0.7.0 and install, it asks if you want to upgrade to the 0.7.0-a patch

[xeroc]

Any idea what the patch to 0.7.0-a does?

I guess it's an updated version to also include the changes made to the web_wallet .. they missed those for 0.7.0 AFAIK

edit: can't find that patch .. where is it?

[monsterer]

Any idea what the patch to 0.7.0-a does?

[pc]

Bought some bitUSD at the same ASK for the lowest price.. order processed right away to withdraw my BTS.. but my buy order just sat there.

That may have been due to price rounding. I. e. the internal price of the offer you tried to match was slightly higher than what was displayed and/or what you put in your order.

[Tuck Fheman]

win7/8gb, running much faster. charts loading very fast now. switching between tabs is very smooth. very impressed.

the only issue i see is in the console :

Code Select Expand


>> get_rich_quick tuckfheman-com

{
  "unlocked": false
}


[BunkerChainLabs-DataSecurityNode]

Another thing to note.. my memory usage floats around 671 to 675MB.

CPU around 2-4% utilization on standby.. about double that of Google Chrome running in the background.

I don't know if these are targets you were trying to achieve or not.

Also I notice when I click around the Exchange area quickly the client no longer crashes. In 0.6.2 if I didn't wait to allow all the data to load before clicking on another section it would often crash. Now the client seems to handle that condition better.

Was happy I didn't have to redownload/reindex the whole db again on upgrade. Those are brutal.

Will post anything else I notice.  +5% though!