BitShares Forum
Main => General Discussion => Topic started by: vikram on April 23, 2015, 12:40:03 am
-
https://github.com/BitShares/bitshares/releases/tag/bts%2F0.9.0-rc2
https://github.com/BitShares/bitshares/releases/tag/bts%2F0.9.0
https://github.com/BitShares/bitshares/releases/tag/bts%2F0.9.2
-
I would suggest adding "depth" button on upper-right corner in the chart, and widening order books. It would be great if order books have price and amounts of both assets (e.g. Amount(NOTE), Price(BTS/NOTE), Amount(BTS))
-
I was able to fire it up without any crash related problems on OS X. still hanging after auth for a while, I assume it is rescanning during this. It would be good to provide a message along side the loader, so users know something is happening in the back ground.
-
Is unusual to see your open orders in your order history list.
My perception on Order History list are already completed trades, there is Open Order List anyway I would suggest to remove it in the Order History.
-
Is unusual to see your open orders in your order history list.
My perception on Order History list are already completed trades, there is Open Order List anyway I would suggest to remove it in the Order History.
The order list in the GUI is really strange. It doesn't contain shorts in an older release.
-
Bug: (http://i.imgur.com/go2iKxn.png)
Edit: windows - missing the icon to minimize the client
-
How to titian? I cannot find the way
-
https://github.com/BitShares/bitshares/releases/tag/bts%2F0.9.0-rc2
This version is only for those who are willing to help test and find any serious problems before the final release.
So is this "rep system" or "burn records" something that's considered a "feature" of BitShares or just something that was thrown in for shits & giggles and will be removed before release?
I'm assuming it still doesn't work since (AFAIK) no one's acknowledged it ever had an issue and I see no fix.
Edit : Confirmed, still broken. Voting FOR yields AGAINST every single time. If you click FOR it swaps to AGAINSTS as well.
FWIW : We hired a guy to write an article for us, paid him in crypto, went to give his BitShares account some rep and ended up giving him a bunch of AGAINST votes. Not good for a small business trying to make a living via BitShares.
-
After resyncing the chain, client is using ~2 GB memory. After entering password to log in, client slowly builds memory usage to just over 5GB until wallet opens and it drops to around 4.5 GB and stays there. After clicking on a market in the >Exchange> tab the client crashes. It only crashes the first time I do this after a new resync while memory usage is over 4.5 GB. If I restart the client, memory usage is down to around 1.5 GB and it never crashes again when clicking on a market from the Exchange tab.
-
Much more stable than RC1 for me!
All the GUI issues I saw were resolved, except the Price graph still scrolls on its own when I hover over it (and continues to scroll around randomly even when I stop moving the cursor). Also, the same thing happens to the Margin and Short tables, but not the Buy/Sell tables.
-
trying to sell muh daily mining of .4424 bitUSD @ 227.7427 and there is a buy order for 2.048 bitUSD sitting there. happens repeatedly, cancels order. (win7/8gb/i7)
getStackTrace@app.js:35:5176
○ request@app.js:45:8571
○ market_submit_bid@app.js:46:7599
○ post_ask@app.js:43:48237
○ app.js:43:46411
○ confirm_order@app.js:43:46529
○ confirm_order@app.js:36:27294
○ app.js:10:7986
○ e@app.js:10:14415
○ $eval@app.js:6:83428
○ $apply@app.js:6:83659
○ app.js:10:14472
○ dispatch@app.js:3:14478
○ handle@app.js:3:11253
35005 invalid_asset_amount: invalid asset amount
{"share_string":"100.753400000000","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"100.753400000000","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"100.753400000000"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"100.753400000000","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"nunya","real_quantity":"100.753400000000","quantity_symbol":"BTS","quote_price":"0.004390920104","quote_symbol":"USD","sign":true}
bitshares wallet.cpp:3549 bts::wallet::wallet::submit_bid
{}
bitshares common_api_client.cpp:5279 bts::rpc_stubs::common_api_client::wallet_market_submit_bid
actually, can't sell at any price it appears.
Edit : Logged out, logged back in, now see a Severe network problems message, so I'm assuming that's what caused the above, despite that message not displaying when I was placing the orders.
-
My address book still has about 20 unregistered full BTS addresses as well as about 20 delegate names. I didn't add any of these to the address book. It also still lists these registered names as unregistered.
I've noticed, If I first go to the >Transfer> tab and quickly select the address book before the balance is updated. The address book simply shows all of my own accounts and none of the addresses that I added myself. If I wait for the balances to update before opening the address book or close and reopen the address book, It then shows all my accounts plus these 20 or so BTS addresses and seemingly random delegates, all of which are listed "unregistered". At no time does it display the addresses that I added to the book.
-
Having troubles building 0.9.0
cmake .
...
CMake Error at libraries/fc/CMakeLists.txt:193 (add_subdirectory):
The source directory
/home/local/bitshares/libraries/fc/vendor/websocketpp
does not contain a CMakeLists.txt file.
-
trying to sell muh daily mining of .4424 bitUSD @ 227.7427 and there is a buy order for 2.048 bitUSD sitting there. happens repeatedly, cancels order. (win7/8gb/i7)
getStackTrace@app.js:35:5176
○ request@app.js:45:8571
○ market_submit_bid@app.js:46:7599
○ post_ask@app.js:43:48237
○ app.js:43:46411
○ confirm_order@app.js:43:46529
○ confirm_order@app.js:36:27294
○ app.js:10:7986
○ e@app.js:10:14415
○ $eval@app.js:6:83428
○ $apply@app.js:6:83659
○ app.js:10:14472
○ dispatch@app.js:3:14478
○ handle@app.js:3:11253
35005 invalid_asset_amount: invalid asset amount
{"share_string":"100.753400000000","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"100.753400000000","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"100.753400000000"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"100.753400000000","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"nunya","real_quantity":"100.753400000000","quantity_symbol":"BTS","quote_price":"0.004390920104","quote_symbol":"USD","sign":true}
bitshares wallet.cpp:3549 bts::wallet::wallet::submit_bid
{}
bitshares common_api_client.cpp:5279 bts::rpc_stubs::common_api_client::wallet_market_submit_bid
actually, can't sell at any price it appears.
Edit : Logged out, logged back in, now see a Severe network problems message, so I'm assuming that's what caused the above, despite that message not displaying when I was placing the orders.
This should be fixed in 0.9 RC2? Are you using RC2 or RC1?
-
This should be fixed in 0.9 RC2? Are you using RC2 or RC1?
RC1, I missed RC2 somehow. loading up latest, which I assume is official 9.0?
Loaded up 9.0, order went through, but the rep system is still broken and I'll keep bringing it up until it's fixed since i think it's a key part, whether anyone else does or not.
It displays FOR immediately after posting Posting/Burning, but if you go to another tab and come back, you'll see your vote was actually AGAINST.
-
why did you remove the tray icon?
-
Having troubles building 0.9.0
cmake .
...
CMake Error at libraries/fc/CMakeLists.txt:193 (add_subdirectory):
The source directory
/home/local/bitshares/libraries/fc/vendor/websocketpp
does not contain a CMakeLists.txt file.
git submodule update --init --recursive
-
After resyncing the chain, client is using ~2 GB memory. After entering password to log in, client slowly builds memory usage to just over 5GB until wallet opens and it drops to around 4.5 GB and stays there. After clicking on a market in the >Exchange> tab the client crashes. It only crashes the first time I do this after a new resync while memory usage is over 4.5 GB. If I restart the client, memory usage is down to around 1.5 GB and it never crashes again when clicking on a market from the Exchange tab.
Possible memory leak while upgrading 'wallet' (not the chain replay).
I met similar issue with v0.9.0-rc1: https://bitsharestalk.org/index.php/topic,15851.msg203714.html#msg203714
-
why did you remove the tray icon?
Better if there is a confirmation before quit.
-
Having troubles building 0.9.0
cmake .
...
CMake Error at libraries/fc/CMakeLists.txt:193 (add_subdirectory):
The source directory
/home/local/bitshares/libraries/fc/vendor/websocketpp
does not contain a CMakeLists.txt file.
same here:
CMake Error at libraries/fc/CMakeLists.txt:193 (add_subdirectory):
The source directory
/home/calabiyau/bitshares/libraries/fc/vendor/websocketpp
does not contain a CMakeLists.txt file.
-- Configuring incomplete, errors occurred!
-
Having troubles building 0.9.0
cmake .
...
CMake Error at libraries/fc/CMakeLists.txt:193 (add_subdirectory):
The source directory
/home/local/bitshares/libraries/fc/vendor/websocketpp
does not contain a CMakeLists.txt file.
same here:
CMake Error at libraries/fc/CMakeLists.txt:193 (add_subdirectory):
The source directory
/home/calabiyau/bitshares/libraries/fc/vendor/websocketpp
does not contain a CMakeLists.txt file.
-- Configuring incomplete, errors occurred!
same solution
git submodule update --init --recursive
-
same solution
git submodule update --init --recursive
Already tried, unfortunately not resolved:
calabiyau@calabiyauUB-14:~/bitshares$ git submodule update --init --recursive
fatal: destination path 'vendor/websocketpp' already exists and is not an empty directory.
Clone of 'https://github.com/zaphoyd/websocketpp' into submodule path 'vendor/websocketpp' failed
Failed to recurse into submodule path 'libraries/fc'
-
same solution
git submodule update --init --recursive
Already tried, unfortunately not resolved:
calabiyau@calabiyauUB-14:~/bitshares$ git submodule update --init --recursive
fatal: destination path 'vendor/websocketpp' already exists and is not an empty directory.
Clone of 'https://github.com/zaphoyd/websocketpp' into submodule path 'vendor/websocketpp' failed
Failed to recurse into submodule path 'libraries/fc'
rm -rf libraries/fc/vendor/websocketpp
git submodule update --init --recursive
-
Thank you xeroc, this saved my day ;)
-
+5% +5% +5%
LOVE IT!!
Not sure how, but it's running faster than 0.8.0 did.
The syncing was quicker too. Whatever you guys are doin, it frign rocks, thank you!!! :)
-
why did you remove the tray icon?
Various reports of hard-to-debug crashes related to it. Was easiest to just remove it.
-
This should be fixed in 0.9 RC2? Are you using RC2 or RC1?
RC1, I missed RC2 somehow. loading up latest, which I assume is official 9.0?
Loaded up 9.0, order went through, but the rep system is still broken and I'll keep bringing it up until it's fixed since i think it's a key part, whether anyone else does or not.
It displays FOR immediately after posting Posting/Burning, but if you go to another tab and come back, you'll see your vote was actually AGAINST.
Bump. Doesn't need to be a priority right now i guess, but it's a nice thing not to forget
-
0.9.0
I voted for bitcube, then, in the top right corner of the linux client, the accounts menu showed his name in my list.
that scared the hell out of me, it made me think I just gave him rights to my accounts or something.
not that it's possible, but man, that feature really threw me off. i restarted the client and then his name was gone from that drop-down menu.
is that an intended feature for some reason? if so, why?
thanx :)
-ken
-
voted for some delegates, look what's in my account tab...
(http://i.imgur.com/BjG9mJe.png)
edit: entries vanished after restarting the wallet
edit2: didn't save my votes
-
Actual price should be applied when one clicks the order book.
For example,
Real market price: 0.24200002371600232416822776848632
Shown price: 0.242000
If I click the sell order on the order book, the real price should be applied, or the order cannot be completed.
This may let people down, thinking this is a bug.
https://github.com/BitShares/web_wallet/issues/674
-
Nice work guys. This version seems very stable.
-
invalid asset amount (35005) still exists
getStackTrace@app.js:35:5176
○ request@app.js:43:10039
○ market_submit_ask@app.js:44:9237
○ post_ask@app.js:42:51107
○ app.js:42:49027
○ confirm_order@app.js:42:49145
○ confirm_order@app.js:37:27453
○ app.js:10:7986
○ e@app.js:10:14415
○ $eval@app.js:6:83428
○ $apply@app.js:6:83659
○ app.js:10:14472
○ dispatch@app.js:3:14478
○ handle@app.js:3:11253
35005 invalid_asset_amount: invalid asset amount
{"share_string":"86.956522","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"86.956522","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"86.956522"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"86.956522","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"clayop","real_quantity":"86.956522","quantity_symbol":"BTS","quote_price":"1.15","quote_symbol":"MOONFUND","sign":true}
bitshares wallet.cpp:3525 bts::wallet::wallet::submit_ask
{}
bitshares common_api_client.cpp:5313 bts::rpc_stubs::common_api_client::wallet_market_submit_ask
-
Branding is everything.
Please get the green and blue logo with the "b" onto the splash screen, the login screen, and in the client app itself.
The web wallet needs our logo too.
Here's the image:
http://bitshares-munich.de/img/_masters/BitShares-logo-transparent.png
Branding is everything.
-
the client doesn't work when one doesn't have more than 4 GB RAM memory available?
-
Great improvements, feels smoother again and I like the new UI (except for the market order depth graphic looks AWFUL and squished)
-
the client doesn't work when one doesn't have more than 4 GB RAM memory available?
0.9.0 requires less memory and in my case takes 1-1.5 GB RAM.
-
the client doesn't work when one doesn't have more than 4 GB RAM memory available?
0.9.0 requires less memory and in my case takes 1-1.5 GB RAM.
0.9.0 is only taking 750MB on my machine. Huge improvement!
-
Great improvements, feels smoother again and I like the new UI (except for the market order depth graphic looks AWFUL and squished)
I changed it yesterday, only one chart at a time now with a button to switch between them. They're bigger too. If you're building yourself you can get it from the develop branch of the web wallet, but I hope we can put out a GUI update next week.
Also has manual candle time intervals.
-
invalid asset amount (35005) still exists
getStackTrace@app.js:35:5176
○ request@app.js:43:10039
○ market_submit_ask@app.js:44:9237
○ post_ask@app.js:42:51107
○ app.js:42:49027
○ confirm_order@app.js:42:49145
○ confirm_order@app.js:37:27453
○ app.js:10:7986
○ e@app.js:10:14415
○ $eval@app.js:6:83428
○ $apply@app.js:6:83659
○ app.js:10:14472
○ dispatch@app.js:3:14478
○ handle@app.js:3:11253
35005 invalid_asset_amount: invalid asset amount
{"share_string":"86.956522","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"86.956522","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"86.956522"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"86.956522","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"clayop","real_quantity":"86.956522","quantity_symbol":"BTS","quote_price":"1.15","quote_symbol":"MOONFUND","sign":true}
bitshares wallet.cpp:3525 bts::wallet::wallet::submit_ask
{}
bitshares common_api_client.cpp:5313 bts::rpc_stubs::common_api_client::wallet_market_submit_ask
see {"from_account_name":"clayop","real_quantity":"86.956522","quantity_symbol":"BTS","quote_price":"1.15","quote_symbol":"MOONFUND","sign":true}
"real_quantity":"86.956522"
I think you can only have 5 places to the right of the decimal (there are 6 there)
-
There is some kind of reset in my votes, "my votes" tab list is empty and every approval icon I had clicked/checked in the past to vote is empty too.
-
There is some kind of reset in my votes, "my votes" tab list is empty and every approval icon I had clicked/checked in the past to vote is empty too.
Same behavior also happening on my end.
-
oops, my bad. the splash screen has the correct logo.
but then the login screen and ui (bottom left corner) do not.
the web wallet still needs the "b" logo as well.
Here's the image:
http://bitshares-munich.de/img/_masters/BitShares-logo-transparent.png
Branding is everything.
-
"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 there anybody that also get's the 'severe network problems' message?
-
"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"
On my desktop I think it was something like 45 minutes, on a FX-8350 CPU 16GB of RAM and a SSD
EDIT
CPU usage was 34%
Windows 7
-
Is there anybody that also get's the 'severe network problems' message?
Yep, at first it says that, then after it connects to more of the nodes that message disappeared.
v0.9.0 is frign awesome, well worth the wait.
-
Is there anybody that also get's the 'severe network problems' message?
o yes
-
invalid asset amount (35005) still exists
getStackTrace@app.js:35:5176
○ request@app.js:43:10039
○ market_submit_ask@app.js:44:9237
○ post_ask@app.js:42:51107
○ app.js:42:49027
○ confirm_order@app.js:42:49145
○ confirm_order@app.js:37:27453
○ app.js:10:7986
○ e@app.js:10:14415
○ $eval@app.js:6:83428
○ $apply@app.js:6:83659
○ app.js:10:14472
○ dispatch@app.js:3:14478
○ handle@app.js:3:11253
35005 invalid_asset_amount: invalid asset amount
{"share_string":"86.956522","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"86.956522","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"86.956522"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"86.956522","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"clayop","real_quantity":"86.956522","quantity_symbol":"BTS","quote_price":"1.15","quote_symbol":"MOONFUND","sign":true}
bitshares wallet.cpp:3525 bts::wallet::wallet::submit_ask
{}
bitshares common_api_client.cpp:5313 bts::rpc_stubs::common_api_client::wallet_market_submit_ask
Had the same problem, strangely enough flipping the market solved the problem
-
invalid asset amount (35005) still exists
getStackTrace@app.js:35:5176
○ request@app.js:43:10039
○ market_submit_ask@app.js:44:9237
○ post_ask@app.js:42:51107
○ app.js:42:49027
○ confirm_order@app.js:42:49145
○ confirm_order@app.js:37:27453
○ app.js:10:7986
○ e@app.js:10:14415
○ $eval@app.js:6:83428
○ $apply@app.js:6:83659
○ app.js:10:14472
○ dispatch@app.js:3:14478
○ handle@app.js:3:11253
35005 invalid_asset_amount: invalid asset amount
{"share_string":"86.956522","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"86.956522","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"86.956522"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"86.956522","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"clayop","real_quantity":"86.956522","quantity_symbol":"BTS","quote_price":"1.15","quote_symbol":"MOONFUND","sign":true}
bitshares wallet.cpp:3525 bts::wallet::wallet::submit_ask
{}
bitshares common_api_client.cpp:5313 bts::rpc_stubs::common_api_client::wallet_market_submit_ask
Had the same problem, strangely enough flipping the market solved the problem
same on my side .. after i've increased my tx fees from 0.1 to 0.5 it worked again ...
-
Slower start than previous version.
-
i tried to install 0.90 and it gives me this warning (osx client):
Warning: BitShares has detected the Adobe Application Manager plug-in is installed on this computer at /Library/Internet Plug-Ins/AdobeAAMDetect.plugin. This plug-in crashes when loaded into BitShares. Please remove this plug-in and restart BitShares.
However when i look into that directory, the mentioned plugin isn't there.
I am not able to enter the program because of this.
-
i tried to install 0.90 and it gives me this warning (osx client):
Warning: BitShares has detected the Adobe Application Manager plug-in is installed on this computer at /Library/Internet Plug-Ins/AdobeAAMDetect.plugin. This plug-in crashes when loaded into BitShares. Please remove this plug-in and restart BitShares.
However when i look into that directory, the mentioned plugin isn't there.
I am not able to enter the program because of this.
crossposting for visibility: I ran into the same issue a few months ago, iirc running http://www.adobe.com/support/contact/cscleanertool.html fixed it for me.
-
i tried to install 0.90 and it gives me this warning (osx client):
Warning: BitShares has detected the Adobe Application Manager plug-in is installed on this computer at /Library/Internet Plug-Ins/AdobeAAMDetect.plugin. This plug-in crashes when loaded into BitShares. Please remove this plug-in and restart BitShares.
However when i look into that directory, the mentioned plugin isn't there.
I am not able to enter the program because of this.
paging @xeroc
-
Transaction scanning takes forever, feels like a regression :/
-
I had several wallets with unregistered (TITAN) accounts interconnected with wallet_add_contact_account. After upgrading to 0.9.0, the contact_accounts are gone, and wallet_account_transaction_history shows public keys instead of account names for related transactions.
wallet_list_contacts show the corresponding public keys, but the label is equal to the key.
After setting a label with wallet_add_contact <key> <label> I can transfer to the labelled account, but the tx history on the sending side shows ANONYMOUS as recipient, and on the recieving side it shows UNKNOWN as sender (where at least in one case the sender is actually a registered account). Also, the receiving side does not show the memo anymore.
-
so far 0.9 feels much faster.
also the exchange now is loading much faster.
something to change or consider
1. on the exchange the "last price" is placed good, but the "call price" should be right on the right side of it and not on the right side of my monitor.
-
0.9.0 runs perfect
it took a while,
first it crashed but then i read that one has to close the client after instal befor you key in the pw for the first time
and after that i had not crashes
the severe network error was gone after sync
it works stable
i will try the markets
thanks to all devs
-
in my addressbook i have now many contacts i never transfered any kind of amount and the real addresses i took into my book shows "unregistered".
-
When I sent funds to accounts I don't own, they are labeled as "no registered" and it is confusing since I think I made a spell error... ( the system means they are not registered from me...)
Sent from my ALCATEL ONE TOUCH 997D
-
1.The installation, replay database and whatever update to the wallet it does, went surprisingly smooth on an unsupported 32bit Win7 regular HD machine (using the bitshares_client - i.e CLI)
2. The New GUI trading looks nice...one problem only - IT WILL BE REAL NICE if ONE CAN SEE and ACTUALLY PLACE his/her orders....(or to have any idea if it is a call/buy or short order for that matter)....pic coming if this is not clear by itself.
-
1.The installation, replay database and whatever update to the wallet it does, went surprisingly smooth on an unsupported 32bit Win7 regular HD machine (using the bitshares_client - i.e CLI)
2. The New GUI trading looks nice...one problem only - IT WILL BE REAL NICE if ONE CAN SEE and ACTUALLY PLACE his/her orders....(or to have any idea if it is a call/buy or short order for that matter)....pic coming if this is not clear by itself.
A picture would be appreciated for #2, because obviously you can see and place orders in a normally working wallet.
-
I miss the ability to see my account balances on top of the page all the time to make better trading decision's... now I must switch to the sell or buy "page" to have a quick view of my account balance...
Sent from my ALCATEL ONE TOUCH 997D
-
1.The installation, replay database and whatever update to the wallet it does, went surprisingly smooth on an unsupported 32bit Win7 regular HD machine (using the bitshares_client - i.e CLI)
2. The New GUI trading looks nice...one problem only - IT WILL BE REAL NICE if ONE CAN SEE and ACTUALLY PLACE his/her orders....(or to have any idea if it is a call/buy or short order for that matter)....pic coming if this is not clear by itself.
A picture would be appreciated for #2, because obviously you can see and place orders in a normally working wallet.
Here is the pic. BTW see the right-hand sliding bar - I cannot go any lower than that. And this is just one short order not placed yet (and no open orders - and at times one can have tens of already placed orders!)
(http://i.imgur.com/YRQyH2j.png)
You should know this but one have no idea what kind of order (buy/sell/short) she is confirming.
(http://i.imgur.com/clqfAtr.png)
And if you wonder why on pic#1 you cannot see and on pic#2 you can see the order - pic one is under 'short' and pic#2 is what you see under buy orders.
-
....
And if you wonder why on pic#1 you cannot see and on pic#2 you can see the order - pic one is under 'short' and pic#2 is what you see under buy orders.
OK it's an issue of your screen having low vertical resolution, the open orders will let you scroll inside their table but you can't even see that. BTW there should be an auto-update of the GUI available to a new version that has the orderbook chart switchable with the price chart.
What resolution are you using? I'll use it to see if I can figure out a solution..
Edit: You can tell you're trying to confirm a short from the coloring of the price which is blue, but I can see if I can make it more explicit.
-
....
And if you wonder why on pic#1 you cannot see and on pic#2 you can see the order - pic one is under 'short' and pic#2 is what you see under buy orders.
OK it's an issue of your screen having low vertical resolution, 1*the open orders will let you scroll inside their table but you can't even see that. BTW there should be an auto-update of the GUI available to a new version that has the orderbook chart switchable with the price chart.
2*What resolution are you using? I'll use it to see if I can figure out a solution..
Edit: You can tell you're trying to confirm a short from the coloring of the price which is blue, but 3*I can see if I can make it more explicit.
1* No I cannot see that.
2* 1366x768
3* Please!
-
in 0.9 you can' see your own created assets
in Dashboard>Assets>My Assets it shows me no assets at all
-
New market layout is awesome! Especially, I love using full precision function - this will beat tricky sellers.
-
Please make transaction scanning faster. As i have multiple wallets, it is such a waste of time to wait for each wallet to be scanned.
-
I don't have 16 GB and i7 to try new wallet but I'am sure that these one is best in the whole crypto space. Thank you. I can't wait version 1.0 and new few billions shares more with everything inside.
Happy Angel shares owner
-
I don't have 16 GB and i7 to try new wallet but I'am sure that these one is best in the whole crypto space. Thank you. I can't wait version 1.0 and new few billions shares more with everything inside.
Happy Angel shares owner
I am as vocal as it gets (including about the damn client). But I do believe you have not even tied upgrading this time!!!!!
Believe it or not all phases of upgrading to 0.9.0 went with less than 1G memory for me - old laptop win7/32bit, regular HD.
Conditions:
-fully synced blockchain before start;
-use bitshares_client.exe (i.e. the CLI client);
-restart after replaying the blockchain (replay took about 70 min.) and log in into your wallet(s).
This should help if you care to try it.
-
I don't have 16 GB and i7 to try new wallet but I'am sure that these one is best in the whole crypto space. Thank you. I can't wait version 1.0 and new few billions shares more with everything inside.
Happy Angel shares owner
@dritz3r - You will be glad if you upgrade to 0.9.0, it is much more stable, runs a little bit faster, and the new features are nice too.
I have a reeeeeeeeeeeally old computer too.
Let me know if you need any help, thanx :)
-ken
-
Severe networks problems it saying all day, i reset router ect.. but still saying that and loosing conections
edit 0.9.1 available lets try
-
Running 9.0 and it is far superior in terms of speed and smoothness!
-
Severe networks problems it saying all day, i reset router ect.. but still saying that and loosing conections
edit 0.9.1 available lets try
delete the "chains" folder from your config/data directory
http://wiki.bitshares.org/index.php/BitShares/Config
it will resync the whole blockchain from the seed nodes ..
-
I don't have 16 GB and i7 to try new wallet but I'am sure that these one is best in the whole crypto space. Thank you. I can't wait version 1.0 and new few billions shares more with everything inside.
Happy Angel shares owner
@dritz3r - You will be glad if you upgrade to 0.9.0, it is much more stable, runs a little bit faster, and the new features are nice too.
I have a reeeeeeeeeeeally old computer too.
Let me know if you need any help, thanx :)
-ken
Running 9.0 and it is far superior in terms of speed and smoothness!
Here we go with the useless pumping...
As I said it is upgradable... running it is as pain in the ass as 0.8.0 was.... basically it takes about 100M more memory than 0.8.0 .
Restarting it immediately after you opening it for the first time is a almost obligatory first step. So is restarting it after opening 2 markets (if you are lucky for them to load that is)....
And btw this is supposed to be feedback thread. The devs are fully aware that it is not as smooth and polish as you describe it. If you want to promote some inexistent smoothness in 0.9.0 just open a dedicated pump up thread in the genera area.
-
Severe networks problems it saying all day, i reset router ect.. but still saying that and loosing conections
edit 0.9.1 available lets try
delete the "chains" folder from your config/data directory
http://wiki.bitshares.org/index.php/BitShares/Config
it will resync the whole blockchain from the seed nodes ..
3 hours later,,,, it works! and with spanish languaje too. thanks bro.
-
I have been gradually buying BTS and really want Bitshares to prosper. I also realize that the developers work very hard for very little and I am hesitant to complain. However I am really frustrated by the Windows client installation procedure, and I doubt I am the only one, and I can’t help but think these problems are having a big negative effect on Bitshares adoption. I cringe whenever there is a mandatory upgrade because I know it won’t go smoothly and will inevitably result in me having to download the blockchain yet again thus taking up a lot of time and using up about 30% of my monthly download allowance (I have a satellite connection with monthly download limits). There really needs to be an easy-to-find set of installation instructions with trouble-shooting procedures if something goes wrong.
Here are a few things I have experienced:
When I start the client I get a window that says “Starting Bitshares” but nothing happens even if I wait for a half hour.
I have tried deleting config.json and letting the system recreate it. This has never helped.
I get a Critical Error Message Window: An error occurred while trying to start. Please try restarting the application. This, of course, never helps.
Sometimes it will tell me that my database needs to be re-set. This never seems to help either.
Also, I don’t understand what the “Check for Updates” option. It always says No updates are available, but when the synchronization gets stuck, it’s usually because an upgrade is required, and it turns out that there is an upgrade available.
What I usually end up doing is to:
1) Make a backup copy of C:\Users\MyName\AppData\Roaming\Bitshares
2) Delete the whole C:\Users\MyName\AppData\Roaming\Bitshares folder
3) Start Bitshares client and then close it when it asks me to create a new wallet
4) Copy the wallets subfolder back into: C:\Users\MyName\AppData\Roaming\Bitshares folder
5) Start the client again and wait for it to sync up the blockchain again
6) Make sure that my bitshares balance is the same as it was before the upgrade
-
I am using 0.9.1 now which so far looks nice and works fine.
BUT...Please show the amount of BTS to be released when a position is covered as it was in all previous versions!
-
0.9.1 still has 35005 invalid_asset_amount error, when I try to buy MOONFUND
35005 invalid_asset_amount: invalid asset amount
{"share_string":"0.869412","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"0.869412","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"0.869412"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"0.869412","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"clayop","real_quantity":"0.869412","quantity_symbol":"BTS","quote_price":"1.1500000230000005","quote_symbol":"MOONFUND","sign":true}
bitshares wallet.cpp:3495 bts::wallet::wallet::submit_bid
{}
bitshares common_api_client.cpp:5279 bts::rpc_stubs::common_api_client::wallet_market_submit_bid
-
Expired shorts (cover orders) are matched with new short orders at the feed, even if there is a better buy bitAsset order with better (higher than the feed in BTS/bitAssets) price.
Example - short at the feed submitted/included in block 2,477,701 and 2,477,703
-
0.9.1 still has 35005 invalid_asset_amount error, when I try to buy MOONFUND
35005 invalid_asset_amount: invalid asset amount
{"share_string":"0.869412","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"0.869412","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"0.869412"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"0.869412","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"clayop","real_quantity":"0.869412","quantity_symbol":"BTS","quote_price":"1.1500000230000005","quote_symbol":"MOONFUND","sign":true}
bitshares wallet.cpp:3495 bts::wallet::wallet::submit_bid
{}
bitshares common_api_client.cpp:5279 bts::rpc_stubs::common_api_client::wallet_market_submit_bid
Buy
0.86941
instead of
0.869412
-
there are still problems with the GUI & Delegate votes I guess. not displayed correctly
-
Could the call the feed price be added on graphs on the exchange home page? They currently have high/low/volume listed in the graphs. Or maybe listed in the table below.
-
I am using 0.9.1 now which so far looks nice and works fine.
BUT...Please show the amount of BTS to be released when a position is covered as it was in all previous versions!
I'm not sure I get what you mean, where was this shown?
-
there are still problems with the GUI & Delegate votes I guess. not displayed correctly
I've fixed this this morning, it was due to a change in how accounts are handled in the v0.9.0 release. I also took the time to add sorting by approval as well as a count of how many positive, neutral and negative votes you've selected.
https://github.com/BitShares/web_wallet/issues/693
-
I am using 0.9.1 now which so far looks nice and works fine.
BUT...Please show the amount of BTS to be released when a position is covered as it was in all previous versions!
I'm not sure I get what you mean, where was this shown?
In previous versions when i had an open position to cover i could see the price, the amount of bitusd owed and BTS collateral (that was released upon covering). Now I can see the price and the amount owed so if I want to calculate the amount of BTS to be released I have to multiply the price with the amount x 1.5 to see the BTS to be released..This is not helpful at all and the only reason I can think this was taken out was to save some space..but this is really annoying and I hope it gets changed back as it was..take some space from the graphs and show that amount please..
-
I am using 0.9.1 now which so far looks nice and works fine.
BUT...Please show the amount of BTS to be released when a position is covered as it was in all previous versions!
I'm not sure I get what you mean, where was this shown?
In previous versions when i had an open position to cover i could see the price, the amount of bitusd owed and BTS collateral (that was released upon covering). Now I can see the price and the amount owed so if I want to calculate the amount of BTS to be released I have to multiply the price with the amount x 1.5 to see the BTS to be released..This is not helpful at all and the only reason I can think this was taken out was to save some space..but this is really annoying and I hope it gets changed back as it was..take some space from the graphs and show that amount please..
There's a tooltip though that shows the collateral.
-
What is a tooltip? Where can I see that? Maybe I missed it so I will check next time when I login..
Thanks svk
-
What is a tooltip? Where can I see that? Maybe I missed it so I will check next time when I login..
Thanks svk
A tooltip is a popup with more information when you move the mouse over an item. There should be one when you move the mouse over the row of an open margin order.
-
Not sure if this has been mentions,
When you are in the exchange section and switch to an unregistered account, it changes to the summary page of the unregistered account instead of staying in the exchange.
-
What is a tooltip? Where can I see that? Maybe I missed it so I will check next time when I login..
Thanks svk
A tooltip is a popup with more information when you move the mouse over an item. There should be one when you move the mouse over the row of an open margin order.
I can see that now..Haven't noticed that...So it's all good!! ;)
Thanks
-
Migrating my wallet to a new computer.
Begun two days ago.
6 hangs at seemingly random blocks, cpu fan banging loudly and no apparent progress.
4 times input password and the dots animation keeps on going for 10 mins, at which point I manually kill the process.
Only 14 days left to sync now, and the balance is horribly wrong.
This is Debian 8/x86_64.
Just.... >:(
-
0.9.1 still has 35005 invalid_asset_amount error, when I try to buy MOONFUND
35005 invalid_asset_amount: invalid asset amount
{"share_string":"0.869412","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"0.869412","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"0.869412"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"0.869412","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"clayop","real_quantity":"0.869412","quantity_symbol":"BTS","quote_price":"1.1500000230000005","quote_symbol":"MOONFUND","sign":true}
bitshares wallet.cpp:3495 bts::wallet::wallet::submit_bid
{}
bitshares common_api_client.cpp:5279 bts::rpc_stubs::common_api_client::wallet_market_submit_bid
Buy
0.86941
instead of
0.869412
I get the same error when I try to vote (i.e. when I press the "Vote" button in the "Vote" tab of one my accounts).
This prevents me from voting.
Is there a workaround for this in version 0.9.1?
-
I get the same error when I try to vote (i.e. when I press the "Vote" button in the "Vote" tab of one my accounts).
This prevents me from voting.
Is there a workaround for this in version 0.9.1?
I gave up on the thumbs up thing, it's tough to tell if it stuck or not.
I just do this:
Open Wallet > Advanced > Console > approve delegate.kencode true
Just edit delegate.kencode to whomever you want to vote for. Change true to false if you want to downvote a delegate.
Hope that helps :)
-ken
-
I get the same error when I try to vote (i.e. when I press the "Vote" button in the "Vote" tab of one my accounts).
This prevents me from voting.
Is there a workaround for this in version 0.9.1?
I gave up on the thumbs up thing, it's tough to tell if it stuck or not.
I just do this:
Open Wallet > Advanced > Console > approve delegate.kencode true
Just edit delegate.kencode to whomever you want to vote for. Change true to false if you want to downvote a delegate.
Hope that helps :)
-ken
Thanks Ken.
And after I've done the console command you suggested - do I need to send my BTS to myself on each of my accounts to apply the vote?
I could say that the current implementation of the voting process in the GUI is just a terrible guessing game for the user.
But I will not say that.
Instead I will say this: just imagine how much of the voting apathy will be gone once we have it properly implemented in 1.0 GUI (hopefully).
-
Thanks Ken.
And after I've done the console command you suggested - do I need to send my BTS to myself on each of my accounts to apply the vote?
I could say that the current implementation of the voting process in the GUI is just a terrible guessing game for the user.
But I will not say that.
Instead I will say this: just imagine how much of the voting apathy will be gone once we have it properly implemented in 1.0 GUI (hopefully).
No need to transfer any BTS, the vote will stick as soon as you cast it.
The voting is a mess, agreed. Accountability here is a mess. Too much complaining, laziness and not enough action...
I am working hard to make this company unbeatable though.
Hang in there jakub please, I'm not giving up just yet. I'm doing everything I can to show people what needs to be done around here to start growing this DAC. Like fuzzy said, I'm the "chicken with his head cut off".
-
Thanks Ken.
And after I've done the console command you suggested - do I need to send my BTS to myself on each of my accounts to apply the vote?
I could say that the current implementation of the voting process in the GUI is just a terrible guessing game for the user.
But I will not say that.
Instead I will say this: just imagine how much of the voting apathy will be gone once we have it properly implemented in 1.0 GUI (hopefully).
No need to transfer any BTS, the vote will stick as soon as you cast it.
The voting is a mess, agreed. Accountability here is a mess. Too much complaining, laziness and not enough action...
I am working hard to make this company unbeatable though.
Hang in there jakub please, I'm not giving up just yet. I'm doing everything I can to show people what needs to be done around here to start growing this DAC. Like fuzzy said, I'm the "chicken with his head cut off".
On the contrary, you need to either manually make a transfer to yourself or use the vote now button (which is just a shortcut for making a transfer of your entire balance to yourself) after having approved the delegates you want.
I've fixed the broken thumbs up/down in the develop branch but it's not live yet unfortunately.
-
Thanks Ken.
And after I've done the console command you suggested - do I need to send my BTS to myself on each of my accounts to apply the vote?
I could say that the current implementation of the voting process in the GUI is just a terrible guessing game for the user.
But I will not say that.
Instead I will say this: just imagine how much of the voting apathy will be gone once we have it properly implemented in 1.0 GUI (hopefully).
No need to transfer any BTS, the vote will stick as soon as you cast it.
The voting is a mess, agreed. Accountability here is a mess. Too much complaining, laziness and not enough action...
I am working hard to make this company unbeatable though.
Hang in there jakub please, I'm not giving up just yet. I'm doing everything I can to show people what needs to be done around here to start growing this DAC. Like fuzzy said, I'm the "chicken with his head cut off".
On the contrary, you need to either manually make a transfer to yourself or use the vote now button (which is just a shortcut for making a transfer of your entire balance to yourself) after having approved the delegates you want.
I've fixed the broken thumbs up/down in the develop branch but it's not live yet unfortunately.
Thanks, svk.
I'll have to do it manually because it's the vote button where my problem started - it fails to perform with the 35005 invalid_asset_amount error.
(The manual way might be a bit scary thing to do if you have a bigger balance)
When do you expect to release an upgrade with the 35005 error fixed?
-
...........
I'll have to do it manually because it's the vote button where my problem started - it fails to perform with the 35005 invalid_asset_amount error.
...........
Same here - 0.9.1. / WIN 7/64 - only one account affected.
-
Migrating my wallet to a new computer.
Begun two days ago.
6 hangs at seemingly random blocks, cpu fan banging loudly and no apparent progress.
4 times input password and the dots animation keeps on going for 10 mins, at which point I manually kill the process.
Only 14 days left to sync now, and the balance is horribly wrong.
This is Debian 8/x86_64.
Just.... >:(
Did you self-compile or use a precompiled version? I have created a BitShares package for Debian-8 (among others), see the link in my .signature.
I think the general suggestion is to use the CLI version for syncing. Let it download the chain, and only then open and unlock your wallet.
-
I compiled and then stripped the (300MB) binary.
-
Client is much more stable, UI is looking great, just two issues bother me:
1. The price graph scrolls on its own and follows my cursor. Sometimes it dances around for a while when I simply leave the cursor over it.
2. My transaction history does not show (this is not new in 0.9). Relevant error:
2015-05-18T18:38:34 th_a:?unnamed? log_message ] Message from GUI: rpc error: JSON Parse error: Unterminated string (undefined)
Utilities.cpp:36
2015-05-18T18:38:44 bitshares:rebroadcast_pending rebroadcast_pending_ ] rebroadcasting 0 client.cpp:730
2015-05-18T18:38:44 th_a:?unnamed? log_message ] Message from GUI: js error: JSON Parse error: Unterminated string
parse@[native code]
○ S@http://localhost/js/app.js:5:1792
○ ec@http://localhost/js/app.js:6:4265
○ http://localhost/js/app.js:6:4692
○ f@http://localhost/js/app.js:4:59285
○ ic@http://localhost/js/app.js:6:4674
○ e@http://localhost/js/app.js:6:10036
○ i@http://localhost/js/app.js:6:46035
○ http://localhost/js/app.js:6:46207
○ $eval@http://localhost/js/app.js:6:82585
○ $digest@http://localhost/js/app.js:6:81099
○ $apply@http://localhost/js/app.js:6:82859
○ f@http://localhost/js/app.js:6:16838
○ r@http://localhost/js/app.js:6:25617
○ onload@http://localhost/js/app.js:6:26157 Utilities.cpp:36
2015-05-18T18:38:44 th_a:?unnamed? log_message ] Message from GUI: rpc error: JSON Parse error: Unterminated string (undefined)
Utilities.cpp:36
-
I have some concerns about the bts/0.9.2 release as I do not see the code previously released to the dvs/0.9.x network for testing. It is my understanding that all code in BitShares will go through DevShares first for testing.
DevShares:
20 APR 2015 | Latest commit [1]
BitShares:
18 MAY 2015 | bts/0.9.2 [2]
04 MAY 2015 | bts/0.9.1
24 APR 2015 | bts/0.9.0
Request:
Please help me understand the decision process used to release the bts/0.9.2 code into the BitShares network.
References:
[1] https://github.com/BitShares/DevShares/commits/master
[2] https://github.com/BitShares/bitshares/commits/master
-
It is my understanding that all code in BitShares will go through DevShares first for testing.
I'm not sure if this is related to the dev's currently doing everything in private, but it could be. I'm sure you'll get a better answer soon.
-
In v.0.9.2 on Windows 7 when you navigate to Delegates->My Votes and start playing with the thumb up/down icon the list of delegates goes "crazy" - the items on the delegate list get duplicated several times.
Reloading the page (with a right-click) sometimes helps and navigating away from this page and coming back to it always helps so I guess this is purely a display issue.
(and I can see that the "invalid asset amount" error is still there which in some cases prevents people from being able to vote, please fix it if it's possible in this release)
-
In v.0.9.2 on Windows 7 when you navigate to Delegates->My Votes and start playing with the thumb up/down icon the list of delegates goes "crazy" - the items on the delegate list get duplicated several times.
Reloading the page (with a right-click) sometimes helps and navigating away from this page and coming back to it always helps so I guess this is purely a display issue.
(and I can see that the "invalid asset amount" error is still there which in some cases prevents people from being able to vote, please fix it if it's possible in this release)
The first one is a stupid error on my part, I'll fix it when I get home.
Edit: For now please just use the delegates overview tables to adjust votes, not the "My Votes" tab, they should work.
-
I have some concerns about the bts/0.9.2 release as I do not see the code previously released to the dvs/0.9.x network for testing. It is my understanding that all code in BitShares will go through DevShares first for testing.
DevShares:
20 APR 2015 | Latest commit [1]
BitShares:
18 MAY 2015 | bts/0.9.2 [2]
04 MAY 2015 | bts/0.9.1
24 APR 2015 | bts/0.9.0
Request:
Please help me understand the decision process used to release the bts/0.9.2 code into the BitShares network.
References:
[1] https://github.com/BitShares/DevShares/commits/master
[2] https://github.com/BitShares/bitshares/commits/master
DevShares is a tool to help prevent problems with BitShares upgrades. It is not a perfect tool, and cannot help with some parts of the upgrade process because the DevShares network has a completely different state from the BitShares network, and hardforks happen at different times between the two networks. So we use this tool at our discretion, but by definition the code will never be exactly the same between the two networks.
In particular, the BitShares 0.9.2 release contains changes to code which is not executed in DevShares: https://github.com/BitShares/bitshares/compare/bts/0.9.1...bts/0.9.2
-
DevShares is a tool to help prevent problems with BitShares upgrades. It is not a perfect tool, and cannot help with some parts of the upgrade process because the DevShares network has a completely different state from the BitShares network, and hardforks happen at different times between the two networks. So we use this tool at our discretion, but by definition the code will never be exactly the same between the two networks.
In particular, the BitShares 0.9.2 release contains changes to code which is not executed in DevShares: https://github.com/BitShares/bitshares/compare/bts/0.9.1...bts/0.9.2
@vikram Your reply is quite helpful in allowing me to see the identified changes and why they in fact must be different in each network.
Respectfully,
Fox
-
In v.0.9.2 on Windows 7 when you navigate to Delegates->My Votes and start playing with the thumb up/down icon the list of delegates goes "crazy" - the items on the delegate list get duplicated several times.
Reloading the page (with a right-click) sometimes helps and navigating away from this page and coming back to it always helps so I guess this is purely a display issue.
(and I can see that the "invalid asset amount" error is still there which in some cases prevents people from being able to vote, please fix it if it's possible in this release)
The first one is a stupid error on my part, I'll fix it when I get home.
Edit: For now please just use the delegates overview tables to adjust votes, not the "My Votes" tab, they should work.
I assume there will be 0.9.2b or something soon?
-
.....
(and I can see that the "invalid asset amount" error is still there which in some cases prevents people from being able to vote, please fix it if it's possible in this release)
Is there some workaround to this voting problem ? I would like to vote for some delegates but this error is blocking one account for quite some time now.
-
.....
(and I can see that the "invalid asset amount" error is still there which in some cases prevents people from being able to vote, please fix it if it's possible in this release)
Is there some workaround to this voting problem ? I would like to vote for some delegates but this error is blocking one account for quite some time now.
console
(http://i.imgur.com/3HjF1k8.png)
"wallet_list_approvals" lists your current votings
-
.....
(and I can see that the "invalid asset amount" error is still there which in some cases prevents people from being able to vote, please fix it if it's possible in this release)
Is there some workaround to this voting problem ? I would like to vote for some delegates but this error is blocking one account for quite some time now.
console
(http://i.imgur.com/3HjF1k8.png)
"wallet_list_approvals" lists your current votings
And after using the console as favdesu described remember to go to each of your accounts and transfer your BTS balance to yourself.
More details in this thread:
https://bitsharestalk.org/index.php/topic,16435.msg210132.html#msg210132
-
.....
(and I can see that the "invalid asset amount" error is still there which in some cases prevents people from being able to vote, please fix it if it's possible in this release)
Is there some workaround to this voting problem ? I would like to vote for some delegates but this error is blocking one account for quite some time now.
console
(http://i.imgur.com/3HjF1k8.png)
"wallet_list_approvals" lists your current votings
And after using the console as favdesu described remember to go to each of your accounts and transfer your BTS balance to yourself.
More details in this thread:
https://bitsharestalk.org/index.php/topic,16435.msg210132.html#msg210132
Thank you - I will give it a try - for each one separately :)
-
for short order less than feed price, the volume display from GUI is wrong.
for example
106.2828 USD 50,000.00000 BTS 0.020000 % 0.0035 USD / BTS c09249efbc97c1f39c95158b12b2fa66c0ca7e99
the volume should be 25,000 BTS, and the ammount should be 25000 * 0.0035 = 87.5 USD
but the GUI display 106.78 USD
-
for short order less than feed price, the volume display from GUI is wrong.
for example
106.2828 USD 50,000.00000 BTS 0.020000 % 0.0035 USD / BTS c09249efbc97c1f39c95158b12b2fa66c0ca7e99
the volume should be 25,000 BTS, and the ammount should be 25000 * 0.0035 = 87.5 USD
but the GUI display 106.78 USD
and if you reverse the market, there is another problem for short order
it display amount(USD) as volume(BTS)
-
1. I want to know how much "shorts" i have. At the moment i have to count them manually - crazy. So let's sum them up!!!
2. I want to have how much collateral i used, so also count them together.
-
please display the quantity of unlocked &locked vested bts in account page 【use play’code】
https://github.com/BitShares/web_wallet/issues/695
-
please display the quantity of unlocked &locked vested bts in account page 【use play’code】
https://github.com/BitShares/web_wallet/issues/695
why not?
-
please display the quantity of unlocked &locked vested bts in account page 【use play’code】
https://github.com/BitShares/web_wallet/issues/695
why not?
like this approach!
-
please display the quantity of unlocked &locked vested bts in account page 【use play’code】
https://github.com/BitShares/web_wallet/issues/695
why not?
like this approach!
+5%
-
any update plan???
-
any update plan???
Development of 0.x series is on hold while 2.0 is developed. I will put out maintenance releases of 0.x series for any serious bugs that are found.