Author Topic: short order didn't match now  (Read 4977 times)

0 Members and 1 Guest are viewing this topic.

Offline vikram

Is this bug somehow related to the slow synchronization for the last few days? I see a lot of fake transactions in my wallet, which kept occurring until i canceled short order ???

Synchronization in general has become a lot slower from increased market activity.

The fake transactions in your wallet are mostly likely due to this bug; the next release will prevent such fake transactions from occurring. If you want to remove the existing ones, take a look at the wallet_remove_transaction command. But be careful not to delete any real transactions.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Known bug .. market is halted due to a rounding loop in the delegates

Offline mf-tzo

  • Hero Member
  • *****
  • Posts: 1725
    • View Profile
Quote
Damn rounding errors resulted in neither the full bid nor full ask getting filled leaving dust on the orders.

I had a check in the engine to make sure that one order or the other was always filled and to exit if not to prevent sending all delegates into an infinite loop.   That check triggered and stopped the GLD market.

The rounding errors were much higher than I anticipated possible (I had checks in there for this)... I have since implemented a more robust approach to rounding that should address this issue.  Yet another test case  for us to add. 

Note: we had test cases for it working even test cases with rounding errors....  just not test cases with rounding errors this large.

But I am not talking about GLD market. I can't short on bitusd market even if I put an order to short @ 28 and the bid price is 31...

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
And so  my 'time bending' theory bites the dust... :)
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
This does not account for missed blocks which we do not know in advance. The genesis time is also more of a symbolic birthtime of the DAC; it is not 1 block interval before block 1.
Ah .. I see .. I always thought missed blocks still have there number :) thanks for pointing out .. do we have counter in the wallet for the number of missed blocks somewhere

Offline vikram

just wrote a small python script to figure out the exact time:
https://github.com/xeroc/pytshares/blob/master/timeofblock.py

2014-09-28 02:38:50 UTC

??
According to your script the fork already happened  :)
oh .. didn't notice .. seems to be a bug in my script ..

//edit: this is odd I basically just do the following in python
     genesisTime + confirmationTime*blockNum
so what's wrong?

This does not account for missed blocks which we do not know in advance. The genesis time is also more of a symbolic birthtime of the DAC; it is not 1 block interval before block 1.

Offline Riverhead


Shouldn't the bitUSD buyer using 1,072,478.01492 BTSX for his/her purchase be informed that his bot (I assume it is a bot) is losing money for him?

Not that I mind the dividend but...
There's no way to know who it is.

Offline bytemaster

Damn rounding errors resulted in neither the full bid nor full ask getting filled leaving dust on the orders.

I had a check in the engine to make sure that one order or the other was always filled and to exit if not to prevent sending all delegates into an infinite loop.   That check triggered and stopped the GLD market.

The rounding errors were much higher than I anticipated possible (I had checks in there for this)... I have since implemented a more robust approach to rounding that should address this issue.  Yet another test case  for us to add. 

Note: we had test cases for it working even test cases with rounding errors....  just not test cases with rounding errors this large.     
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline mf-tzo

  • Hero Member
  • *****
  • Posts: 1725
    • View Profile
So I assume therefore that 0.4.18 is still buggy and a new version will replace it soon?


Offline johncitizen

  • Full Member
  • ***
  • Posts: 142
    • View Profile
I shouldn't complain since I had some short orders and BTSX price fell more so these should have been actioned at lower prices but...

It would be nice if I can manage to finally short some bitusd. What am I doing wrong?

Top bid price I see is 350 @ 31.01
Top ask I see is 500 @ 31.99
price feed is @ 32.7370

Are the above correct? What price should I put in order to short bitusd? I would think that 31.01 would be ok and my order will get instantly actioned.

I am on v.0.4.18 RC1 which I downloaded from DACsunlimited webiste..

On 0.4.18 and cannot short the BitUSD or GLD

Driving me crazy watching those orders sit still. I spammed that 31.01 trying to get it but no avail. Tried shorting those high BitGLD buy orders at 44,000 too.

Hahaha... glad to see im not the only shark!

Offline mf-tzo

  • Hero Member
  • *****
  • Posts: 1725
    • View Profile
I shouldn't complain since I had some short orders and BTSX price fell more so these should have been actioned at lower prices but...

It would be nice if I can manage to finally short some bitusd. What am I doing wrong?

Top bid price I see is 350 @ 31.01
Top ask I see is 500 @ 31.99
price feed is @ 32.7370

Are the above correct? What price should I put in order to short bitusd? I would think that 31.01 would be ok and my order will get instantly actioned.

I am on v.0.4.18 RC1 which I downloaded from DACsunlimited webiste..

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
just wrote a small python script to figure out the exact time:
https://github.com/xeroc/pytshares/blob/master/timeofblock.py

2014-09-28 02:38:50 UTC

??
According to your script the fork already happened  :)
oh .. didn't notice .. seems to be a bug in my script ..

//edit: this is odd I basically just do the following in python
     genesisTime + confirmationTime*blockNum
so what's wrong?
« Last Edit: September 28, 2014, 03:19:28 pm by xeroc »

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
That's sounds Chinese to me my friend.. ::)

Based on your scrypt when is the estimation? In the mean time I can put whatever short orders I want and cancel them I assume and short orders will initiate after the hard fork at the current market prices?

Has a final decision been made regarding how long the shorts can keep their position open until they are forced to cover? Or this is still indefinite?

I think it is just a proposal, with high likelihood to become reality, but not in v.0.4.18
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline mf-tzo

  • Hero Member
  • *****
  • Posts: 1725
    • View Profile
That's sounds Chinese to me my friend.. ::)

Based on your scrypt when is the estimation? In the mean time I can put whatever short orders I want and cancel them I assume and short orders will initiate after the hard fork at the current market prices?

Has a final decision been made regarding how long the shorts can keep their position open until they are forced to cover? Or this is still indefinite?

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
just wrote a small python script to figure out the exact time:
https://github.com/xeroc/pytshares/blob/master/timeofblock.py

2014-09-28 02:38:50 UTC

??
According to your script the fork already happened  :)
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
just wrote a small python script to figure out the exact time:
https://github.com/xeroc/pytshares/blob/master/timeofblock.py

2014-09-28 02:38:50 UTC

Offline mf-tzo

  • Hero Member
  • *****
  • Posts: 1725
    • View Profile

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc

Offline mf-tzo

  • Hero Member
  • *****
  • Posts: 1725
    • View Profile
Ok...I am running 0.4.18.. The bid price is currently @ 31.31, the price feed is @ 30.92 and I can see outstanding short orders not actioned @ 25, 28, 28.28 , 29.06 , 29.48 , 29.68, 30 etc..

Why? Bug not fixed yet on windows or something else?

Offline mf-tzo

  • Hero Member
  • *****
  • Posts: 1725
    • View Profile
you mean 04.18? I am on 0.4.17 and I see margin orders below the current bid, I place orders at current bid, I had open orders since last night which some of them should have been opened but nothing... :(

The system just doesn't like me i think...

Offline bytemaster

Error is fixed in latest pre release.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline mf-tzo

  • Hero Member
  • *****
  • Posts: 1725
    • View Profile
Does shorting works now for other people but not for the current Gui?

Show some love to the Gui please...hehehe..

Offline cd

  • Newbie
  • *
  • Posts: 3
    • View Profile
Trying to buy some bitBTC and seeing an error with order matching against a short as well.


Offline mf-tzo

  • Hero Member
  • *****
  • Posts: 1725
    • View Profile
Is there a reason why the shorts order are not shown at all?

If I short @ 28. At what price I will have a margin call and my collateral will vanish?
« Last Edit: September 27, 2014, 09:14:15 am by mf-tzo »

Offline bytemaster

I put a short order at the bid price and it hasn't been matched. Is this a known issue not fixed? I am on 0.4.17 gui

Should I cancel my orders?


No need to cancel... fix for this will be released soon (testing it now).
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline mf-tzo

  • Hero Member
  • *****
  • Posts: 1725
    • View Profile
I put a short order at the bid price and it hasn't been matched. Is this a known issue not fixed? I am on 0.4.17 gui

Should I cancel my orders?

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
bid order didn't match, bid order at price 0.03121, ask order at price 0.03120
Code: [Select]
market USD/BTSX    average price: 0.0323               min cover: 0.02907              short amount: 76701.6023988 USD(2374662.61297 BTSX)             14:00:21
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
    Bid Price    Vol(USD)  Depth(USD) Depth(BTSX) |     Ask Price    Vol(USD)  Depth(USD) Depth(BTSX) |   Cover Price    Vol(USD)  Depth(USD) Depth(BTSX)    Warnning
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
   0.03124024        0.50        0.50       16.01 |    0.03120934    33471.33    33471.33  1072478.01 |    0.02884726      100.00      100.00     3466.53  0.03205251
   0.03121200     1044.71     1045.21    33487.34 |    0.03174603        2.60    34049.52  1072559.91 |    0.02884615        4.00      104.00     3605.33  0.03205128

I think they know about that alt, and fixing (have fixed) it.
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
bid order didn't match, bid order at price 0.03121, ask order at price 0.03120
Code: [Select]
market USD/BTSX    average price: 0.0323               min cover: 0.02907              short amount: 76701.6023988 USD(2374662.61297 BTSX)             14:00:21
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
    Bid Price    Vol(USD)  Depth(USD) Depth(BTSX) |     Ask Price    Vol(USD)  Depth(USD) Depth(BTSX) |   Cover Price    Vol(USD)  Depth(USD) Depth(BTSX)    Warnning
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
   0.03124024        0.50        0.50       16.01 |    0.03120934    33471.33    33471.33  1072478.01 |    0.02884726      100.00      100.00     3466.53  0.03205251
   0.03121200     1044.71     1045.21    33487.34 |    0.03174603        2.60    34049.52  1072559.91 |    0.02884615        4.00      104.00     3605.33  0.03205128

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
feed price is 0.0315129811996 now, but short order didn't match the ask order
Code: [Select]
market USD/BTSX    average price: 0.0315129811996      min cover: 0.0283616830797      short amount: 76396.6023992 USD(2424289.91136 BTSX)             12:58:39
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
    Bid Price    Vol(USD)  Depth(USD) Depth(BTSX) |     Ask Price    Vol(USD)  Depth(USD) Depth(BTSX) |   Cover Price    Vol(USD)  Depth(USD) Depth(BTSX)    Warnning
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
   0.03059739    26822.34    26822.34   876621.80 |    0.03120934    33471.33    33471.33  1072478.01 |    0.02884726      100.00      100.00     3466.53  0.03205251
   0.03053435     3000.00    29822.34   976681.54 |    0.03174603        2.60    34049.52  1072559.91 |    0.02884615        4.00      104.00     3605.33  0.03205128
   0.03052000     5921.69    35744.03  1171167.48 |    0.03216213      531.94    35027.75  1089099.27 |    0.02862595        5.00      109.00     3807.73  0.03180662
   0.03051100       30.51    35774.54  1172512.95 |    0.03220468      484.50    35558.59  1104143.58 |    0.02848462     1227.26     1336.26    46911.73  0.03164958
   0.03051000      305.10    36079.64  1182551.38 |    0.03252033       37.32    35944.43  1105291.13 |    0.02819125        7.00     1343.26    47648.21  0.03132361
   0.03050073     1000.00    37079.64  1215696.87 |    0.03282664      158.36    36441.36  1110115.20 |    0.02818203        5.00     1348.26    47841.21  0.03131337