|
Indeed qkc calcs are not correct.
Switched coin back to testing state and will figure out the correct formula as it differs somehow from default ethash.
|
|
|
|
Hello!
Can you share at which pool you have been mining exactly? QKC has multiple chains and they vary in difficulty. |
|
|
|
Hello!
The calculator calculates QKC incorrectly
I noticed this before and thought that I would fix the error, but after a few months everything is still the same.
I connected one farm with 220 megahashes, the calculator writes 488.5793 current income and QKC 476.5064 per day.
Miningpool paid an average of 100 QKC for 10 hours, which is 240 QKC per day. The calculator cheats by 2 times.
Hey, best to report those problems as soon as they happen. Faster on discord as well. Will check whats going on with qkc. |
|
|
|
For example, "eqa" query parameter corresponds to "Equihash (210,9)" algo name returned in the JSON response. This is something I figured out, but there are some query params like "cnh" or "cm29" that are harder to correlate with algo names returned by JSON response. It would be awesome if JSON response for each coin contained this shoretened algo name that could be correlated with the URL param. That way I could reliably determine the power usage of the GPU for the corresponding algo and substract the power cost from the revenue returned in JSON response to get profits. AFAIK no matter what kW/h price I send in the query param it will always produce the same JSON response with revenue based on hashrate. I know you have this logic somewhere in the backend because the website frontend shows profitability (as opossed to JSON that only shows revenue).
I would say scrape for now is the best option. You have translated algo param names to algo names so it should be fine now? If you dont mind the possibility of response format changing at one point then check for JS call made in the browser (adapt) on https://whattomine.com/coinsAs long as you plan to use our data on some other website it would be welcome to put a link + explanation on your side. |
|
|
|
fredeq is the premium access and api somewhere on the roadmap or is it just an idea at this point?  Api is ready, the docs and premium access are missing. But what do you need it for? Its gonna basically do almost the same stuff as current json |
|
|
|
|
No navi support for aeternity / bittube?
Polaris works fine.
|
|
|
|
Thanks, got it now - its based on pow block count only but its hard to track, havent seen any official api giving this info. Would be cool to switch to global block_count as halving trigger. |
|
|
|
|
Could someone please share reward halving interval (+offset) / halving schedule?
At which block numbers does it happen exactly.
|
|
|
|
I have a question regarding JSON response, sorry if you already answered it somewhere (search didn't help).
Is there any way to programmatically obtain hash values for each GPU ? I'm making a Python script for ROI calculation for each available GPU, and I had to manually hardcode hash values that pop out on your website after selecting a specific GPU. I've tried constructing the query URL without those parameters but JSON response gives default calculations in that case (3 x 480 cards).
Thanks!
At this moment we do not have a stable api response that you could call for all gpus hashrate. It could be possible to tap into js response of /coins adapt call for gpu values but thats not the intended way (we could change the format/architecture at any point) Maybe it could be bundled with user premium access and api |
|
|
|
|
Updated beamhash3 GPU hashrates for BEAM with latest miniZ and lolMiner
Reselect cards to get new values.
|
|
|
|
|
Extracted RVN to separate KawPow form and updated amd gpu values for latest teamredminer.
|
|
|
|
Already looking into it  |
|
|
|
|
Any working explorer with api?
|
|
|
|
Yes we can make it. I will. Will release image within 2 days.
Great news, looking forward to it  |
|
|
|
I can only get lolmner to mine .3 on c31 on my 5700s, worked fine on windows.
Getting the same problem here. Also getting other problems around new amd cards with lolminer @ 19.5 build and old cards with 18.2 build. Lolliedieb confirmed that navi cards wont work for ct31 and 19.5 drivers. Any chance there was a smos build with 19.3? They seem to be more stable and well running. |
|
|
|
Claymore will not support this.
lolminer should but i guess it has problems too.
Can you try phoenixminer too ? -it should be working with phoenix
Phoenix managed to start. Ok so this is miner problem not supporting newest drivers, damn. Need this mainly for benchmark, will manage somehow |
|
|
|
|
Is it possible to mine on polaris gpus with "SimpleMiningOS (SM-5.0.21-9-a19.50-n440.44)" version?
I have a mixed rig vii+vegas+polaris and with that version only vii+vegas are actually mining.
Polaris cards are detected, can see and configure OC for them, but both claymore and lolminer see only vii+vegas as available for mining.
|
|
|
|
Previously, I had some experience in ProgPoW programming and can confirm that the DAG is 100% identical with Ethereum.
Size also matters though. BCI grows slowly and remains small if I am not mixing coins. SERO on the other hand already has significant DAG size. |
|
|
|
Hi,
tried to find, but failed,
tell me plz, is there an API for fetching your jsons?
tnx in advance
Json is all there is - always marked by UI button on the top. There are no docs if thats the question. Params are the same as used in general UI urls. |
|
|
|
it's pointless and does not worth it.
Pointless for grin maybe, but mwc will stay on this algo without fading. |
|
|
|
|
Show Posts
