Yes I found "eth_submitHashrate" but I'd like to check some miner that sends this command to see how it works. There is no any documentation about it but it seems it has two params: first is the hashrate, second is filled by random and it's strange, it must be worker name so pool can know who reports the hashrate. I confirmed with dr_pra that the 2nd param is ignored (at least by ethpool/ethermine). If more then one worker connects via a stratum proxy, submitted hashrate doesn't work. If a single worker is used on a connection, the hashrate is assosiated with that worker.
|
|
|
Yes I found "eth_submitHashrate" but I'd like to check some miner that sends this command to see how it works. There is no any documentation about it but it seems it has two params: first is the hashrate, second is filled by random and it's strange, it must be worker name so pool can know who reports the hashrate.
https://github.com/ethereum/wiki/wiki/JSON-RPC#eth_submithashrateParams: 1. Hashrate, a hexadecimal string representation (32 bytes) of the hash rate 2. ID, String - A random hexadecimal(32 bytes) ID identifying the client I am fairly sure most of the pools just ignore the ID string. Could ask dr_pra or miningpoolhub to confirm how they how they handle it.
|
|
|
Source code please. And if you publish build steps that would be amazing. Many people struggled with compiling qtminer.
|
|
|
@Claymore so far so good im quite happy 15h straight without major problems, keep up the good work only problem so far was crashing while i tried changing cclock and mclock(no matter if over or underclock), and not showing reported hashrate on ethermine.org only effective current hashrate is visible even after adding worker name and changing esm to 1 -tt works ok, after some time it stabilizes fans speed
"-esm 1" works, miner must write "qtminer mode" during start. Just wait some time (an hour) and pool will show info about shares. Check this topic a few pages ago there was same problem and it was solved. I think people are talking about the eth_submitHashrate stratum method that eth-proxy supports. Ethermine/ethpool and mph (maybe others) will show your "reported hashrate," as in, reported by the mining software.
|
|
|
edit "start.bat" file example from claymore start.bat .. notice i've added the clock settings in the syntax. GPU_FORCE_64BIT_PTR 0 GPU_MAX_HEAP_SIZE 100 GPU_USE_SYNC_OBJECTS 1 GPU_MAX_ALLOC_PERCENT 100 GPU_SINGLE_ALLOC_PERCENT 100 EthDcrMiner64.exe -epool us1.ethpool.org:3333 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F -epsw x -dpool stratum+tcp://dcr.suprnova.cc:2252 -dwal Redhex.my -dpsw x -wd 1 -cclock 1100 -mclock 1375
and read the "readme.txt" file you'll learn more That won't do anything... you need to prefix those lines with setx e.g. setx GPU_FORCE_64BIT_PTR 0
|
|
|
After a few hours, I am at <1% DCR rejects on stratum. No change to ethash output. Big improvement from 20-30% rejects with http getwork.
|
|
|
I'm a little curious as to how the developer fee is applied in a rig with multiple cards with some GPUs restricted to mining Ethereum only and was wondering if they were taxed 2% just like those mining Ethereum as well as Decred.
Probably. Could always run 2 instances if you're using different modes.
|
|
|
i thought the algo was most efficient running in increments of 250mhz..
that seems to hash out with my testing too.. for another 50mhz mem clock you should see nice gains.
It's unlikely anything to do with the algo or some ratio, and almost certainly to do with mem straps. Don't think I've ever seen the memory timing ranges posted for fiji cards. They may align on 250mhz.
|
|
|
v2.0 with Stratum for Decred and many improvements/fixes wil be available within 24 hours.
Stahp making me wait to give you 2% of all my hashes! Oh wait, I already am. <3
|
|
|
I will do the same. I save all the Ethereum I mined recently. When the price reaches 0.04 to 0.06, I will sell some.
You're dreaming. I doubt we'll ever see Ether get that high, at least not unless something bad happens to the bitcoin network. I personally think Eth hit it's ATH already and will only consolidate downwards from here. Building the EVM as a mandatory part of the blockchain really isn't very novel or even a good idea. It makes endlessly more sense to keep blockchain (the ledger) and purpose (e.g. distributed computer) separate.
|
|
|
Eth mining is still very profitable right now even if you are paying for (reasonably priced) power.
|
|
|
Why Decred Claymore ? Just asking. I actually like the coin too, buy tokens, get POS, etc.
Probably because it's very processing intensive but not memory intensive. Good combo with Ethash. I like decred as well, and think it has a fair bit of potential.
|
|
|
90% likely Decred will be less than worthless within 7-10 days if not sooner. The market was already very small for it and now we are increasing the supply for sale dramatically while not bringing new buyers, and exponentially making it beyond reasonably difficult to mine for those who were in that community before we arrived. If it can recover after we stop mining it due to being less valuable than the devfee and lost eth hash it costs us to get, then the extreme low prices coming to it over the next week will look like the golden age to the original Decred folks. Until we start mining it again after the recovery..
That makes absolutely no sense... total mining output is a fixed value, doesn't matter if more people start mining. *sideways look*
|
|
|
Getting much lower DCR rejects (and it looks like the exact same eth hashrate) with -ethi 8 . Went from 15-25% rejects with -ethi 16 to ~5% with -ethi 8.
|
|
|
edit: coinmine has lower rejects, but i'm getting some disconnects here and there...
So far on diff 8 : 74 accepted, rejected 3.
I was still at 10%+ rejects when I tested coinmine for DCR.
|
|
|
I have observed similar results over 24hr+. Invalid shares have dropped to nearly 0, where 1-3% was typical with ethminer (any variant). And, total submitted shares have definitely increased. Watching GPU usage %, with claymore they stay at 100% almost all the time. With genoil or web3 ethminer, there are constant dips to 0%. Not to mention this miner seems way more stable and consistent. I do get stupidly high DCR rejects tho (10%+), no matter what difficulty I use. Hoping the next version with stratum support will improve that. I've tried every pool and they all seem the same. Using 64 diff I can get down to maybe 8% rejects, but round variance is quite high.
|
|
|
Indeed, you are correct. Was a stupid mistake on my part. Apologies for false alarm.
|
|
|
v1.1:
- Fixed issue with rejected shares for dwarfpool (and for other pools that use similar code). - Fixed issue with f2pool pool. - Added "-worker" option. - "-dcri" option: max value is 500 now. - Added "Rejected shares" info.
f2pool working now, but --eworker option doesn't have any effect there (all shares show up under the blank worker).
|
|
|
qtminer = 60mh/s Claymore = 45mh/s
why ?
(i have 4x r7 370 and crimson 15.12)
Read the known issues...
|
|
|
|