0 Members and 1 Guest are viewing this topic.
Quote from: evolvo on August 28, 2014, 07:27:40 amand surprise surprise...it's not working...not connecting at all...groanmaybe wait a little bit?
and surprise surprise...it's not working...not connecting at all...groan
will exe. be available or does it even matter which one you download?
Quote from: liondani on August 28, 2014, 01:44:23 amSOSI 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 updateSecond, the second part of the collateral comes from the sell proceeds.How you ganna buy those 30 bitUSD back is a different story.
SOSI 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 ??
Quote from: liondani on August 28, 2014, 01:44:23 amSOSI 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?
Quote from: TheOnion on August 28, 2014, 12:41:12 amThere 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...
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.
Quote from: liondani on August 28, 2014, 12:34:37 amsame 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.
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?
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"
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
Quote from: bytemaster on August 27, 2014, 09:17:59 pmStill left to be resolved:1) random crash on closing a connection. - work arounds: - delegates: don't allow incoming connections how?
Still left to be resolved:1) random crash on closing a connection. - work arounds: - delegates: don't allow incoming connections
Quote from: trader on August 27, 2014, 09:55:48 pmSo is this upgrade going to be 0.4.9 ?Yes
So is this upgrade going to be 0.4.9 ?
Quote from: bytemaster on August 27, 2014, 09:17:59 pm1) 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.
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.