# Last edited on 2014-06-27 17:24:03 by stolfilocal
# POSTED TO THE BITCOINWISDOM THREAD 

Bitstamp's transaction log from BitcoinWisdom.com's chart (lower right sub-window) usually has a dozen or so entries out of order every hour, e. g.

[pre]
2014-06-27 01:27:49 | 581.06 | 0.90985
2014-06-27 01:28:32 | 583.70 | 0.12139
2014-06-27 01:28:35 | 583.70 | 0.01592
[color=red]2014-06-27 01:29:54 | 583.89 | 0.51166
2014-06-27 01:29:57 | 583.97 | 0.93952[/color]
[color=green]2014-06-27 01:29:53 | 584.00 | 1.89133[/color]
2014-06-27 01:29:58 | 584.49 | 0.27701
2014-06-27 01:30:02 | 584.59 | 0.09477
2014-06-27 01:30:04 | 584.64 | 0.03455
[/pre]

This problem occurs only with Bitstamp, not with BTC-e, Bitfinex, Huobi, or OKCoin. The owner of BitcoinWisdom.com gave a technical explanation, apparently having to do with chlock skew or concurrency races between the machines used by API trade and manual trade. 

Also, if the chart is refreshed after some time, there are many differences: timestamps change by several seconds, entries get merged or split, and BTC amounts are rounded off differently (e.g., 2.0000 versus 1.9999), or completely changed.  For instance, the left and right halves of the table below are matching sections of the transaction logs captured before and after refreshing the page, sorted by the timestamps:

[pre]
2014-06-27 02:41:26 | 579.69 |  [color=red]0.19999[/color] | 2014-06-27 02:41:26 | 579.69 |  [color=red]0.20000[/color]
2014-06-27 02:41:[color=red]30[/color] | 579.69 |  0.20000 | 2014-06-27 02:41:[color=red]29[/color] | 579.69 |  0.20000
2014-06-27 02:41:42 | 579.69 |  [color=red]0.19999[/color] | 2014-06-27 02:41:42 | 579.69 |  [color=red]0.20000[/color]
2014-06-27 02:43:41 | 581.59 |  0.13100 | 2014-06-27 02:43:41 | 581.59 |  0.13100
                                        | [color=red]2014-06-27 02:43:43 | 581.61 |  0.02851[/color]
2014-06-27 02:43:47 | 582.27 |  [color=red]0.64365[/color] | 2014-06-27 02:43:47 | 582.27 |  [color=red]0.61513[/color]
2014-06-27 02:43:52 | 582.47 |  0.13873 | 2014-06-27 02:43:52 | 582.47 |  0.13873
2014-06-27 02:43:56 | 582.61 |  0.10367 | 2014-06-27 02:43:56 | 582.61 |  0.10367
2014-06-27 02:[color=red]43:59[/color] | 582.[color=red]67[/color] |  [color=red]0.03466[/color] | 2014-06-27 02:[color=red]44:00[/color] | 582.[color=red]72[/color] |  [color=red]0.30400[/color]
2014-06-27 02:44:04 | 582.77 |  0.24398 | 2014-06-27 02:44:04 | 582.77 |  0.24398
2014-06-27 02:44:08 | 582.91 |  0.29504 | 2014-06-27 02:44:08 | 582.91 |  0.29504
[color=red]2014-06-27 02:44:12 | 583.06 |  0.09733[/color] | 
[color=red]2014-06-27 02:44:12 | 583.06 |  0.36631[/color] | 
[color=red]2014-06-27 02:44:14 | 583.21 |  0.21029[/color] | 
[color=red]2014-06-27 02:44:15 | 583.36 |  0.03428[/color] | 
2014-06-27 02:44:16 | 583.48 |  [color=red]0.03462[/color] | 2014-06-27 02:44:16 | 583.48 |  [color=red]0.41083[/color]
[color=red]2014-06-27 02:44:18 | 583.51 |  0.06889[/color] | 
2014-06-27 02:44:19 | 583.53 |  [color=red]0.03461[/color] | 2014-06-27 02:44:19 | 583.53 |  [color=red]0.06889[/color]
2014-06-27 02:44:[color=red]21[/color] | 583.[color=red]58[/color] |  [color=red]1.05500[/color] | 2014-06-27 02:44:[color=red]23[/color] | 583.[color=red]66[/color] |  [color=red]1.14992[/color]
                                        | [color=red]2014-06-27 02:44:25 | 583.68 |  1.90715[/color]
[color=red]2014-06-27 02:44:55 | 583.58 |  0.03461[/color] | 
[color=red]2014-06-27 02:44:55 | 583.68 |  1.96746[/color] | 
2014-06-27 02:45:[color=red]11[/color] | 583.20 |  0.01792 | 2014-06-27 02:45:[color=red]10[/color] | 583.20 |  0.01792
2014-06-27 02:47:24 | 582.62 |  0.17500 | 2014-06-27 02:47:24 | 582.62 |  0.17500
2014-06-27 02:50:55 | 583.02 |  1.23464 | 2014-06-27 02:50:55 | 583.02 |  1.23464
[/pre]

Note in particular the entry at 02:43:59 on the left side, that got replaced by an entry at 02:44:00 on the right side, with different price (582.67 became 582.72) and different amount (0.03466 BTC became 0.30400 BTC).

I suppose that these differences, like the trades out of order, are due to bugs in Bitstamp's chart data server.  The Bitstamp owners should fix these bugs, they are bad for their image in many ways.  For one thing, they are annoying complications for people who try to analyze these logs. (Which is the real chronological order: that implied by the timestamps, or the order of the entries in the log?)  These "bugs" would also be good covers for front-running or other unethical manipulation of the orders, and therefore may have a negative impact on the confidence of their clients.

----------------------------------------------------------------------


[pre]
2014-06-27 02:41:26 | 579.69 |  0.19999 | 2014-06-27 02:41:26 | 579.69 |  0.20000
2014-06-27 02:41:30 | 579.69 |  0.20000 | 2014-06-27 02:41:29 | 579.69 |  0.20000
2014-06-27 02:41:42 | 579.69 |  0.19999 | 2014-06-27 02:41:42 | 579.69 |  0.20000
2014-06-27 02:43:41 | 581.59 |  0.13100 | 2014-06-27 02:43:41 | 581.59 |  0.13100
                                        | 2014-06-27 02:43:43 | 581.61 |  0.02851
2014-06-27 02:43:47 | 582.27 |  0.64365 | 2014-06-27 02:43:47 | 582.27 |  0.61513
2014-06-27 02:43:52 | 582.47 |  0.13873 | 2014-06-27 02:43:52 | 582.47 |  0.13873
2014-06-27 02:43:56 | 582.61 |  0.10367 | 2014-06-27 02:43:56 | 582.61 |  0.10367
2014-06-27 02:43:59 | 582.67 |  0.03466 | 2014-06-27 02:44:00 | 582.72 |  0.30400
2014-06-27 02:44:04 | 582.77 |  0.24398 | 2014-06-27 02:44:04 | 582.77 |  0.24398
2014-06-27 02:44:08 | 582.91 |  0.29504 | 2014-06-27 02:44:08 | 582.91 |  0.29504
2014-06-27 02:44:12 | 583.06 |  0.09733 | 
2014-06-27 02:44:12 | 583.06 |  0.36631 | 
2014-06-27 02:44:14 | 583.21 |  0.21029 | 
2014-06-27 02:44:15 | 583.36 |  0.03428 | 
2014-06-27 02:44:16 | 583.48 |  0.03462 | 2014-06-27 02:44:16 | 583.48 |  0.41083
2014-06-27 02:44:18 | 583.51 |  0.06889 | 
2014-06-27 02:44:19 | 583.53 |  0.03461 | 2014-06-27 02:44:19 | 583.53 |  0.06889
2014-06-27 02:44:21 | 583.58 |  1.05500 | 2014-06-27 02:44:23 | 583.66 |  1.14992
                                        | 2014-06-27 02:44:25 | 583.68 |  1.90715
2014-06-27 02:44:55 | 583.58 |  0.03461 | 
2014-06-27 02:44:55 | 583.68 |  1.96746 | 
2014-06-27 02:45:11 | 583.20 |  0.01792 | 2014-06-27 02:45:10 | 583.20 |  0.01792
2014-06-27 02:47:24 | 582.62 |  0.17500 | 2014-06-27 02:47:24 | 582.62 |  0.17500
2014-06-27 02:50:55 | 583.02 |  1.23464 | 2014-06-27 02:50:55 | 583.02 |  1.23464
[/pre]