Hello! Please, can anyone explains me?..
1. On tab GPU when I click adapter button, for example 580 it highlited red, but 1050Ti highlited green, what it means? 2. On tab Asic I don't see choose of model. Parameters that giving default, for example for SHA-256 from Antminer S17 I think, but for another algo from where do I see it parameters?
Hey! 1. It means that the GPU is selected for adapt values in given quantity. 2. On asic we roughly estimate other algos hashrate and power to the equivalent cost of one S17.
|
|
|
For mining Ethereum with the 480 card, which driver is better to use and which hashrate should be?
You can use the latest Adrenalin 2019 and get 31-33-35Mh. what's wrong ? followed the advice and only 12 mh. on the forks of ethereum 29 mh. Check -y setting to enable compute mode
|
|
|
Hi guys. Has anyone tested Vega56 with 14.6? I find quite different information about the mining speed with the new claymore miner, from 47 mh/s to 55 mh/s. Any info about power consumtion? I will buy new video cards and i'm hesitating what to buy. Thanks in advance.
In my test vega56 51.3mh/S and 175w. Radeon7 101MH/s and around 250w. How do you get such hashrate with Vega56? I get about 45 Even more interested about rad7 here. Running 90 here would result in draw of 280w. Vega56 also feels strange below 200-230w
|
|
|
Any plans for x25x for suqa rebrand?
|
|
|
The bot of this service in telegram is very convenient, I advise.
Keep in mind its not our official channel though. If you need something confirmed 100% please always check here or on discord.
|
|
|
Added adapt values for radeon VII Ethash running on reduced clocks to avoid high temps and throttling.
|
|
|
Hi NOOB here Does anyone know of any secret ETH miners as whattomine now shows 80mh for vega 64. They show 90 for radeon vii and are usually accurate about this stuff. The max I can do is 47.5 on a vega 64 with rare incorrects I am not sure if this is an error or some new information that we should all know
Thank you
Code introducing VII started to multiply v64 hashrate by accident. Bug fixed now, thanks for sharing!
|
|
|
This is only on a rig with 2 GPUs, if you got more than 4 GPUs then you got no choice but to upgrade because from what I recall you can't use more than 4 GPUs. There was a fix for this during the Litecoin mining days of 2014 where you installed a patch, however that patch only worked with older GPUs like R9 280X. Reason why is because it only patched an old AMD drivers version from like 2015, the newer ones were never patched since most people just used Win 10 to mine.
Patch still worked for me last year with polaris cards, but yeah its best now to stick to win10 or linux.
|
|
|
What's with Galactrum (ORE)? =)
Coin switched to PoS, thanks for the ping, updated
|
|
|
Updated asic view to adapt values for equivalent cost of one S17 (approx) Added five new/old algos to asic: BCD, Lyra2z, PHI1612, Keccak, Groestl
Some units are different between asic and solo forms, but there is a plan to unify them finally in the coming weeks.
|
|
|
HUSH difficulty seems to be too low. They started new chain, block height is around 3000 now.
Thanks for the ping, switched to follow new chain.
|
|
|
Golden. Will it work on future amd cards, or you need to update everytime new gpu is released?
|
|
|
I see also NiceHash listed as separate coins, but with sone different data. How is revenue calculated for NiceHash coins???
Not sure what you mean by some different data. Revenue is calculated from your input hashrate and nicehash api 24h payouts (by default) @tbates76 Not adding more exchanges at the moment. Will take note on graviex.
|
|
|
@Beave162 Listed CryptoNightR with monero and lethean in the GPU section. XHV haven and TUBE saber will now calculate with heavy values.
|
|
|
BTCP delisted from Hitbtc ? Cant find any info about, also confused whats going on.
|
|
|
Added CuckooCycle for aeternity to GPU list with nvidia values. Binance is not accepting the main token deposits yet, but gate.io is and the market for it was also added.
ETH reward dropped, difficulty looks stable already.
|
|
|
Which formula?) Looks like it's just (86400 * 60 * hashrate / diff) E.g. for 100 H/s WTM shows ~3.56 coins/day, which exactly matches the above. For nethash = 2.1 MH/s reward will be 74872 coins/day, not far from current total daily rewards of (86400 / blocktime * 60) = 76235 But it's not correct, should be 76235 * 0.87 = 66324 Or maybe I'm wrong Think the main confusion here is coming from your equation of `76235 * 0.87 = 66324` The block_time given on wtm is estimate of *only* cr29 blocks, so your equation should either be `(86400 / 60) * 60 * 0.87` or `(86400 / cr29_block_time) * 60` In other words, 0.87 is already covered within block_time.
|
|
|
So WTM rewards for 29 algo already take current 87% into account?
Sure, we always want to estimate the return you would get from mining on a pool. Formula was tested over few days of mining.
|
|
|
I am aware of the variable distribution logic. But what that has to do with us listing ct31?
|
|
|
GRIN has 10% pool fee, is it the part of blocks that's going to cuckaroo31 now? Any plans to add 31 separately?
10% is for negative pool luck or whatever is wrong with hashrate displayed in the miner compared to real hashrate (does not mean hashrate reported by pool) Will add ct31 for sure, but not working on it currently. High mem requirement makes it low priority.
|
|
|
|