Honestly I am thinking that weighted average is the explanation here. Simple average wont represent the data well, cause you can have many blocks stacked in short period with low diff. In other words taking all blocks from last 24h and calculating simple avg is not good or wanted. It matters how long each difficulty period was mined for. |
|
|
|
So, how that STRAKS test went?) I'm running nodes for new coins and then switch to WTM when they appear there, generally WTM avg diff is 0.5-5% higher than the real one.
The only exception is STRAKS where it's always 20-25%. Considering 5-10% or even more can be wasted on some random things during mining, it can be closer to reality, but still it's not right.
I prefer correct values and then you can apply -10% if you want it to be more realistic and not theoretical.
Nothing new since last time. Feeling the same way as you do, would be better to have closer average diff and then manual fee if needed. Will continue with straks after I will process the last batch of requests and emails. |
|
|
|
|
Whats the exact miner reward?
Every site I can find lists this as 50, but I got some sources that 20% from that is going to the devs leaving 40 to the miner.
|
|
|
|
Lyra2z added to the GPU list. Luxcoin delisted due to algo switch to new PHI2 - hardfork still not finished. @oubee1 Not sure what you mean honestly, posted in the wrong thread?  |
|
|
|
|
Revert back to Cryptonight a few days after nicehash added cn-heavy?
Was that the reason?
|
|
|
|
Hi! Do you have some pools list on the Whattomine web page? We'll be glad to be added.
We are uCrypto.net multipool with low fees and cryptocoin variety - 18 coins based on the Ethash and Equihash algorithms.
Hey, thanks for reaching out. No list like that yet, but it might be coming. There will be channels open to sign on the list once ready. |
|
|
|
|
Mpos pools let you query for current difficulty, same as explorers.
Agreed that calcs need to originate from difficulty - all coins are calculated this way.
|
|
|
|
Because they are down randomly  Explorer API provides all the required commands though. for (i = last_block_in_db; i <= getblockcount; i++) { getblock(getblockhash(i)) }Hehe true, some of them go down quite often. In more than half of the cases the data is fetched from pools or other custom apis, so there is no way to pull all the blocks. Soon I will reach 24h on the test mining and looks like the calc is ok. I know it uses the average diff around 20% higher than what would be calculated from simple average of all blocks. We could ofc pull the entire chain for straks, the values for diff would be smaller but then again estimated_rewards would be 20% higher and not correct. Now the reason for this is not yet clear to me, though I have a feeling this might be caused by using a simple average vs for example weighted one. |
|
|
|
Why do you grab current diff instead of diff for every block since last poll? And explorers are unreliable. I'll have to run more nodes  Cause I am not running nodes for most of the coins. Not sure why do you think explorers are unreliable though. Running a test on straks now, will compare with calc when done. |
|
|
|
So there won't be a fix for diff calculation? I guess it's safe to assume WTM is totally inaccurate then.
P.S. What's up with ORE, lagging for more than a day?
I have reduced polling time for straks, but it didnt help much. At the end of the day calcs are correct for me on other coins - still need to check straks to make sure. ORE official explorer is down. |
|
|
|
How is "profitability" calculated? it doesn't make any sense to me. Some examples from the ASIC tab today using 0.075 $ power:
Bitcoin: Revenue is showing as $6.46, profit is showing $3.74 and the profitability is showing as 100%. There isn't any math I can figure where profitability is 100%.
Siacoin: Revenue showing 3.93 and profit is 1.59 and profitability is 60%.
The way I would normally look at profit margin or profit ratio would be profit over power so in the case of bitcoin it would be $3.74/($6.46-3.74)= 1.37 so a 1.37 or 137% profit ratio of net revenue over power. I have no clue where the 100% comes from.
Can someone help explain or point to a formula that explains the profitability calculation on the site?
The naming is not accurate - its based on revenue in BTC. 100% is a base to compare other coins to either BTC or ETH. |
|
|
|
It is an average diff, not sure why it would be wrong though. Can you explain what are you comparing it with?
Sum up diffs of every single block for the last 86400 seconds, divide by their count. I get 1254: https://blockstats.pw/straks/WTM shows almost 1600, so I'm also not sure how that is possbile I'm running a node and use blocknotify to get data for each block and put it in DB. SELECT COUNT(`diff`), SUM(`diff`) DIV COUNT(`diff`) FROM `straks_pow` WHERE `time` >= (UNIX_TIMESTAMP() - 86400) Returns block count = 1290 (~67 sec per block, matches WTM) and 1254 avg diff. Indeed my average is higher than the real average. From what I can see its caused by lowered diff periods of around 300-500, where many blocks are mined in short time and not all of them are cached into the db. Now the question remains which average is able to produce closer estimated_rewards. |
|
|
|
@fredeq Isnt it possible to change the web page layout so adding new algos doesnt need to remove other ones? Cost, Sort, Volume, difficulty and exchange columns can go below algos in one single line then you can add 3 more algos That would be a solution, but currently all algos moving away from gpu section are a result of asics being introduced for those algos. No point to keep those algos in the gpu section. @Mikanoshi Still alive and well It is an average diff, not sure why it would be wrong though. Can you explain what are you comparing it with? @mmortal03 Will check last CN values and copy them to CNv7 @xiders Unfortunately the block explorer that provided complete 5 algos diff api has been taken down. I have reached out on discord to ask for a similiar api, but nothing so far. Was using a clearnet node before for verge, probably will have to get it running again via tor. |
|
|
|
|
@Atexor
Havent processed it yet.
@YarMiner
Your logic looks sound and it should work for all coins.
Maybe you have wrong nethash values to start with?
|
|
|
|
|
Do you plan to stay on cryptonight algo for asics?
|
|
|
|
Please use the contact form on the website and include all the required info. |
|
|
|
|
@Navidz
Markets supported by the website are missing.
Will not list an algo which only coin runs as multi-algo. You can still calculate at single pages.
@lukemanz
Market added
|
|
|
|
|
Show Posts
