0 Members and 1 Guest are viewing this topic.
Quote from: alt on December 24, 2017, 11:28:39 pmnobody ever told me about these rule.Who told you that the margin call would be filled at the lower price? I guess nobody did. It's just an assumption on your side.I admit that it's a *reasonable* assumption, and that this is how it *should* work. But the fact that it doesn't is not a bug. It's just the way it has been implemented, and AFAIK it does not violate the specification.It's not the only point where the market engine does not behave how people assume it does, see the case brought up by @alexpmorris a couple of months ago. The market engine needs an overhaul, but that is something that takes care, and planning, and detailed specifications, and lots of discussion. You don't do someting like this overnight.
nobody ever told me about these rule.
Quote from: alt on December 24, 2017, 11:28:39 pmas the most active trader in DEX,nobody ever told me about these rule.so where is my compensation?Bitshares owes you no compensation, in accordance with the implemented MIT license: https://github.com/bitshares/bitshares-core/blob/master/LICENSE.txtSpecifically:QuoteTHE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS INTHE SOFTWARE.
as the most active trader in DEX,nobody ever told me about these rule.so where is my compensation?
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS INTHE SOFTWARE.
Quote from: alt on December 24, 2017, 11:28:39 pmas the most active trader in DEX,nobody ever told me about these rule.so where is my compensation?I remember the committee member @fav have told me I will get it of course.where is it now?Quote from: alt on December 24, 2017, 11:24:05 pmhave you told the shorters they will lose 10% even there are plenty of bid orders in the market?have you told the buyer their bid order can't be filled even their order is in the first position?this is just another joke from the core team.Quote from: pc on December 24, 2017, 02:08:55 pmShorters should know that they risk a 10% penalty when being margin called. None of the defined operational parameters are broken through this behaviour.IMO this bug is a flaw, but not a serious problem. It certainly doesn't justify an emergency fix, or whatever you expect.Make sure to contact the bitshares blockchain for a refund. Good luck though, since every loss happened within the rules.
as the most active trader in DEX,nobody ever told me about these rule.so where is my compensation?I remember the committee member @fav have told me I will get it of course.where is it now?Quote from: alt on December 24, 2017, 11:24:05 pmhave you told the shorters they will lose 10% even there are plenty of bid orders in the market?have you told the buyer their bid order can't be filled even their order is in the first position?this is just another joke from the core team.Quote from: pc on December 24, 2017, 02:08:55 pmShorters should know that they risk a 10% penalty when being margin called. None of the defined operational parameters are broken through this behaviour.IMO this bug is a flaw, but not a serious problem. It certainly doesn't justify an emergency fix, or whatever you expect.
have you told the shorters they will lose 10% even there are plenty of bid orders in the market?have you told the buyer their bid order can't be filled even their order is in the first position?this is just another joke from the core team.Quote from: pc on December 24, 2017, 02:08:55 pmShorters should know that they risk a 10% penalty when being margin called. None of the defined operational parameters are broken through this behaviour.IMO this bug is a flaw, but not a serious problem. It certainly doesn't justify an emergency fix, or whatever you expect.
Shorters should know that they risk a 10% penalty when being margin called. None of the defined operational parameters are broken through this behaviour.IMO this bug is a flaw, but not a serious problem. It certainly doesn't justify an emergency fix, or whatever you expect.
This should work properly by using your Smart asset to reduce the collateral first, then fill all orders until sold or until it reaches the margin call price.
I don't know if you don't know what can happen with this flaw, or you don't care about others lost totally.in fact the users could have lost millions USD in these days if somebody attack with this flaw.when the price drop down, some short possition will be margin call after several minutes,the attacker can borrow 0.1 CNY with collect rate just a little bit higher than the first debt position.in fact he can create many short position like this.the other hand, the attacker create some bid orders prepare to fill the comming magin call orders. the bid price is feedprice/1.1when the margin call happen, the small debt position will execute first, and make all bid orders be ignore just like what happend to mine 4 days ago.then the real big margin call orders will filled the attacker's bid order at feed price / 1.1finally the attacker can sell these cheaper BTS to the bid orders which have be ignore just now.so he can earn 10% without any risk.
The issue was submitted a long ago, why wasn't the fix included in the last fork?
Quote from: alt on December 21, 2017, 05:38:13 amseems not the same issue.Quote from: abit on December 21, 2017, 05:22:07 amThis issue has been discussed on github:* https://github.com/bitshares/bitshares-core/issues/453 and* https://github.com/bitshares/bitshares-core/issues/338#issuecomment-318808452There is a test case to reproduce it:* https://github.com/bitshares/bitshares-core/pull/341/commits/aa60533269d7ca5e534bedb8a63ac4742d50164cIt's on the to-do list, will be fixed in a future release.It is.
seems not the same issue.Quote from: abit on December 21, 2017, 05:22:07 amThis issue has been discussed on github:* https://github.com/bitshares/bitshares-core/issues/453 and* https://github.com/bitshares/bitshares-core/issues/338#issuecomment-318808452There is a test case to reproduce it:* https://github.com/bitshares/bitshares-core/pull/341/commits/aa60533269d7ca5e534bedb8a63ac4742d50164cIt's on the to-do list, will be fixed in a future release.
This issue has been discussed on github:* https://github.com/bitshares/bitshares-core/issues/453 and* https://github.com/bitshares/bitshares-core/issues/338#issuecomment-318808452There is a test case to reproduce it:* https://github.com/bitshares/bitshares-core/pull/341/commits/aa60533269d7ca5e534bedb8a63ac4742d50164cIt's on the to-do list, will be fixed in a future release.
alt, did you really lose 1M (one million) BTS?
I don't know what happend to you?! and you want who to give you an apologize?! the community? the developer? the user? the Committee? the system?If you hate the system flaw, destroy it in your way.If you hate the BITSHARES, leave or destroy it in your way.“Don’t let hatred control you, no matter what others do that causes [anger]. You would only become guilty of the same sin that afflicts them, and nothing would be solved.” —Billy GrahamYou are a very good developer of BTS, do what you think is right.
Quote from: alt on December 20, 2017, 11:53:58 pmseems nobody will take responsibility for my lose because of the system bug?and nobody care about repair the flaw to protect the short position?this is what the great DEX you told to others?Dude WTF happened to you ? You used to be a star around hear everybody use to love you, even Dan gave you accolades. I used to think you are a genius. Now you are coming here and just fucking up everything, it is like you are possessed or something ,like somebody is against you and we all want to fuck you.You are just threatening this and that ... WTF . We know you are a smart guy but you should decide either you are on the dark side or not. Bitshares gave you a lot so if you want to help this is good and you'll got all the love in the world for all of us, if not don't act like you are the second coming of Jesus or Buddha or whatever you believe in, cause you are not..... Go ahead fuck up Bitshares and ruin all the fucking time you spend to built it. If not just calm down body we still love you man if you are with us. We will fucking fix your lose if you don't act like a douche-bag.....
seems nobody will take responsibility for my lose because of the system bug?and nobody care about repair the flaw to protect the short position?this is what the great DEX you told to others?
Quote from: alt on December 20, 2017, 02:23:12 amwhat ever, I guess somebody should pay for my lost. and also pay for the shorters lost.sell 969536 BTS to me at price 2.84and send some BTS to the margin call owner, they should spent less BTS to pay for the debt.I'm sure the blockchain will give you a refund. stop the cryptic bullshit please, if there's an issue make a clear post.
what ever, I guess somebody should pay for my lost. and also pay for the shorters lost.sell 969536 BTS to me at price 2.84and send some BTS to the margin call owner, they should spent less BTS to pay for the debt.
I have confirmedit's very easy to develop a script to attack the margin call orders.and very danger to the system.this is another fuck flaw because of this BSIP18 fork.
2.840 10000.0000 28405.0000 kaifeng92.840 969536.4689 2753532.0542 demo.btsbots 2.840 3038.1662 8628.5439 abcbts
12/20 12:38:06 2.833 16970.4275 48077.2211 xlggd tara12/20 12:38:06 2.835 35263.8986 99973.1561 xlggd yxb12/20 12:38:06 2.835 1763.6683 5000.0000 xlggd exchange.btsbots12/20 12:38:06 2.839 352.1127 1000.0000 xlggd hsh1983090712/20 12:38:06 2.840 100000.0000 284000.0000 xlggd ags12/20 12:38:06 2.840 3521.1268 10000.0000 xlggd bts812912/20 12:38:06 2.840 35193.3518 99949.1228 xlggd yxb12/20 12:38:06 2.840 50000.0000 142000.5000 xlggd