There is a long-shot I am wrong... But, from the outside, looking-in... I say that is the issue. (I also noticed that coinchoose seems to purposely be reporting cryptsy's value of CAP short by 0.00001, making it look like it is only valued at 0.00001887, when it is actually strongly trading at 0.00002887. The other places all report the correct value, and the API reports the correct value, which he uses. Might be part of the problem/source. Again, that is pure speculation. I am sure he is just exactly 0.00001 off, randomly out of nowhere, for no reason, the whole time the diff has been falling and value has been falling to match the diff-value.  Then again, all other cryptsy numbers are accurate, to the decimal.) It could be my averaging calculation, but looking at the standing orders I do not think my calc should show a price greater than 0.00019 (since I look at the orders to a certain depth to prevent people / bots from putting high orders to inflate profitability) |
|
|
|
(You never calculate on open-orders... that is potential only. Bots don't list what they actually have to sell, or even real prices. They use probes to "feel the market". You have to look at actual "sold values". The API gives you averages and highs and lows and opens and closes... Though I am not sure why any of those values are not used.)
I debated what price to use and how I would calculate it many many times. I decided to use just the appropriate orders on Cryptsy that sell the alt for BTC / LTC since they represent the immediate translation to the base currency. In addition, by using open orders I reflect what the current market is and not make some hypothetical judgment on where the market will be. In addition, I look to a certain depth to prevent what I saw as market manipulation by people placing high orders to skew prices. This may tilt the profitability numbers downward compared to sites like Coin-Warz, but I feel this is a good thing as an overestimation is more problematic. In addition, based on all the fast comments I get when my profitability is a percentage too high - I'd much rather look at a lower profitability. Besides - my data is based on the current snapshot of data. If you theoretically could mine the coin instantaneous, you'd only have the open orders to deal with. I am happy to PM you my simple PHP code that does the pricing calculation. I just verified that it is working as designed. |
|
|
|
|
As many of you may know, I am the person behind CoinChoose. Since my time has become a bit more strained (as I am working on that trading platform and real life has caught up), I don't feel I can given CoinChoose the attention it deserves. As a result, I am looking at selling the site, code , set-up.
The site collects a lot of data and has potential beyond what it currently does. I know some members here have indicated there are some premium features I could add. In addition, it is at least profitable right now based on its limited AnonymousAd revenue.
I am in the process of listing the site on Flippa (which for some reason calculated the value of the site at six figures), but would like to really sell it to someone in the community. For that reason, I am taking offers here.
I would help with all transition, initial support to get the site up. It uses PHP for its scripting and heavy reliance on Javascript for the display. There are some shell scripts to deal with less resource intensive access to the daemons.
I am happy to answer any questions (though some may require some sort of confidentiality statement).
I am also happy to trade this site....just throwing that out there.
Thanks!
|
|
|
|
Numbers at the moment are 0.00001955 (Which is ARG, not CAP, which is 0.00002920... Unless you are off by 0.00001 for some reason, on purpose...)
CAP also, based on looking at the open orders and how I would sum them to get to the necessary depth, looks accurately calculated. |
|
|
|
Some of the numbers are waaay off... (For cryptsy) One of note is CAP, which seems to be using ARG's values... Not sure which others are incorrect. Cap is reporting as 0.00001778, when it is, and has been 0.00002778 for hours and hours. (Seems to match ARG's values though. So I assume it is an ID mixup for the charts. Might want to double-check all the ID's. CAP's ID is 53 on cryptsy. The numbers report fine through API, both buy and sell values. The reported number for value isn't even between the two values.) Was reporting fine a few days ago... Might have just been coincidence. (Pun intended.) Numbers at the moment are 0.00001955 (Which is ARG, not CAP, which is 0.00002920... Unless you are off by 0.00001 for some reason, on purpose...) How are you figuring out what the price should be? Remember - I do not use the last the last trade value and do not take an average between buy and sell. I do use the API to get the values, but sum up open orders that would allow the given currency to be converted into the base to a set depth. I just eyeballed one of the calcs (Diamond) and it appears accurate. |
|
|
|
...
- but it`s not in a table - it`s kind of random in a table...
So the issue is I make the link clickable to the exchange and the actual text is not numeric. Therefore, what effectively happens is the exchange link causes confusion in Google Visualization. I really need a partner or some to run with this site to take it to the next level  |
|
|
|
Is it just me, or are there a bunch of coins missing from this now???
i noticed too. perhaps server work or a CULL?? of coins to carry. - digeros Yup they are gone for me too. One of our daemon servers crashed due to high load. Should be back up now. |
|
|
|
Yeah - sorting by hash rate is a known issue. I am not sure how to fix it besides just show everything in Khash. Any javascript experts out there have an opinion or a thought?
As far as best price - that sorts it based on the highest price to convert one of the given currency into BTC.
example: Coin Algo Blocks Difficulty Reward Best Price(BTC)▲ Exchange % Profitability of BTC Profitability % Adj for Stales Avg Profitability Past 7 Days Network Hash Rate Avg Hash Rate Past 24 Hours BitcoinBitcoin SHA-256 268850 510929738.01615 25 1. 100.00% 100.00% 100.00% 3834.56 TH/sec 3479.44 TH/sec DevcoinDevcoin SHA-256 113285 228527080.398 5000 0.00000023 mcxNOW 0.01% 0.01% 0.01%  WorldcoinWorldcoin scrypt 773651 9.922 57.88045 0.00010012 mcxNOW 1,193.64% 1,003.06% 1,404.71% 1.23 GH/sec 1.24 GH/sec MincoinMincoin scrypt 236800 4.823 2 0.00080103 mcxNOW 678.86% 627.52% 732.33% 84.86 MH/sec FeathercoinFeathercoin scrypt 111570 119.772 200 0.00034 BTC-e 1,160.31% 1,131.06% 1,150.70% 3.08 GH/sec 3.23 GH/sec TerracoinTerracoin SHA-256 213252 222557.99576 20 0.00041 BTC-e 75.30% 72.77% 85.03% 1.49 TH/sec 1.58 TH/sec ExtremecoinExtremecoin scrypt 17577 0.51965 1 0.00001161 Bter.com 45.66% 45.28% 451.04% 1.34 MH/sec 21.61 MH/sec WorldcoinWorldcoin MincoinMincoin FeathercoinFeathercoin - sorted by best price... 0.00010012 < 0.00034 < 0.00080103 - but it`s not in a table - it`s kind of random in a table... Must be a bug within Google visualization. Sort looks fine here. I'll report it and see.. |
|
|
|
You mean just that column or are you seeing other columns not sorting either?
[..] - sorted by hash rate - all mixed: 1.51 TH is smaller then 136.84 MH for ex. 2-nd and third lines... [...] -s sorted by best price.... what the does it mean? ) Thank you! Yeah - sorting by hash rate is a known issue. I am not sure how to fix it besides just show everything in Khash. Any javascript experts out there have an opinion or a thought? As far as best price - that sorts it based on the highest price to convert one of the given currency into BTC. |
|
|
|
Coinex has no volume why add it at all? Adding an exchange before it has a reasonable amount of volume it stupid Please consider to remove CoinEx quotation for ANC .
They say their wallet has issue and there is a total out of market buy offer there.
IMHO It is just smoke and mirrors and it modifies at the limit of lecit profitability for that coin.
Darkest
Ummm...if it has no volume there would be no pending trades. There are pending trades. |
|
|
|
Nice - wonder if there is some integration we can do. This is also open source and a trading platform to provide automated systems, graphing, etc. |
|
|
|
Okay - I will be putting the code up tonight and now working on expanding this to be more user friendly, but have it hooked to BTER. More eye candy:  |
|
|
|
Hi. can you please fix sorting? - it`s not sorting correctly any columns by values like of Mhash are on top of Ghash
or currency exchange rates are mixed... if sorting asc or desc (
Thank you!
You mean just that column or are you seeing other columns not sorting either? |
|
|
|
I sent them an email and updated their thread.
I got Coinwarz to update their stats and I'm waiting on an answer from coinchoose (which is still showing 20 block rewards).
Fixed now? |
|
|
|
IFC coin per block is wrong? should already halved.
I'll check and it likely is wrong. |
|
|
|
Just wanted to let ya'll know the difficulty algorithm has been fixed in the latest update. The hashrate should also correct itself over the next day or two. Thank you.  When did the latest update occur - I just synced up about 24 hours ago? 2 updates occured 1 after the other. You need Client Version 0.7.1.4 *sigh* Ok. Any more updates anticipated soon? |
|
|
|
Why is Worldcoin (WDC) not listed? It's quite often right up the top on profitability.
Because I haven't had time to add in the changing profitability logic - working on it. |
|
|
|
Just wanted to let ya'll know the difficulty algorithm has been fixed in the latest update. The hashrate should also correct itself over the next day or two. Thank you. When did the latest update occur - I just synced up about 24 hours ago? |
|
|
|
Good riddance. Yeah Illuminati!! |
|
|
|
coinwarz lists it as Block Reward: 60.25. im not sure how they do this but it shows its possible to include it on a profitability chart
Well, it might be possible but no one in the WDC thread gave me a hint at how to do it. I take that as they don't want it on my site. Have you taken a look at this code? https://github.com/worldcoinproject/Worldcoin/blob/master/src/main.cpp#L833-L865It looks like after block 600000, the initial reward was changed to 64, and it is decreased by 1% after each "week" (20160 blocks) I think my biggest issue is understanding what a week was. Looks like this code makes it clear that it isn't as week but something else . Good, let me tinker a bit. |
|
|
|
|
Show Posts
