BitcoinWisdom.com - Live Bitcoin/LiteCoin Charts

[embargar]

Thanks for a huge update!
Any plans to add more exchanges, particularly hitbtc?
Sometimes I do arbitrage. For this purpose I use btc-e, bitstamp and hitbtc exchanges. But hitbtc' absence makes arbitrage more difficult.

[yellowduck2]

i have been using bitcoinwisdom for many months now and i like it very much. If the premium account can offer more benefits , i will pay for it , 1 whole year to show my support for the site.

[BitcoinWisdom]

hi op

you have just removed bc chart and replaced it with cloack chart.
can you please add other mintpal charts?
bc , rzr and others?
coingy.com have started their TI service and have a full mintpal and other exchanges charts.. but your site is better and would be even greater
if you will add extra charts.

thanks.

Now the list of Mintpal in 'Markets' is automatic base on 7 days volume. All supported altcoin could be found in homepage https://bitcoinwisdom.com

[BitcoinWisdom]

Thanks for a huge update!
Any plans to add more exchanges, particularly hitbtc?
Sometimes I do arbitrage. For this purpose I use btc-e, bitstamp and hitbtc exchanges. But hitbtc' absence makes arbitrage more difficult.

hitBTC's trades is abnormal obviously, so it would not be supported.

[BitcoinWisdom]

i have been using bitcoinwisdom for many months now and i like it very much. If the premium account can offer more benefits , i will pay for it , 1 whole year to show my support for the site.

Of course. We will try our best.

[chipmadness]

Bitcoin Wisdom is by far the best live bitcoin chart to look at! Also love the Mintpal API that is implemented!

[JorgeStolfi]

Hi, it is me again...

I already wrote some time ago that Bitstamp's transaction log (the lower right sub-window) usually has a dozen or so entries out of order every hour, e. g.

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
2014-06-27 01:29:54 | 583.89 | 0.51166
2014-06-27 01:29:57 | 583.97 | 0.93952
2014-06-27 01:29:53 | 584.00 | 1.89133
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

This problem occurs only with Bitstamp, not with BTC-e, Bitfinex, Huobi, or OKCoin. You explained that it is some technical problem on their side, having to do with them using separate computers or databases forAPI trades and manual trades. (Did I understand correctly?)

But the bugs seem to be worse than just trades being reported of order.  If I refresh the Bitstamp chart after it has run for some time, I many differences show up all over the trade log: timestamps change by several seconds, entries get merged or split, and BTC amounts are rounded off differently (e.g., 2.0000 versus 1.9999). Sometimes entries appear, disappear, or change radically.  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:

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

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.

[yellowduck2]

i have a suggestion.

For alarm setting, why not automatically draw a line across the chart based on the value of alarm set ? The line will enable user to know and represent once it's hit i am out (take profit) or i am in (buy order fill). I believe people set alarm to represent their buy order or sell order. A line across the chart which represent the value set on alarm will visually help user to see clearly the value they have set on the alarm.

[embargar]

Thanks for a huge update!
Any plans to add more exchanges, particularly hitbtc?
Sometimes I do arbitrage. For this purpose I use btc-e, bitstamp and hitbtc exchanges. But hitbtc' absence makes arbitrage more difficult.

hitBTC's trades is abnormal obviously, so it would not be supported.

I have not noticed any abnormal activity on hitbtc while trading.
Its trading volume and history seems legit.
https://i.imgur.com/iQzNgXL.png

[mrmate]

Thanks for adding Bitfinex to the top bar. Why is Litecoin still in the top bar?

[BitcoinWisdom]

Hi, it is me again...

I already wrote some time ago that Bitstamp's transaction log (the lower right sub-window) usually has a dozen or so entries out of order every hour,

This problem occurs only with Bitstamp, not with BTC-e, Bitfinex, Huobi, or OKCoin. You explained that it is some technical problem on their side, having to do with them using separate computers or databases forAPI trades and manual trades. (Did I understand correctly?)

Bitstamp doesn't contain trade type info, so there is different when the first load and updating in realtime.
The trade type is guessed base on previous price when initialize. In realtime it is base on current price and orderbook.
Also there is no timestamp in realtime, it's simple set as server time when receive the trade. so it is different with initialize data which is always use the true timestamp.

[BitcoinWisdom]

i have a suggestion.

For alarm setting, why not automatically draw a line across the chart based on the value of alarm set ? The line will enable user to know and represent once it's hit i am out (take profit) or i am in (buy order fill). I believe people set alarm to represent their buy order or sell order. A line across the chart which represent the value set on alarm will visually help user to see clearly the value they have set on the alarm.

I'm afraid it could not be improved. Current design is minimize the affact on the main chart and keep the main chart clearly.

[BitcoinWisdom]

Is there a bug? With chrome every time I remove my lines or retracements, I can't add new ones, I have to restart the entire browser to be able to use these tools again, even a new tab doesn't fix it?

I cannot reproduce the issue. Is there any error message in console?

[JorgeStolfi]

Hi, it is me again...

I already wrote some time ago that Bitstamp's transaction log (the lower right sub-window) usually has a dozen or so entries out of order every hour,

This problem occurs only with Bitstamp, not with BTC-e, Bitfinex, Huobi, or OKCoin. You explained that it is some technical problem on their side, having to do with them using separate computers or databases forAPI trades and manual trades. (Did I understand correctly?)

Bitstamp doesn't contain trade type info, so there is different when the first load and updating in realtime.
The trade type is guessed base on previous price when initialize. In realtime it is base on current price and orderbook.
Also there is no timestamp in realtime, it's simple set as server time when receive the trade. so it is different with initialize data which is always use the true timestamp.

Thanks for the explanation.  But why would that affect the prices and amounts so much? E.g.in the second transaction below

[ ... ]
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
[ ... ]

Is is possible for a transaction to be displaced by several minutes when the log is reordered by timestamp?

[BitcoinWisdom]

Hi, it is me again...

I already wrote some time ago that Bitstamp's transaction log (the lower right sub-window) usually has a dozen or so entries out of order every hour,

This problem occurs only with Bitstamp, not with BTC-e, Bitfinex, Huobi, or OKCoin. You explained that it is some technical problem on their side, having to do with them using separate computers or databases forAPI trades and manual trades. (Did I understand correctly?)

Bitstamp doesn't contain trade type info, so there is different when the first load and updating in realtime.
The trade type is guessed base on previous price when initialize. In realtime it is base on current price and orderbook.
Also there is no timestamp in realtime, it's simple set as server time when receive the trade. so it is different with initialize data which is always use the true timestamp.

Thanks for the explanation.  But why would that affect the prices and amounts so much? E.g.in the second transaction below

[ ... ]
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
[ ... ]

Is is possible for a transaction to be displaced by several minutes when the log is reordered by timestamp?

I think it is not needed. It is bitstamp only issue, and doesn't have good solution. because the trade type is missed, reorder only won't solve the issue and will make the code more complex and decrease the charts performance. Several seconds unexpected offset is not big problem.

[cryptobear]

Guys, your vtc/btc graph stopped, and now showing smth unreal. Please fix.
https://bitcoinwisdom.com/markets/cryptsy/vtcbtc

[BitcoinWisdom]

Thanks for a huge update!
Any plans to add more exchanges, particularly hitbtc?
Sometimes I do arbitrage. For this purpose I use btc-e, bitstamp and hitbtc exchanges. But hitbtc' absence makes arbitrage more difficult.

hitBTC's trades is abnormal obviously, so it would not be supported.

I have not noticed any abnormal activity on hitbtc while trading.
Its trading volume and history seems legit.

Here is an article about it that on Reddit
http://www.reddit.com/r/BitcoinMarkets/comments/25mpbf/hitbtcs_volume_is_very_suspicious/

[BitcoinWisdom]

Guys, your vtc/btc graph stopped, and now showing smth unreal. Please fix.
https://bitcoinwisdom.com/markets/cryptsy/vtcbtc

The price dropped too quickly and trigger the anti-glitch mechanism.
The trades is the same as cryptsy site, so it is still working.

[JorgeStolfi]

[ ... ]
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
[ ... ]

Is is possible for a transaction to be displaced by several minutes when the log is reordered by timestamp?

I think it is not needed. It is bitstamp only issue, and doesn't have good solution. because the trade type is missed, reorder only won't solve the issue and will make the code more complex and decrease the charts performance. Several seconds unexpected offset is not big problem.

My question was not meant to be a suggestion for Bicoinwisdom, sorry for the confusion.  Of course it is Bitstamp who should fix their act.

I meant to ask whether the timestamps problem and lack of trade type could explain why 0.03466 BTC became 0.304 BTC (almost 9x) with a different price. If the entries can be displaced by several minutes when refreshing, that could explain it, perhaps...

It is ironic that Bitstamp is the only exchange that cannot get the timestamp right. 

(And, by the way, the omission of  the trade type is another thing that their clients could think that it was meant to hide front-running and other order manipulation.  Yet another reason for them to fix their API.)

[noSlave]

Hey,
love your side and that's why I have paid fort it.

....but the adds are still there. Can you pls check this?

Here's my Adress: https://blockchain.info/address/19pgFoigj22FEmKVgFazuFD3Fxbde82zNv