Here's something that bothers me. When I am watching the bid/ask right hand graph, the price indicator on the horizontal cursor obliterates the bid/ask graph. Maybe it could relocate an inch or so to the left with some keystroke or menu selection? I'd be glad to donate .25BTC for this feature.
Sometimes I consider a market order. The available bids that cover my proposed order are not always available in the bid/ask list. I think it would be useful to have some vertical lines at the B/A graph to indicate the approximate value of at a given point. What I mean is that a wall of 25 has a definite horizontal length. If there were vertical lines spaced at say 50 or something like that, I'd be able to guess approximately how many coins are up for bid at a given price on the cursor/graph position. Any questions? I'd be glad to donate .25BTC for this feature.
The first feature is improved. when the cursor on the axis, the price indicator shows in the left. The Second will be a bit later, because the currently way save them in the cookie, this feature will bring 15 extra parameters. I have to move them to server side to decrease the cookie size.
|
|
|
BTC-e LTC/USD buys: 2.482 18.42539849 45.73183905 2.480001 68.17056556 169.06307075 2.48 1061.98050225 2633.711645
2.4820000 18.425 4800000 68.170 4790000 1.0000 4770000 37.000 4767200 0.5000 4740300 9.0315 4740200 261.10 4710000 1.0000 4700000 10.060 4690000 20.368 4683000 0.2020 4682600 1.0000 4675500 157.68 4675400 367.28 4670000 1.0000
2.48 87 47 398 46 1622 45 1950 44 2083 43 2121
You can see that the 1000LTC order is not appear on wisdom. Something wrong here or I don't get it?
That's a big bug, I see, the price precision is not enough, so the 2.480001 overwrite 2.48. I hated Mt.Gox, at the first design I was following Mt.Gox rule which is limit to 5 digest precision, that's totally wrong way. The volume is not affected, the trade history is not accurate, but it seems not big problem, up to 0.00001 errors. I will try redesign the database. The issue has been solved.
|
|
|
That looks great! Any plans to expand to other alt-coins?
I'm sorry, there is no plan add any other coins. The lowest volume to add is 5000 BTC per day.
|
|
|
I would phrase it like "Last updated XX seconds ago" or "Updated XX seconds ago".
I've changed the text to "Updated X seconds ago". but still feel it would be confused with "Browser read the data from server X seconds ago" instead of "The data is synced to the exchange X seconds ago".
|
|
|
I was just posting about this... There are some orders on BTC-e that don't always show up on your site. I check back and forth, and this has been going on for a few days that larger orders usually don't appear on your site.
Also... At the bottom where it says "Update to X seconds ago"; shouldn't it read "Updated X seconds ago"?
I'm sorry English is not my first language. which I want to express is: current tick and depth is X seconds ago of the exchange. for example. The server get the ticker of BTC-e The browser get the ticker from server after 2 seconds Then it refresh to "Update to 2 seconds ago". Which word should be use?
|
|
|
BTC-e LTC/USD buys: 2.482 18.42539849 45.73183905 2.480001 68.17056556 169.06307075 2.48 1061.98050225 2633.711645
2.4820000 18.425 4800000 68.170 4790000 1.0000 4770000 37.000 4767200 0.5000 4740300 9.0315 4740200 261.10 4710000 1.0000 4700000 10.060 4690000 20.368 4683000 0.2020 4682600 1.0000 4675500 157.68 4675400 367.28 4670000 1.0000
2.48 87 47 398 46 1622 45 1950 44 2083 43 2121
You can see that the 1000LTC order is not appear on wisdom. Something wrong here or I don't get it?
That's a big bug, I see, the price precision is not enough, so the 2.480001 overwrite 2.48. I hated Mt.Gox, at the first design I was following Mt.Gox rule which is limit to 5 digest precision, that's totally wrong way. The volume is not affected, the trade history is not accurate, but it seems not big problem, up to 0.00001 errors. I will try redesign the database.
|
|
|
There is lot of values now on the top of the page, and having 796 in #2 position close to mtgox is a little bit invasive when you just need mtgox and bitstamp Is it possible to have the choice to hide some you don't use ? We could still have access through the menu like btc-china for example ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Custom watching list is position 2 of the TODO list. Exchange Comparision will take about 1 week or more to design and code. so custom watching list will be added after 1 week.
|
|
|
I adore this service already. The one addition that would make it perfect is the ability to draw fibonacci retracements/extensions. Thanks!
Thanks. We have plan to support drawing lines, but currently we are not focus on it, so it will take some time maybe several weeks to wait.
|
|
|
great work... in the future do you plan on adding more technical indicators and Price band? like Bollinger Band?
Yes. I've added a TODO list in the top post. add more indicators and band has low priority to other tasks, but it is not absolute.
|
|
|
Can someone clearly explain the signals on the right ? Would really love to understand them better. ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fs10.postimg.org%2Fyf50lztrt%2FScreen_Shot_2013_07_08_at_9_12_01_PM.png&t=663&c=SO5JNnqowaP47A) Green line is asks. the longer the more amount on that price. Red line is bids. White triangle is the average price of bids and asks nearby. Yellow triangle is the latest price.
|
|
|
I would love premium paid future where one can draw on the graph and save graphs. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Nice, but it still is far from draw and save the graph.
|
|
|
Is there an explanation for this phenomena? Perhaps I'm ignorant on something. The oldest sell in the images below for 30 BTC shows green on BitcoinWisdom, but red on Moody. I watched it happen, it was a sell. You can see it happen a few more times in just these two images. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F859VhYN.png&t=663&c=g2nXQrBSh_x0NQ) ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FmH4yQ63.png&t=663&c=MTk4F95WFqFn-w) I see this happen with the candles and volume bars at times, too. I watched a 1,424 LTC/USD buy go through on btc-e a few days ago and it grew a red volume bar and candle on BitcoinWisdom. I believe this is to do with the difference in Candlestick HLC vs Candlestick, though I wanted to mention just in case there is a correlation with the transaction history colors. BitcoinWisdom mark if the price great than previous price then it is green, if the price less than it is red, if equals then the color is the same as previous trade instead of bid is green and ask is red. BTC-e's stick equals CandleStick+30m. CandleStick is short alias of CandleStickOHLC(Open High, Low, Close). CandleStickHLC(High, Low Close) keep the price continous. I set it because of bitstamp does't return trade type. now I've changed it to bid green, ask red except bitstamp.
|
|
|
Is there an explanation for this phenomena? Perhaps I'm ignorant on something. The oldest sell in the images below for 30 BTC shows green on BitcoinWisdom, but red on Moody. I watched it happen, it was a sell. You can see it happen a few more times in just these two images. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F859VhYN.png&t=663&c=g2nXQrBSh_x0NQ) ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FmH4yQ63.png&t=663&c=MTk4F95WFqFn-w) I see this happen with the candles and volume bars at times, too. I watched a 1,424 LTC/USD buy go through on btc-e a few days ago and it grew a red volume bar and candle on BitcoinWisdom. I believe this is to do with the difference in Candlestick HLC vs Candlestick, though I wanted to mention just in case there is a correlation with the transaction history colors. BitcoinWisdom mark if the price great than previous price then it is green, if the price less than it is red, if equals then the color is the same as previous trade instead of bid is green and ask is red. BTC-e's stick equals CandleStick+30m. CandleStick is short alias of CandleStickOHLC(Open High, Low, Close). CandleStickHLC(High, Low Close) keep the price continous.
|
|
|
please add an option to switch to log scale, it would be useful for analyzing longer time frames.
log scale is added. 'SETTINGS -> Scale'
|
|
|
Can you add time server now ?
What's time server?Do you mean display time on page?Currently footer and header has no room for the time, and OS always display the time, the latest trade shows the time too, so it won't be added until I redesign the page.
|
|
|
i donated some ltc to you, this chart is really setting the bar. the new markets are really good, and the rate and amplitude stuff is just excellent.
Thank you very much!
|
|
|
Really a great site, quickly became my top one.
Any chance of additional exchanges being added? If so I would like to see Crypto-trade on there.
I've checked crypto-trade. the trade history API needs authorize. I wrote some code to request, authorize is passed, but server return 500 Internal Error array_key_exists() expects parameter 2 to be array, boolean given for private/getinfo and I'm afraid the TradeHistory is similar to BTC-e, only returns the trade of owner, then crypto-trade's trades cannot be tracked. Good news, the API returns trade history. so there is no problem. Is it possible to add CT to the charts now? Crypto-Trade is added. http://bitcoinwisdom.com/markets/cryptotrade/btcusd
|
|
|
please add namecoin.
by far the best chart available. great job. a real contribution to the community. thanks much.
Thanks. About namecoin, I'm sorry, I'm afraid it will not be added recently. because namecoin is not popular enough and any new currency in the same exchange will decrease the scan frequence 33% to 50%, especially for BTC-e which doesn't have trade history API.
|
|
|
Good website, however it would benefit a lot if you can add Bitstamp support so we can finally move off from Gox.
Bitstamp was added many weeks ago.
|
|
|
Really a great site, quickly became my top one.
Any chance of additional exchanges being added? If so I would like to see Crypto-trade on there.
I've checked crypto-trade. the trade history API needs authorize. I wrote some code to request, authorize is passed, but server return 500 Internal Error array_key_exists() expects parameter 2 to be array, boolean given for private/getinfo and I'm afraid the TradeHistory is similar to BTC-e, only returns the trade of owner, then crypto-trade's trades cannot be tracked. Good news, the API returns trade history. so there is no problem.
|
|
|
|