BTSX 0.4.8-a Known Issues Status Update

[doxymoron]

In Market trading, when you click your Balance value it will autofill the Quantity field value with comma (3,500.000), but the comma is not valid in the field.

Second this.  Was frustrating me for a while.

[xeroc]

Yes, they will have to be signed by DAC Sun Limited.

To be honest .. I was 100% sure you would answer like that :-) thanks for the confirmation anyway :)

[bytemaster]

some kind of auto-updating for the wallet would simplify user experience million-fold at this rate of new releases

Auto-update feature is implemented for GUI.  This will allow developers to notify users that an upgrade is available.  It will also allow us to fix GUI bugs without having to make a release, much closer to a web-site upgrade than it is now.

I hope you made those "gui updates" signed cryptographically ..

Yes, they will have to be signed by DAC Sun Limited.

[xeroc]

some kind of auto-updating for the wallet would simplify user experience million-fold at this rate of new releases

Auto-update feature is implemented for GUI.  This will allow developers to notify users that an upgrade is available.  It will also allow us to fix GUI bugs without having to make a release, much closer to a web-site upgrade than it is now.

I hope you made those "gui updates" signed cryptographically ..

[bytemaster]

some kind of auto-updating for the wallet would simplify user experience million-fold at this rate of new releases

Auto-update feature is implemented for GUI.  This will allow developers to notify users that an upgrade is available.  It will also allow us to fix GUI bugs without having to make a release, much closer to a web-site upgrade than it is now.

[CLains]

some kind of auto-updating for the wallet would simplify user experience million-fold at this rate of new releases

[joele]

In Market trading, when you click your Balance value it will autofill the Quantity field value with comma (3,500.000), but the comma is not valid in the field.

[biophil]

When do we expect the next version to come out? I've never been able to get 0.4.8-a to work. I'm on Windows 7 SP1. I rescanned, after which the program crashes every time I try to open it. Then I took the little dialog box's advice to rebuild the database, and had that going overnight. I woke up in the morning to a crash report waiting for me to send.

Soon I'll see if I had any more luck on my work computer, but for now it looks like I'm on the sidelines until a less crashy version is released.

Have you tried running it in Windows XP compatibility mode?

Hm, have not tried that yet. I'll give it a look.

Sent from my SCH-S720C using Tapatalk 2

[robrigo]

When do we expect the next version to come out? I've never been able to get 0.4.8-a to work. I'm on Windows 7 SP1. I rescanned, after which the program crashes every time I try to open it. Then I took the little dialog box's advice to rebuild the database, and had that going overnight. I woke up in the morning to a crash report waiting for me to send.

Soon I'll see if I had any more luck on my work computer, but for now it looks like I'm on the sidelines until a less crashy version is released.

Have you tried running it in Windows XP compatibility mode?

[biophil]

When do we expect the next version to come out? I've never been able to get 0.4.8-a to work. I'm on Windows 7 SP1. I rescanned, after which the program crashes every time I try to open it. Then I took the little dialog box's advice to rebuild the database, and had that going overnight. I woke up in the morning to a crash report waiting for me to send.

Soon I'll see if I had any more luck on my work computer, but for now it looks like I'm on the sidelines until a less crashy version is released.

[Overthetop]

I increased connections to my seed node and my demo-wallet.  Try

Code Select Expand


network_add_node "95.85.33.16:8764"
network_add_node "104.131.238.223:1776"

Start syncing.... thanks  :)

[puppies]

I increased connections to my seed node and my demo-wallet.  Try

Code Select Expand


network_add_node "95.85.33.16:8764"
network_add_node "104.131.238.223:1776"

[Overthetop]

no connnections yet with the additional nodes...

[emski]

Code Select Expand

network_add_node "84.238.140.192:42577" add
Sorry I forgot the whole command line. Use the one above.

[cryptkeeper]

can not get any connections while using BTSX 0.4.8-a

network_add_node "107.170.30.182:1776"

do not work....

network_add_node "84.238.140.192:42577"

I've greatly increased max network connections.
You should be ok now.

sorry to barge in, I tried that add node and got an error in the console. I may be typing wrong. do you type it exactly the same way?

[sudo]

1) UNKNOWN recipients in transaction history.
2) 1hr Avg Price not displayed properly in GUI
3) Sometimes nodes get stuck on a fork when a delegate double produces
4) There is still a random crash when network connections are closed (we are very close to having that one nailed down... it was quiet a rabbit hole)
5) I suspect that you may still need to run it in Win XP Service Pack 3 compatibility mode
6) RPC "Key Not Found" -  this happens when you are re-syncing to the blockchain with a wallet that has newer transactions, it will clear up on its own.

:'( i create a new wallet
import my privatekey of one id
rescan&wallet_rescan_blockchain is very slow
and the bill   last night i short USD @ 32BTS/USD  in market   is missing

[麥可貓]

When I click on BitUSD:BTSX market it will hang.. with the three loading circles. 0.4.8 on Ubuntu.

I am having same issues. Tried git pull master, same result.

I am having the same issue in 0.4.8 and 0.4.8a

and during this long long waiting, the BitSharesX process occupied up to 6G of ram

[cygnify]

When I click on BitUSD:BTSX market it will hang.. with the three loading circles. 0.4.8 on Ubuntu.

I am having same issues. Tried git pull master, same result.

git pull https://github.com/dacsunlimited/bitsharesx.git master

thats what worked for me.

[bitcoinerS]

When I click on BitUSD:BTSX market it will hang.. with the three loading circles. 0.4.8 on Ubuntu.

I am having same issues. Tried git pull master, same result.

[cygnify]

git pull https://github.com/dacsunlimited/bitsharesx.git 0.4.8-a ?? Is that correct?

[emski]

can not get any connections while using BTSX 0.4.8-a

network_add_node "107.170.30.182:1776"

do not work....

network_add_node "84.238.140.192:42577"

I've greatly increased max network connections.
You should be ok now.

[Overthetop]

can not get any connections while using BTSX 0.4.8-a

network_add_node "107.170.30.182:1776"

do not work....

[bytemaster]

can not get any connections while using BTSX 0.4.8-a

network_add_node "107.170.30.182:1776"

[Overthetop]

can not get any connections while using BTSX 0.4.8-a

and get one error about: 

RPC Server Error: in method:'wallet_get_info': Key not found(6)

[bytemaster]

When I click on BitUSD:BTSX market it will hang.. with the three loading circles...

I have this problem too on Win 7 - must restart after this happens.

The 0.4.8-a release fixed this problem, if you are just using 0.4.8 then you will experience that.

[sschechter]

When I click on BitUSD:BTSX market it will hang.. with the three loading circles...

I have this problem too on Win 7 - must restart after this happens.

[liondani]

Linux VPS which is running my delegate is super fine, there is about 100 connections. But WIN GUI only has 1 or 2 connections, weird.

Yep windows gui has 1-2 connections, linux is ok...

[cygnify]

When I click on BitUSD:BTSX market it will hang.. with the three loading circles. 0.4.8 on Ubuntu. Noticed it was harder to get connection count high on this version. Tried restarting, same problem.
Nothing major, just reporting.

EDIT: restarted again and 5 connections straight away.

[bytemaster]

The limiting algorithm is   average price * 10 / 9... average price gets updated every time a trade occurs...  this limits new shorts, but strait up USD vs BTSX can trade at any price.   This is a birthing problem... working to increase the average price.

The minimum short price should be in the GUI.  I need to take a while to think about the economic implications of this limiting scheme and possible failure modes...

The main failure mode is that LONGS have an advantage of SHORTS in this situation... however, if there are not enough longs willing to trade then the market can "freeze" with no trades occurring and the average price would be stuck.

[theoretical]

The limiting algorithm is   average price * 10 / 9... average price gets updated every time a trade occurs...  this limits new shorts, but strait up USD vs BTSX can trade at any price.   This is a birthing problem... working to increase the average price.

The minimum short price should be in the GUI.  I need to take a while to think about the economic implications of this limiting scheme and possible failure modes...

[cryptkeeper]

ok its connecting now. thanks for the response.

[bytemaster]

In the web wallet, I'm getting "Order failed:  Assert Exception (10) short_index.order_price < market_stat->maximum_bid();" when trying to place a short at a price equal to the top bid (currently $21.00 / BTSX).

In the past, there's been some discussion on this forum about locking the price to within a certain range of delegate price feeds and/or some form of rate limiting on price changes.  I'm thinking I might be running up against some limitation like that.

But I'm not sure what limiting algorithm was actually implemented, or where the current limit is displayed.

The limiting algorithm is   average price * 10 / 9... average price gets updated every time a trade occurs...  this limits new shorts, but strait up USD vs BTSX can trade at any price.   This is a birthing problem... working to increase the average price.

[bytemaster]

same here I can't connect to 0.4.8 a either. can I go back to 0.4.8?

There is no difference in the backend code between 0.4.8 and 4.8-a... the issue is the seed nodes limiting connection count. 

[theoretical]

In the web wallet, I'm getting "Order failed:  Assert Exception (10) short_index.order_price < market_stat->maximum_bid();" when trying to place a short at a price equal to the top bid (currently $21.00 / BTSX).

In the past, there's been some discussion on this forum about locking the price to within a certain range of delegate price feeds and/or some form of rate limiting on price changes.  I'm thinking I might be running up against some limitation like that.

But I'm not sure what limiting algorithm was actually implemented, or where the current limit is displayed.

[yinchanggong]

Linux VPS which is running my delegate is super fine, there is about 100 connections. But WIN GUI only has 1 or 2 connections, weird.

[bytemaster]

Can't connect. Opened a new VPS and only getting 1 connection and it's taking forever to catch up.

Anyone else having this issue? It was fine until I updated to 0.4.8-a


*now I am getting 4 connections.

New seed nodes are coming on line as we speak.. connections were getting full.

[cryptkeeper]

same here I can't connect to 0.4.8 a either. can I go back to 0.4.8?

[Riverhead]

Can't connect. Opened a new VPS and only getting 1 connection and it's taking forever to catch up.

Anyone else having this issue. It was fine until I updated to 0.4.8-a

Could be you're connected to a chain server. Mine stayed like that for a while.

[Ggozzo]

Can't connect. Opened a new VPS and only getting 1 connection and it's taking forever to catch up.

Anyone else having this issue? It was fine until I updated to 0.4.8-a


*now I am getting 4 connections.

[tonyk]

win7/ 32 bit;
All 3 after rescan.

1.Median price is 0 in the GUI

2.Below is the result of (clicking on ) transaction link in the GUI


-----------------------------
Transaction #8cda348a

Block # , transaction # , next #0
Timestamp:

Deposits
Withdraws
Fee
Net Delegate Approval Update
Operations:
---------------------------------------------------------------------

3.Right mouse button not working (again).

[bytemaster]

1) UNKNOWN recipients in transaction history.
2) 1hr Avg Price not displayed properly in GUI
3) Sometimes nodes get stuck on a fork when a delegate double produces
4) There is still a random crash when network connections are closed (we are very close to having that one nailed down... it was quiet a rabbit hole)
5) I suspect that you may still need to run it in Win XP Service Pack 3 compatibility mode
6) RPC "Key Not Found" -  this happens when you are re-syncing to the blockchain with a wallet that has newer transactions, it will clear up on its own.