New Mandatory Upgrade

[evolvo]

and surprise surprise...it's not working...not connecting at all...groan

maybe wait a little bit?

waited 20 minutes...its an error....RPC Server Error: In method 'blockchain_list_assets': Assert Exception (10)

[liondani]

and surprise surprise...it's not working...not connecting at all...groan

maybe wait a little bit?

[evolvo]

and surprise surprise...it's not working...not connecting at all...groan

[joele]

exe 0.4.9 is now available

[jwiz168]

I honestly hope these UNKNOWN bugs will go away . Its been on my wallet and I can not do  transactions further to lose even more BTSX. Its hopeless.

[Troglodactyl]

will exe. be available or does it even matter which one you download?

Generally they build and post the .exes immediately after the others, it seems, I expect that will be up shortly.

https://github.com/dacsunlimited/bitsharesx/releases

[cryptkeeper]

will exe. be available or does it even matter which one you download?

[tonyk]

It is fine, believe me. Read mine or toast's post above.

Now the only problem is that from 'account manager' you will have to become also a BTSX 'lender'. :)
That if you want to close the position relatively soon.

[liondani]

SOS

I managed on a account I have 1000 BTSX to short 30 bitUSD that needed 1449 BTSX as a collateral (?)  (price 24.15)
I thought 2X collateral was neccesary to have as a minimum! How has the system accepted the order without the needed collateral ??

First stop playing with a market that is waiting a fork...ok mandatory update

Second, the second part of the collateral comes from the sell proceeds.

How you ganna buy those  30 bitUSD back is a different story.

how is this supposed to work when the collateral is not guaranteed...  it seems the needed collateral is in reality 1:1  ....

[liondani]

SOS

I managed on a account I have 1000 BTSX to short 30 bitUSD that needed 1449 BTSX as a collateral (?)  (price 24.15)
I thought 2X collateral was neccesary to have as a minimum! How has the system accepted the order without the needed collateral ??

I think the rest comes from the bid?

the bid is about 700 btsx...  so no... I have left 280 btsx + the short order..   

[tonyk]

SOS

I managed on a account I have 1000 BTSX to short 30 bitUSD that needed 1449 BTSX as a collateral (?)  (price 24.15)
I thought 2X collateral was neccesary to have as a minimum! How has the system accepted the order without the needed collateral ??

First stop playing with a market that is waiting a fork...ok mandatory update

Second, the second part of the collateral comes from the sell proceeds.

How you ganna buy those  30 bitUSD back is a different story.

[toast]

SOS

I managed on a account I have 1000 BTSX to short 30 bitUSD that needed 1449 BTSX as a collateral (?)  (price 24.15)
I thought 2X collateral was neccesary to have as a minimum! How has the system accepted the order without the needed collateral ??

I think the rest comes from the bid?

[liondani]

SOS

I managed on a account I have 1000 BTSX to short 30 bitUSD that needed 1449 BTSX as a collateral (?)  (price 24.15)
I thought 2X collateral was neccesary to have as a minimum! How has the system accepted the order without the needed collateral ??

[tonyk]

There is an order before yours which eats up the opposing order. i.e your order is actually the second

[Edit] What needs fixing is the  'display bug' - what I mean by this is - after the two orders are matched the bid order will disappear but the amount in the short (in this case) will stay the same '600' bitUSD.

Now I understand. It is very confusing with this "display bug"... + it would be great to have a message from the system like: "wait to match orders with the same value as yours that have priority" or something like this...

It is not cool that "display bug" affects also your pending orders... that being said I discovered like 20 bugs and/or incontinences. I did not want to state them all out, as they are not top priority IMHO.

[liondani]

There is an order before yours which eats up the opposing order. i.e your order is actually the second

[Edit] What needs fixing is the  'display bug' - what I mean by this is - after the two orders are matched the bid order will disappear but the amount in the short (in this case) will stay the same '600' bitUSD.

Now I understand. It is very confusing with this "display bug"... + it would be great to have a message from the system like: "wait to match orders with the same value as yours that have priority" or something like this...

[mavisjames]

same bid and ask/short orders...
even it seems they exist the bid order for bitUSD I couldn't sell my bitUSDs in that price so I canceled the order  :(

have you fixed that?

There is an order before yours which eats up the opposing order. i.e your order is actually the second

[Edit] What needs fixing is the  'display bug' - what I mean by this is - after the two orders are matched the bid order will disappear but the amount in the short (in this case) will stay the same '600' bitUSD.

Yes, that is one issue. However the order that he is referring to sat at the top of the list for a solid 2 hours. It just cleared now.

[tonyk]

same bid and ask/short orders...
even it seems they exist the bid order for bitUSD I couldn't sell my bitUSDs in that price so I canceled the order  :(

have you fixed that?

There is an order before yours which eats up the opposing order. i.e your order is actually the second

[Edit] What needs fixing is the  'display bug' - what I mean by this is - after the two orders are matched the bid order will disappear but the amount in the short (in this case) will stay the same '600' bitUSD.

[cygnify]

Its got something to do with them not matching because of the decimal points I believe. Because if you put the last decimal point one higher it will always work.

Which could have something to do with the price when it was entered, ie if it was in bitUSD to BTSX or if it was in BTSX to bitUSD to begin with (when you flip the market).

[mavisjames]

Noticed the same thing Liondani. Seems the order is stuck there. I tried to clear it a few times

[liondani]

same bid and ask/short orders...
even it seems they exist the bid order for bitUSD I couldn't sell my bitUSDs in that price so I canceled the order  :(

have you fixed that?

[mavisjames]

We have identified and fixed an issue with the market execution that will require all users to upgrade.  A DAC Sun Limited is preparing a release.

This update has addressed some critical issues:
1) The 1hr moving average could get "stuck" if the price moves too fast and no trades occur to trigger an update.  We have adjusted it so that if no trades occur the average will gradually adjust on its own over 6 hours. 

2) We fixed the bug that generate the Assert exception during market execution.

3) We have fixed a bug that would cause seed nodes or locked wallets to get stuck on a fork.

4) Many other small fixes.

Still left to be resolved:
1) random crash on closing a connection.
    - work arounds: 
        - seed nodes, auto relaunch with shell script
        - delegates:  don't allow incoming connections
    - Dan & Eric have made great progress on solving this bug, but the source of the bug is "deep & involved"

eta?

[CoinHoarder]

Will it fix the UNKNOWN bug? This is the cause I have lost my BTSX and BitUSD . Still a problem on ver 0.4.8 b

Try this: https://bitsharestalk.org/index.php?topic=7768.0

[jwiz168]

Will it fix the UNKNOWN bug? This is the cause I have lost my BTSX and BitUSD . Still a problem on ver 0.4.8 b

[svk]

I have to get to bed, work calls in the morning, will upgrade first thing when I wake up..

[puppies]

Still left to be resolved:
1) random crash on closing a connection.
    - work arounds: 
        - delegates:  don't allow incoming connections

how?

--accept-incoming-connections=0

[svk]

Any ETA on this? It's already 30 minutes past midnight here so I hope it'll be soon!

[ripplexiaoshan]

Is the "open order disappear" bug fixed? It seems more and more people are reporting this bug besides me.
https://bitsharestalk.org/index.php?topic=7275.0
https://bitsharestalk.org/index.php?topic=7696.0
https://bitsharestalk.org/index.php?topic=7744.0

[bitcoinerS]

Still left to be resolved:
1) random crash on closing a connection.
    - work arounds: 
        - delegates:  don't allow incoming connections

how?

[speedy]

So is this upgrade going to be 0.4.9 ?

Yes

Love you man.

[alt]

+5%

来自我的 HUAWEI P7-L00 上的 Tapatalk

[bytemaster]

So is this upgrade going to be 0.4.9 ?

Yes

[speedy]

So is this upgrade going to be 0.4.9 ?

[bytemaster]

1) The 1hr moving average could get "stuck" if the price moves too fast and no trades occur to trigger an update.  We have adjusted it so that if no trades occur the average will gradually adjust on its own over 6 hours. 

Was wondering how 1hr moving average would fair through huge price movements.  Given that 1hr moving average is based on internal executed prices, how does the average gradually adjust?  Curious about the mechanics of this.

Every time there is a trade I use the following equation:

NEXT_AVG_PRICE = (CURRENT_AVG_PRICE * (BLOCKS_PER_HOUR-1) + BID + ASK) / (BLCOKS_PER_HOUR+1) )

BID and ASK price are bounded to +/- 10% CURRENT_AVG_PRICE

The change we made was to assume a trade is made at least once per minute even if there were no trades. 

[Bitcoinfan]

1) The 1hr moving average could get "stuck" if the price moves too fast and no trades occur to trigger an update.  We have adjusted it so that if no trades occur the average will gradually adjust on its own over 6 hours. 

Was wondering how 1hr moving average would fair through huge price movements.  Given that 1hr moving average is derived from internal executed prices, how does the average gradually adjust?  Curious about the mechanics of this. 

[xeroc]

We have identified and fixed an issue with the market execution that will require all users to upgrade.  A DAC Sun Limited is preparing a release.

This update has addressed some critical issues:
1) The 1hr moving average could get "stuck" if the price moves too fast and no trades occur to trigger an update.  We have adjusted it so that if no trades occur the average will gradually adjust on its own over 6 hours. 

2) We fixed the bug that generate the Assert exception during market execution.

3) We have fixed a bug that would cause seed nodes or locked wallets to get stuck on a fork.

4) Many other small fixes.

Still left to be resolved:
1) random crash on closing a connection.
    - work arounds: 
        - seed nodes, auto relaunch with shell script
        - delegates:  don't allow incoming connections
    - Dan & Eric have made great progress on solving this bug, but the source of the bug is "deep & involved" 

+5% +5% +5%

Thanks for your hard work ... I know (just a little, but I know) how shi**** difficult it can be to debug  ... thanks alot!!

[bytemaster]

We have identified and fixed an issue with the market execution that will require all users to upgrade.  A DAC Sun Limited is preparing a release.

This update has addressed some critical issues:
1) The 1hr moving average could get "stuck" if the price moves too fast and no trades occur to trigger an update.  We have adjusted it so that if no trades occur the average will gradually adjust on its own over 6 hours. 

2) We fixed the bug that generate the Assert exception during market execution.

3) We have fixed a bug that would cause seed nodes or locked wallets to get stuck on a fork.

4) Many other small fixes.

Still left to be resolved:
1) random crash on closing a connection.
    - work arounds: 
        - seed nodes, auto relaunch with shell script
        - delegates:  don't allow incoming connections
    - Dan & Eric have made great progress on solving this bug, but the source of the bug is "deep & involved"