any chance we can get vault of satoshi on bitcoin wisdom? It is one of the bigger exchanges in canada (outside of virtex). trades in btc, ltc, cad, usd, and other cryptos.
https://www.vaultofsatoshi.com/
Topic: BitcoinWisdom.com - Live Bitcoin/LiteCoin Charts - page 93. (Read 502656 times)
+1
thank you
+1 too. Thanks for all your work!
Okay thanks - we all look forward to the addition of BTC-China's LTC/CNY pair - especially because there will be a 0% commission/trading fee - which is of course absolute MUSIC TO OUR EARS!!
I apologise in advance if it has already been discussed, but is anyone else having connection issues with BTCCharts.com? I cannot even access their forum. I am able to access the site directly, but unable to log in or create a new password/username.
Hi there,
thanks for this great tool!!
Do you have any plans to implement Auroracoin on cryptsy soon?
best regards
tom
thanks for this great tool!!
Do you have any plans to implement Auroracoin on cryptsy soon?
best regards
tom
I changed timezone to Brazil West, but cannot reproduce the issue. It shows hour goes from 0 to 23 when cursor move.
Wait, the problem is real, but occurs only on Safari (5.1.10)/Macbook. It does not occur on Fireox/PCThe problem on Safari occurs only with hours "8" and "9", on the 1h charts, they display as "0" on the crosshair cursor's bottom tab. It does not occur on the 30m charts, so "8:0" and "8:30" display correctly.
It occurred to me that in some languages/systems, a number that starts with "0" is interpreted as octal rather than decimal. In those platforms, "00"through "07" give the same result in octal and decimal, "11" to "23" are interpreted as decimal, but "08" and "09" would be invalid.
Perhaps Safari's javascript differs from the javascript in other browsers in that detail? Sometimes the interpretation of numbers that start with "0" is determined by a global variable, and that variable may have a different default value on Safari?
+1
thank you
+1 too. Thanks for all your work!
+1
thank you
+1 too. Thanks for all your work!
+1
thank you
Please add litecoin from btcchina!
Thanks
Thanks
Since bids increase price and asks reduce it, shouldn't bids be colored green and asks red in the depth graph???
It looks a bit counterintuitive with the current colors.
I guess it's currently intended to mean how easy is for price to go up or down? Thank you.
Yes, It's long historical problem. It was designed as "Trends". After average price implemented some weeks ago, it became meaningless. So for the color, I intend to change it to bid green, ask red too. The main reason I haven't changed because the color of text 'Buy xxx BTC .... will reach xxx' is hard to decide and current setting upward green, downward red is still not bad. It looks a bit counterintuitive with the current colors.
I guess it's currently intended to mean how easy is for price to go up or down? Thank you.
can you increase "step" of the wall for Huobi?
3500 is quite a big number, and steps by 10 Yen not much useful.
I suggest to increase step by at least 25 for CNY.
It's understandable to make it mathematical formula to change these steps (so it will be autoadjusted if price reach ever 3000 USD on btc for example).
Not sure how should formula be, but seems like with current volatility 1% per step looks okish.
Because Huobi doesn't have enough orders. If display in 25 CNY, it will be only 4~5 grouped bids or asks. 3500 is quite a big number, and steps by 10 Yen not much useful.
I suggest to increase step by at least 25 for CNY.
It's understandable to make it mathematical formula to change these steps (so it will be autoadjusted if price reach ever 3000 USD on btc for example).
Not sure how should formula be, but seems like with current volatility 1% per step looks okish.
I see there has already been posted some inquiries about having Justcoin added to your site, but because of registration problems this never went through.
Would you give it another try? New features have been implemented since the last time you tried and both the BTC/EUR and the BTC/NOK have shown great volume.
Please let me know if you have any questions regarding Justcoin.
Best regards,
August
[email protected]
Would you give it another try? New features have been implemented since the last time you tried and both the BTC/EUR and the BTC/NOK have shown great volume.
Please let me know if you have any questions regarding Justcoin.
Best regards,
August
[email protected]
Love your charting service!
Any chance of adding Auroracoin soon? Airdrop to 320,000 people in Iceland is scheduled for March 25th. Exciting times.
Any chance of adding Auroracoin soon? Airdrop to 320,000 people in Iceland is scheduled for March 25th. Exciting times.
First off, love the charts. But I just wanted to say I would pay for the premium version in a heartbeat if it had a more complete list of markets and currency pairs. I find that I have to jump through a ton of sites to find information when I want to invest in other altcoins besides bitcoin. But Bitwisdom is far and above better than all the others. If I could only find charts on less traded coins on Cryptsty or Bter, I would gladly pay the monthly fee.
I changed timezone to Brazil West, but cannot reproduce the issue. It shows hour goes from 0 to 23 when cursor move.
Wait, the problem is real, but occurs only on Safari (5.1.10)/Macbook. It does not occur on Fireox/PCThe problem on Safari occurs only with hours "8" and "9", on the 1h charts, they display as "0" on the crosshair cursor's bottom tab. It does not occur on the 30m charts, so "8:0" and "8:30" display correctly.
It occurred to me that in some languages/systems, a number that starts with "0" is interpreted as octal rather than decimal. In those platforms, "00"through "07" give the same result in octal and decimal, "11" to "23" are interpreted as decimal, but "08" and "09" would be invalid.
Perhaps Safari's javascript differs from the javascript in other browsers in that detail? Sometimes the interpretation of numbers that start with "0" is determined by a global variable, and that variable may have a different default value on Safari?
Hello, is there any possibility that you can implement "ignore trades below xxx" for your great interface?
0.xxxx trades from bots are really annoying to see in trading activities and bid/ask table.
Thanks for reply, or ... implementing that
K.
Actually, I've implemented two different mode for filter trades.0.xxxx trades from bots are really annoying to see in trading activities and bid/ask table.
Thanks for reply, or ... implementing that
K.
The first is let user input the threshold, below xxx will be filtered.
The second is 'auto filter', shows 98.5% total volume of trades, so all tiny trades will be filtered automatically.
But there are some issues when using.
1. There is no good position to place the option.
2. It will increase complex when using.
3. The trades number is not too much. So I won't feel it's great improvement when using even it has filtered 20% tiny trades. Only useful when I need to see the trades which is above 1 BTC only.
So it won't be supported currently.
thanks for reply, but i really dont see problem to implement that (like bitcoinity have).
you have "settings" tab and complex would be same, as you can filter only results not queries
as now there is every 5s trade with 0.01 volume and that is really annoying
(i've just achieved similar result when using tampermonkey, but it is not so nice as i would like to
)
Hello, I love your adding Fib, but I think it'll be great if we could choose our own figures concerning fib retracements and fib extensions. Would it be possible ?
Thanks in advance
Thanks in advance
Since bids increase price and asks reduce it, shouldn't bids be colored green and asks red in the depth graph???
It looks a bit counterintuitive with the current colors.
I guess it's currently intended to mean how easy is for price to go up or down? Thank you.
It looks a bit counterintuitive with the current colors.
I guess it's currently intended to mean how easy is for price to go up or down? Thank you.
I'm not sure I understand the problem. There are two things you mention, right?
1) Problem: Not all exchanges return the entire order book. Solution: Work with what you get. Also, it seems that the currently most important exchange, Bitstamp, does return the full order book, right?
2) Problem: Too much data needed. Solution: Maybe I missed something, but you don't need to keep the order book data, no? Just calculate the ratio once, and keep that. Or did I misunderstand you?
I don't know what happens at the backend of your website, so maybe I underestimate the amount of code needed to make bid/ask work, but to me it seems that if you only store the bid/ask ratio value itself, not the order book data, it's not such a huge amount of data you need to handle... but maybe I'm wrong.
Another 40+ tables needed to save the depth result. 1) Problem: Not all exchanges return the entire order book. Solution: Work with what you get. Also, it seems that the currently most important exchange, Bitstamp, does return the full order book, right?
2) Problem: Too much data needed. Solution: Maybe I missed something, but you don't need to keep the order book data, no? Just calculate the ratio once, and keep that. Or did I misunderstand you?
I don't know what happens at the backend of your website, so maybe I underestimate the amount of code needed to make bid/ask work, but to me it seems that if you only store the bid/ask ratio value itself, not the order book data, it's not such a huge amount of data you need to handle... but maybe I'm wrong.
Then calculate the bid/ask and save to table, embed the result to period.
Modify frontend return the extra field. It cannot not simple added. because it's not apart of trades or period.
Also there are some small issues, such as find a way to make it works in realtime.
Hmm, I see. Can I make a suggestion? Maybe look at bid/ask on the link I already gave above, or on http://coinorama.net/ for example, and see if it helps your own trading in the coming weeks or so.
If it does help you, maybe you can consider implementing it, but if you conclude it's a useless indicator, that's a good reason not to implement it.
Jump to: