Bitcoin Forum
November 11, 2024, 03:31:18 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Do MtGox create their own lag to suit their own trading regime!?  (Read 1045 times)
The Koolio (OP)
Hero Member
*****
Offline Offline

Activity: 560
Merit: 500


Minds are like parachutes they work best when open


View Profile WWW
April 24, 2013, 04:50:23 PM
 #1

I started this post as Im sick to death of MtGox's engine lag. It all seems overly suspicious and I wanted the thoughts of you guys.

When huge buy ups happen, there is little to no lag, which in my eyes suits MtGox as this means they create definite panic buying. However, when there is a huge sell off there is instant lag upto minutes and in some instances an hour. I translate this as to Gox taking the high buy orders (therefore getting the best prices for themselves), and once trading resumes, panic selling takes hold and they buy back cheaper.

Now this assumes Gox converts or leaves their client trading profit in coin form, which I suspect they would. I highly suspected this for some time as do others but yet I see no outcry of this. People need to wake up and realise a large company like theres DO have great servers, and that lag is simply created by themselves to suit their trading habits. Embarrassed Embarrassed

1. Litecoin 2. Bitcoin 3. Any of the Anon coins
xane
Newbie
*
Offline Offline

Activity: 51
Merit: 0



View Profile
April 24, 2013, 05:12:14 PM
 #2

I strongly suspect incompetence over any kind of coordinated conspiracy. Gox already makes a fortune in trading fees alone. They would have to be more than just technically inept to risk their credibility to make a few extra trades.
The Koolio (OP)
Hero Member
*****
Offline Offline

Activity: 560
Merit: 500


Minds are like parachutes they work best when open


View Profile WWW
April 24, 2013, 05:14:15 PM
 #3

I once suspected the same, but now after watching prices since pre crash Ive come to notice that lag only ever takes place on sell offs. Never on buy ups, and volume is similar in a lot of instances... Its a shame that the Gox guys have the biggest exchange yet are relatively quiet about their company...

1. Litecoin 2. Bitcoin 3. Any of the Anon coins
TalkingAntColony
Member
**
Offline Offline

Activity: 62
Merit: 10


View Profile
April 24, 2013, 05:14:55 PM
 #4

How can you rule out that the volume of trades during a sell-off is simply greater than a buy-off (note, there is a difference between trade volume and the shear number of trades, which could be greater during sell-off and is the real factor affecting trade lag)? After all, prices tend to fall more easily than they rise in almost every financial instrument.
BinaryMage
Hero Member
*****
Offline Offline

Activity: 560
Merit: 500


Ad astra.


View Profile
April 24, 2013, 05:22:23 PM
 #5

I started this post as Im sick to death of MtGox's engine lag. It all seems overly suspicious and I wanted the thoughts of you guys.

When huge buy ups happen, there is little to no lag, which in my eyes suits MtGox as this means they create definite panic buying. However, when there is a huge sell off there is instant lag upto minutes and in some instances an hour. I translate this as to Gox taking the high buy orders (therefore getting the best prices for themselves), and once trading resumes, panic selling takes hold and they buy back cheaper.

Now this assumes Gox converts or leaves their client trading profit in coin form, which I suspect they would. I highly suspected this for some time as do others but yet I see no outcry of this. People need to wake up and realise a large company like theres DO have great servers, and that lag is simply created by themselves to suit their trading habits. Embarrassed Embarrassed

I've heard crazier conspiracy theories. That said, you should take a long, hard look at Hanlon's Razor.

-- BinaryMage -- | OTC | PGP
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!