Whattomine - profitability website with basic json.

[Mikanoshi]

Yes, mining reward for hashrate (it's in the legend )
I'm just saying that there shouldn't be any distortions like that, chart should be smooth.

[1714871342]

1714871342

[1714871342]

1714871342

[1714871342]

1714871342

[fredeq]

Yes, mining reward for hashrate (it's in the legend )
I'm just saying that there shouldn't be any distortions like that, chart should be smooth.

If nethash drops in half then the diff will sooner or later drop in half as well, this is normal.
Same for increase. Thats why I prefer to look at profitability in 24h intervals.

[gozcominer]

this website look user friendly and very helpful to people when they want to compare altcoin mining

[Mikanoshi]

If nethash drops in half then the diff will sooner or later drop in half as well, this is normal.
Same for increase. Thats why I prefer to look at profitability in 24h intervals.

Second line on chart is 24h diff and it's not dropping anywhere. How estimated_rewards from API is being calculated? Green chart is just this value over time.
If it's based on average 24h block reward and difficulty it cannot suddenly drop 50% and go up 100% in the next half hour, but that's exactly what happens.
I've seen it in another calcs, there it was block reward being detected incorrectly, switches to PoS or MN reward or something like that, and this last block reward value was used for mining reward/profit.

[fredeq]

If nethash drops in half then the diff will sooner or later drop in half as well, this is normal.
Same for increase. Thats why I prefer to look at profitability in 24h intervals.

Second line on chart is 24h diff and it's not dropping anywhere. How estimated_rewards from API is being calculated? Green chart is just this value over time.
If it's based on average 24h block reward and difficulty it cannot suddenly drop 50% and go up 100% in the next half hour, but that's exactly what happens.
I've seen it in another calcs, there it was block reward being detected incorrectly, switches to PoS or MN reward or something like that, and this last block reward value was used for mining reward/profit.

Indeed for aeon there were stats with lower than usual block_reward (around 6).
Thats odd cause the block_reward is fetched straight from the pool.
This happened last time more than 7 days ago. Will be checking this in the future.

[Mikanoshi]

Loki? Block reward there is 116.9 as explorer says, very low deviation (unless you count fees too )

[LuKePicci]

Hi guys, could you provide an educated guess on how much it will take for the new Equihash-BTG algo to be listed? I see mph called the new algorithm "Equihash-BTG" but it is shown as "EquihashBTG" in WTM pages, that will require some dirty translations inside most wtm-based auto-switchers scripts to work. What is the "official" name of this new algo?

[Mikanoshi]

BTG uses Equihash 144,5 aka Zhash, I call all 144,5 Zhash they differ only by personalization string

[whittle]

@whittle @nitro3
Last time I asked dbix devs about working apis for network stats I got no response.
Honestly listing invalid api urls on official website does not inspire confidence.
Guess I will wait for the apiv2? Or the old apis are back online?

This apis do not work
https://api.arabianchain.org/doc.html

[linlinhl]

Added few coins like Aricoin, Honorcoin, Ripoffcoin Wink
Updated Digibyte with multialgo.

Next step - look into Doge merged mining.

[LuKePicci]

BTG uses Equihash 144,5 aka Zhash, I call all 144,5 Zhash they differ only by personalization string

So do you think BTG and other Zhash coins will be listed in whattomine as "Zhash" algo?

[Mikanoshi]

So do you think BTG and other Zhash coins will be listed in whattomine as "Zhash" algo?

That's for @fredeq to decide

This happened last time more than 7 days ago. Will be checking this in the future.

 

Even if fees are included and block reward jumps around, the chart is based on 24h average value that should't change like that.

[fredeq]

BTG uses Equihash 144,5 aka Zhash, I call all 144,5 Zhash they differ only by personalization string

So do you think BTG and other Zhash coins will be listed in whattomine as "Zhash" algo?

Leaning towards renaming BTG to Zhash as well.
This algo will be added to the list for sure. Just wish we had some stable amd miner.

@whittle
Not sure if you are saying or asking, but yes the links in the api docs are not working. Still not working.
http://api.arabianchain.org/v1/dbix/main for example

@Mikanoshi
Price is not 24h average, but always using the last one, so that can cause that "spike" on your chart.
Btw the chart is not in scale, this "spike" is just 2,5% difference.

You can fetch profitability using 24h price average if you wish. Just need to feed the wanted value to the `er` param.

[Mikanoshi]

@Mikanoshi
Price is not 24h average, but always using the last one, so that can cause that "spike" on your chart.
Btw the chart is not in scale, this "spike" is just 2,5% difference.

Chart is a mining reward in Aeon coins per day, based on estimated_rewards from API.
2.5% is a lot if only average values are used, especially when it just goes back to normal 15 minutes later.

[fredeq]

Chart is a mining reward in Aeon coins per day, based on estimated_rewards from API.
2.5% is a lot if only average values are used, especially when it just goes back to normal 15 minutes later.

We could check the data when the next spike appears, but please put the timestamp in utc onto the chart.

[Mikanoshi]

Spikes appear all the time, every single mini jump on that chart is wrong
Average diff does not spike like that, average block reward changes smoothly, so mining reward should too.
This is how chart looks for coin with constant block reward (GINcoin):
 

And this is Loki:


It should mirror the difficulty and slowly go down with block reward.
estimated_rewards is just using current block reward instead of 24h average, isn't it?)

[fredeq]

It should mirror the difficulty and slowly go down with block reward.
estimated_rewards is just using current block reward instead of 24h average, isn't it?)

By default yes. That would explain the spikes.
Need to rethink which coins need to stay on current and which ones to switch to 24h average.
Will tweak this for sure.

[Raymond_B]

Hello, super noob SQL import question. I'd like to import the JSON output in to SQL, but I am struggling with the structure. I can select "coins", but none of the other headers seems available. Anyone done this that might have tips or pointers?  

Edit to be a bit more clear.

I am struggling with the structure of the JSON output. Coins is declared as the top level, but then it gets tough to find the fields and headers so I can properly import them in to columns. Coinwarz is easy to import, but your data and site is MUCH better Is this just the state of things or am I not referencing the JSON correctly?

As a reference https://www.coinwarz.com/content/images/profitability-api-output.png

[Mikanoshi]

How do you import to SQL? What's the problem in iterating through JSON and adding fields that you need? Unless you are not writing a code yourself and using some tool that does it for you.

P.S. I also have some questions then
In global JSON https://whattomine.com/coins.json, what hashrate is used for estimated_rewards/estimated_rewards24 (I assume these are based on current/24 diff)?
And also why changing hr param in API call for particular coin is not changing estimated_rewards accordingly?
E.g. for 10 MH/s it's 636 coins, but for 1000 MH/s it's 62102? 2.35% seems to be a huge rounding error.
I hope estimated_rewards there is based on 24h average diff? Inconsistent field names

P.P.S. ?eth=true&factor[eth_hr]=50 works with global API, default hr must be from some presets... At least write an API docs with all the available params or using it is trial and error.

[Raymond_B]

How do you import to SQL? What's the problem in iterating through JSON and adding fields that you need? Unless you are not writing a code yourself and using some tool that does it for you.

P.S. I also have some questions then
In global JSON https://whattomine.com/coins.json, what hashrate is used for estimated_rewards/estimated_rewards24 (I assume these are based on current/24 diff)?
And also why changing hr param in API call for particular coin is not changing estimated_rewards accordingly?
E.g. for 10 MH/s it's 636 coins, but for 1000 MH/s it's 62102? 2.35% seems to be a huge rounding error.
I hope estimated_rewards there is based on 24h average diff? Inconsistent field names

P.P.S. ?eth=true&factor[eth_hr]=50 works with global API, default hr must be from some presets... At least write an API docs with all the available params or using it is trial and error.

At the moment I am using PowerShell to grab the JSON, works perfect. Where I run in to trouble is the SQL query to import the JSON file. Coins is the first property name, good,  but there is no Coin Name property (the coin names are just listed), so the query blows up. Like I said I am a noob at this and possibly I need to manipulate the JSON and add the coin name property, but I am not sure how.

Below is an example of the JSON, see how the coin name is not under a property?

Code:

{
  "coins": {
    "Cannabiscoin": {
      "id": 188,
      "tag": "CANN",
      "algorithm": "X11",
      "block_time": "44.0",
      "block_reward": 70,
      "block_reward24": 70,
      "last_block": 3030623,
      "difficulty": 159943.13453935,
      "difficulty24": 160679.297308647,
      "nethash": 15612512092414,
      "exchange_rate": 0.00000265,
      "exchange_rate24": 0.00000240881924198251,
      "exchange_rate_vol": 1.78501334098998,
      "exchange_rate_curr": "BTC",
      "market_cap": "$2,845,033.74",
      "estimated_rewards": "298.68986",
      "estimated_rewards24": "297.32436",
      "btc_revenue": "0.00079153",
      "btc_revenue24": "0.00078791",
      "profitability": 115,
      "profitability24": 114,
      "lagging": false,
      "timestamp": 1531882963
    }