You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm confused about how you're reaching the numbers you claim, specifically for the 1hr attack cost.
First, you take the algorithm's p value from the stats. I'm presuming that p means price, but it's very ill-documented on Nicehash's api doc, and you seem confused about it too.
Then you divide this value by 108. It seems like you're doing this to normalize from 100 GH to 1 H... But I'm not sure why you're sure that the p value from Nicehash is always denominated in GH since Nicehash uses TH, PH, GH, etc. as well. Either way, this value is in BTC/xH/Day (where x is one of TH, PH, or whatever).
Lastly, you multiply this value by the network hashpower. But, nethash is denominated in H/sec and you're multiplying by BTC/H/Day. Don't you first have to convert the pricing to per-second? (Or nethash to H/Day)
The text was updated successfully, but these errors were encountered:
I'm confused about how you're reaching the numbers you claim, specifically for the 1hr attack cost.
First, you take the algorithm's
p
value from the stats. I'm presuming thatp
means price, but it's very ill-documented on Nicehash's api doc, and you seem confused about it too.Then you divide this value by 108. It seems like you're doing this to normalize from 100 GH to 1 H... But I'm not sure why you're sure that the
p
value from Nicehash is always denominated in GH since Nicehash uses TH, PH, GH, etc. as well. Either way, this value is in BTC/xH/Day (where x is one of TH, PH, or whatever).Lastly, you multiply this value by the network hashpower. But, nethash is denominated in H/sec and you're multiplying by BTC/H/Day. Don't you first have to convert the pricing to per-second? (Or nethash to H/Day)
The text was updated successfully, but these errors were encountered: