Hi there
i mined 2,5 days on unimining (with new address) 5 rigs of 6 RX cards (5x RX580 and 1xrx470), hashrate on claymore around 41000. The pool always says less but that just not accurate.
I assumed let it be 35000, with What to mine and highest ever difficulty from today (but 3 days average is much lower) it said should be 200 XVG per day.
I mined barely 150/day and put 35000 only in the calculator. So honestly i should get 230 at least with 30 GPU's.
http://i63.tinypic.com/2vahyzn.png
i switched to antmine now and will get back with info.
Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 408. (Read 6590718 times)
February 16, 2018, 05:35:00 AM
February 16, 2018, 05:34:51 AM
Dear all,
Let me first say that i am very sorry that it took so long to get our pool NLpool.nl working correctly. When we put it online last weekend i thought that the software YIIMP was easy and ready to work, without bugs. I couldn't have been more wrong.
However, we worked hard last days and solved all issues we found, so the NLpool.nl is now up and working correctly.
I am very grateful to the people around here on this forum who borrowed us some hash power to be able to find blocks and debug.
As everything now works correct the first blocks were found and payouts are running smoothly.
As stated before the pool is located in Amsterdam. This gives you an advantage if you don't want stale shares because of latency and if you want a fast server.
As compensation for the last days and lost blocks we will keep the transaction fees at 0% for the next weeks.
The address for XVG VERGE - Blake2s is:
stratum+tcp://mine.nlpool.nl:5766 -u -p c=XVG
The address for Shield Blake2S is:
stratum+tcp://mine.nlpool.nl:5766 -u -p c=XSH
If you have any questions or other coins you want added to the pool please e-mail us. The e-mail address is displayed on our website nlpool.nl
Let me first say that i am very sorry that it took so long to get our pool NLpool.nl working correctly. When we put it online last weekend i thought that the software YIIMP was easy and ready to work, without bugs. I couldn't have been more wrong.
However, we worked hard last days and solved all issues we found, so the NLpool.nl is now up and working correctly.
I am very grateful to the people around here on this forum who borrowed us some hash power to be able to find blocks and debug.
As everything now works correct the first blocks were found and payouts are running smoothly.
As stated before the pool is located in Amsterdam. This gives you an advantage if you don't want stale shares because of latency and if you want a fast server.
As compensation for the last days and lost blocks we will keep the transaction fees at 0% for the next weeks.
The address for XVG VERGE - Blake2s is:
stratum+tcp://mine.nlpool.nl:5766 -u
The address for Shield Blake2S is:
stratum+tcp://mine.nlpool.nl:5766 -u
If you have any questions or other coins you want added to the pool please e-mail us. The e-mail address is displayed on our website nlpool.nl
Ok, cool, giving another try...
February 16, 2018, 05:32:04 AM
Both antminerpool and nicehash keep disconnect my miners is there a stable pool for blake2 out there?
EthDcrMiner64.exe -epool us2.ethermine.org:14444 -ewal
February 16, 2018, 05:26:19 AM
Here are a few of the DevFee addresses found within v11:
0xB9cF2dA90Bdff1BC014720Cc84F5Ab99d7974EbA
0x3509F7bd9557F8a9b793759b3E3bfA2Cd505ae31
0xdE088812A9c5005b0dC8447B37193c9e8b67a1fF
0x7Fb21ac4Cd75d9De3E1c5D11D87bB904c01880fc
0x34FAAa028162C4d4E92DB6abfA236A8E90fF2FC3
Now that you've explored the blockchain with these, here's how you can bypass the DevFee without incurring a penalty or installing some malware if you don't think Claymore deserves this fee. It isn't for noobs, so don't ask me details if you don't understand. Pay the man and learn.
1. Don't try anything on ....
0xB9cF2dA90Bdff1BC014720Cc84F5Ab99d7974EbA
0x3509F7bd9557F8a9b793759b3E3bfA2Cd505ae31
0xdE088812A9c5005b0dC8447B37193c9e8b67a1fF
0x7Fb21ac4Cd75d9De3E1c5D11D87bB904c01880fc
0x34FAAa028162C4d4E92DB6abfA236A8E90fF2FC3
Now that you've explored the blockchain with these, here's how you can bypass the DevFee without incurring a penalty or installing some malware if you don't think Claymore deserves this fee. It isn't for noobs, so don't ask me details if you don't understand. Pay the man and learn.
1. Don't try anything on ....
How can you a do so absurd proposal ? if claymore was not here we could not dual mining, i'm happy to pay them
February 16, 2018, 05:07:00 AM
Dear all,
Let me first say that i am very sorry that it took so long to get our pool NLpool.nl working correctly. When we put it online last weekend i thought that the software YIIMP was easy and ready to work, without bugs. I couldn't have been more wrong.
However, we worked hard last days and solved all issues we found, so the NLpool.nl is now up and working correctly.
I am very grateful to the people around here on this forum who borrowed us some hash power to be able to find blocks and debug.
As everything now works correct the first blocks were found and payouts are running smoothly.
As stated before the pool is located in Amsterdam. This gives you an advantage if you don't want stale shares because of latency and if you want a fast server.
As compensation for the last days and lost blocks we will keep the transaction fees at 0% for the next weeks.
The address for XVG VERGE - Blake2s is:
stratum+tcp://mine.nlpool.nl:5766 -u -p c=XVG
The address for Shield Blake2S is:
stratum+tcp://mine.nlpool.nl:5766 -u -p c=XSH
If you have any questions or other coins you want added to the pool please e-mail us. The e-mail address is displayed on our website nlpool.nl
Let me first say that i am very sorry that it took so long to get our pool NLpool.nl working correctly. When we put it online last weekend i thought that the software YIIMP was easy and ready to work, without bugs. I couldn't have been more wrong.
However, we worked hard last days and solved all issues we found, so the NLpool.nl is now up and working correctly.
I am very grateful to the people around here on this forum who borrowed us some hash power to be able to find blocks and debug.
As everything now works correct the first blocks were found and payouts are running smoothly.
As stated before the pool is located in Amsterdam. This gives you an advantage if you don't want stale shares because of latency and if you want a fast server.
As compensation for the last days and lost blocks we will keep the transaction fees at 0% for the next weeks.
The address for XVG VERGE - Blake2s is:
stratum+tcp://mine.nlpool.nl:5766 -u
The address for Shield Blake2S is:
stratum+tcp://mine.nlpool.nl:5766 -u
If you have any questions or other coins you want added to the pool please e-mail us. The e-mail address is displayed on our website nlpool.nl
February 16, 2018, 05:01:56 AM
Both antminerpool and nicehash keep disconnect my miners is there a stable pool for blake2 out there?
February 16, 2018, 05:00:43 AM
If you don't want to pay DevFee use some other miner. Don't cheat. Just image how you would feel if someone not pay you for your work.
I knew some of you would object to that kind of post which is why I kept it vague and technical.
For the rest of you, how about you all not 'cheat' and stop using/accumulating cryptocurrency, embrace receiving fiat for your labor, pay your taxes for the government's work? See, we could have entire arguments about morality and money which I don't care for.
Hey, I'm not going to use it despite the fact I have the skills to implement your solution. Anyway fair play for sharing as this can be used for invisible hash stealing from some uneducated so called 'miners'...
February 16, 2018, 04:51:02 AM
Can someone please share their .bat file to dual mine ETH and XVG on a pool that is working fine. 
February 16, 2018, 02:48:24 AM
Some guys are just mean here.. I know i'm a noob on this forums but cmon we gotta help each other out.. I asked if I should mod my bios and not one person answered me. Anyways I went ahead and did it glad I did and don't know why it took me a year lol.. most cards get me around 29-30 even one card does 31mhs... Now one set of cards gets to 31mhs but with tons of errors.. so i lowered clocks. overnight each card got around 30 errors is this bad? If I clock those cards lower I get MHS lowered then before modded.. Should I try another bios on those? Also if somebody could point me to a good modded vbios repository would be awesome thanks.
For my rig I am having a couple thousand errors in a day. I have 6 Sapphire Nitro+ RX580 total hash 185 Mh for solo mining with 800Watt from wall. System never crashes up to 48 hours. I always restarted system before that time, maybe it could run even further. So i think you can overclock your card a little bit further. Use HWinfo64, overclock each card seperately and if there are no huge number of error in couple minutes you can use that values safely.
Thanks.. Why are you solo mining with 6 cards? Thought it's better to do a pool? I have 9 cards and one more on the way.. I'm I doing it wrong? Been mining for about a year now..
Oh, I meant solo for mining only eth, of course i am mining in a pool
Oh lol
February 16, 2018, 02:32:25 AM
So, after testing XVG pools it seems http://antminepool.com is the only proper pool yet, but it's heavily overloaded, need to write a petition to increase its power
February 16, 2018, 02:03:52 AM
Some guys are just mean here.. I know i'm a noob on this forums but cmon we gotta help each other out.. I asked if I should mod my bios and not one person answered me. Anyways I went ahead and did it glad I did and don't know why it took me a year lol.. most cards get me around 29-30 even one card does 31mhs... Now one set of cards gets to 31mhs but with tons of errors.. so i lowered clocks. overnight each card got around 30 errors is this bad? If I clock those cards lower I get MHS lowered then before modded.. Should I try another bios on those? Also if somebody could point me to a good modded vbios repository would be awesome thanks.
For my rig I am having a couple thousand errors in a day. I have 6 Sapphire Nitro+ RX580 total hash 185 Mh for solo mining with 800Watt from wall. System never crashes up to 48 hours. I always restarted system before that time, maybe it could run even further. So i think you can overclock your card a little bit further. Use HWinfo64, overclock each card seperately and if there are no huge number of error in couple minutes you can use that values safely.
Your system does not need to crash. It can look stable. But you have no idea how much shares you've lost due tu your too overclocked gpus/mem straps. Memory errors indicates, the card is not running comfortable in 100% condition. So you could definatelly have more shares with cards without mem errors. In early days I was alsi running my cards like that and I had no clew what memory errors are. But one day I learned everything needed, optimized my cards, my cards showed lower hashrate, but my overall accepted efective hashrate increased. And that's the point.
I dont think i am losing so much shares. Because my avarage hashrate and reported hashrates are almost identical on nanopool even %1.5 devfee
I switched from Nanopool to Ethermine that X2 difficulty with shares was lowering my profits.. Even with X2 rewards ... I hate Etermines calculator though it's not accurate at all.. Dunno hash rate also seemed higher on Nanopool .. What says this forum whats better?
February 16, 2018, 12:24:00 AM
Some guys are just mean here.. I know i'm a noob on this forums but cmon we gotta help each other out.. I asked if I should mod my bios and not one person answered me. Anyways I went ahead and did it glad I did and don't know why it took me a year lol.. most cards get me around 29-30 even one card does 31mhs... Now one set of cards gets to 31mhs but with tons of errors.. so i lowered clocks. overnight each card got around 30 errors is this bad? If I clock those cards lower I get MHS lowered then before modded.. Should I try another bios on those? Also if somebody could point me to a good modded vbios repository would be awesome thanks.
For my rig I am having a couple thousand errors in a day. I have 6 Sapphire Nitro+ RX580 total hash 185 Mh for solo mining with 800Watt from wall. System never crashes up to 48 hours. I always restarted system before that time, maybe it could run even further. So i think you can overclock your card a little bit further. Use HWinfo64, overclock each card seperately and if there are no huge number of error in couple minutes you can use that values safely.
Thanks.. Why are you solo mining with 6 cards? Thought it's better to do a pool? I have 9 cards and one more on the way.. I'm I doing it wrong? Been mining for about a year now..
Oh, I meant solo for mining only eth, of course i am mining in a pool
February 16, 2018, 12:04:05 AM
Some guys are just mean here.. I know i'm a noob on this forums but cmon we gotta help each other out.. I asked if I should mod my bios and not one person answered me. Anyways I went ahead and did it glad I did and don't know why it took me a year lol.. most cards get me around 29-30 even one card does 31mhs... Now one set of cards gets to 31mhs but with tons of errors.. so i lowered clocks. overnight each card got around 30 errors is this bad? If I clock those cards lower I get MHS lowered then before modded.. Should I try another bios on those? Also if somebody could point me to a good modded vbios repository would be awesome thanks.
For my rig I am having a couple thousand errors in a day. I have 6 Sapphire Nitro+ RX580 total hash 185 Mh for solo mining with 800Watt from wall. System never crashes up to 48 hours. I always restarted system before that time, maybe it could run even further. So i think you can overclock your card a little bit further. Use HWinfo64, overclock each card seperately and if there are no huge number of error in couple minutes you can use that values safely.
Your system does not need to crash. It can look stable. But you have no idea how much shares you've lost due tu your too overclocked gpus/mem straps. Memory errors indicates, the card is not running comfortable in 100% condition. So you could definatelly have more shares with cards without mem errors. In early days I was alsi running my cards like that and I had no clew what memory errors are. But one day I learned everything needed, optimized my cards, my cards showed lower hashrate, but my overall accepted efective hashrate increased. And that's the point.
I dont think i am losing so much shares. Because my avarage hashrate and reported hashrates are almost identical on nanopool even %1.5 devfee
February 15, 2018, 09:48:02 PM
...
Now that you've explored the blockchain with these, here's how you can bypass the DevFee
...
Now that you've explored the blockchain with these, here's how you can bypass the DevFee
...
Parasite. Pay the man for his work.
I agree! Nothing wrong with paying Claymore. I do hope the fee gets reduced in the near future down to 0.5%. They kept the dual mining fee for longer than it should have been. More miners, growing industry, significantly higher gains... ultimately up to them to do the right thing.
February 15, 2018, 09:08:11 PM
Hello Miners
Can somebody please advise what I can do to resolve the following errors. My Rig is crashing once a day with these errors and I don't know how to fix the error.
14:52:26:041 1e8 parse packet: 242
14:52:26:041 1e8 ETH: job is the same
14:52:26:056 1e8 new buf size: 0
14:52:26:885 374 GPU 3, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:885 374 GPU 3, GpuMiner kx failed 1
14:52:26:900 374 Set global fail flag, failed GPU3
14:52:26:900 374 GPU 3 failed
14:52:26:900 1358 GPU 4, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:900 de4 GPU 2, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:916 de4 GPU 2, GpuMiner kx failed 1
14:52:26:916 de4 Set global fail flag, failed GPU2
14:52:26:932 de4 GPU 2 failed
14:52:26:932 1358 GPU 4, GpuMiner kx failed 1
14:52:26:932 1534 GPU 3, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:932 1534 GPU 3, GpuMiner kx failed 1
14:52:26:947 21c8 GPU 1, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:947 226c GPU 5, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:947 79c GPU 2, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:963 79c GPU 2, GpuMiner kx failed 1
14:52:26:963 d10 GPU 0, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:963 d10 GPU 0, GpuMiner kx failed 1
14:52:26:978 2160 GPU 6, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:978 2160 GPU 6, GpuMiner kx failed 1
14:52:26:978 226c GPU 5, GpuMiner kx failed 1
14:52:26:932 1358 Set global fail flag, failed GPU4
14:52:26:963 79c Set global fail flag, failed GPU2
14:52:27:010 79c GPU 2 failed
14:52:26:978 d10 Set global fail flag, failed GPU0
14:52:27:025 21c8 GPU 1, GpuMiner kx failed 1
14:52:26:978 2160 Set global fail flag, failed GPU6
14:52:27:025 2160 GPU 6 failed
14:52:27:025 1358 GPU 4 failed
14:52:27:041 e60 GPU 4, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:27:041 e60 GPU 4, GpuMiner kx failed 1
14:52:27:041 d10 GPU 0 failed
14:52:27:057 139c GPU 0, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:27:057 139c GPU 0, GpuMiner kx failed 1
14:52:26:978 226c Set global fail flag, failed GPU5
14:52:27:072 970 GPU 6, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:27:072 970 GPU 6, GpuMiner kx failed 1
14:52:27:041 e60 Set global fail flag, failed GPU4
14:52:27:072 e60 GPU 4 failed
14:52:27:057 139c Set global fail flag, failed GPU0
14:52:27:088 139c GPU 0 failed
14:52:27:088 226c GPU 5 failed
14:52:26:947 1534 Set global fail flag, failed GPU3
14:52:27:103 1534 GPU 3 failed
14:52:27:025 21c8 Set global fail flag, failed GPU1
14:52:27:103 40c GPU 5, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:27:103 40c GPU 5, GpuMiner kx failed 1
14:52:27:119 21c8 GPU 1 failed
14:52:27:119 1e84 GPU 1, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:27:119 1e84 GPU 1, GpuMiner kx failed 1
14:52:27:119 40c Set global fail flag, failed GPU5
14:52:27:135 40c GPU 5 failed
14:52:27:119 1e84 Set global fail flag, failed GPU1
14:52:27:135 1e84 GPU 1 failed
14:52:27:072 970 Set global fail flag, failed GPU6
14:52:27:150 970 GPU 6 failed
14:52:30:682 1e8 got 243 bytes
14:52:30:682 1e8 buf:
Can somebody please advise what I can do to resolve the following errors. My Rig is crashing once a day with these errors and I don't know how to fix the error.
14:52:26:041 1e8 parse packet: 242
14:52:26:041 1e8 ETH: job is the same
14:52:26:056 1e8 new buf size: 0
14:52:26:885 374 GPU 3, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:885 374 GPU 3, GpuMiner kx failed 1
14:52:26:900 374 Set global fail flag, failed GPU3
14:52:26:900 374 GPU 3 failed
14:52:26:900 1358 GPU 4, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:900 de4 GPU 2, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:916 de4 GPU 2, GpuMiner kx failed 1
14:52:26:916 de4 Set global fail flag, failed GPU2
14:52:26:932 de4 GPU 2 failed
14:52:26:932 1358 GPU 4, GpuMiner kx failed 1
14:52:26:932 1534 GPU 3, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:932 1534 GPU 3, GpuMiner kx failed 1
14:52:26:947 21c8 GPU 1, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:947 226c GPU 5, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:947 79c GPU 2, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:963 79c GPU 2, GpuMiner kx failed 1
14:52:26:963 d10 GPU 0, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:963 d10 GPU 0, GpuMiner kx failed 1
14:52:26:978 2160 GPU 6, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:26:978 2160 GPU 6, GpuMiner kx failed 1
14:52:26:978 226c GPU 5, GpuMiner kx failed 1
14:52:26:932 1358 Set global fail flag, failed GPU4
14:52:26:963 79c Set global fail flag, failed GPU2
14:52:27:010 79c GPU 2 failed
14:52:26:978 d10 Set global fail flag, failed GPU0
14:52:27:025 21c8 GPU 1, GpuMiner kx failed 1
14:52:26:978 2160 Set global fail flag, failed GPU6
14:52:27:025 2160 GPU 6 failed
14:52:27:025 1358 GPU 4 failed
14:52:27:041 e60 GPU 4, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:27:041 e60 GPU 4, GpuMiner kx failed 1
14:52:27:041 d10 GPU 0 failed
14:52:27:057 139c GPU 0, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:27:057 139c GPU 0, GpuMiner kx failed 1
14:52:26:978 226c Set global fail flag, failed GPU5
14:52:27:072 970 GPU 6, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:27:072 970 GPU 6, GpuMiner kx failed 1
14:52:27:041 e60 Set global fail flag, failed GPU4
14:52:27:072 e60 GPU 4 failed
14:52:27:057 139c Set global fail flag, failed GPU0
14:52:27:088 139c GPU 0 failed
14:52:27:088 226c GPU 5 failed
14:52:26:947 1534 Set global fail flag, failed GPU3
14:52:27:103 1534 GPU 3 failed
14:52:27:025 21c8 Set global fail flag, failed GPU1
14:52:27:103 40c GPU 5, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:27:103 40c GPU 5, GpuMiner kx failed 1
14:52:27:119 21c8 GPU 1 failed
14:52:27:119 1e84 GPU 1, GpuMiner cu_k04 failed 4, unspecified launch failure
14:52:27:119 1e84 GPU 1, GpuMiner kx failed 1
14:52:27:119 40c Set global fail flag, failed GPU5
14:52:27:135 40c GPU 5 failed
14:52:27:119 1e84 Set global fail flag, failed GPU1
14:52:27:135 1e84 GPU 1 failed
14:52:27:072 970 Set global fail flag, failed GPU6
14:52:27:150 970 GPU 6 failed
14:52:30:682 1e8 got 243 bytes
14:52:30:682 1e8 buf:
February 15, 2018, 07:52:42 PM
If you don't want to pay DevFee use some other miner. Don't cheat. Just image how you would feel if someone not pay you for your work.
I knew some of you would object to that kind of post which is why I kept it vague and technical.
For the rest of you, how about you all not 'cheat' and stop using/accumulating cryptocurrency, embrace receiving fiat for your labor, pay your taxes for the government's work? See, we could have entire arguments about morality and money which I don't care for.
February 15, 2018, 07:26:22 PM
Here are a few of the DevFee addresses found within v11:
0xB9cF2dA90Bdff1BC014720Cc84F5Ab99d7974EbA
0x3509F7bd9557F8a9b793759b3E3bfA2Cd505ae31
0xdE088812A9c5005b0dC8447B37193c9e8b67a1fF
0x7Fb21ac4Cd75d9De3E1c5D11D87bB904c01880fc
0x34FAAa028162C4d4E92DB6abfA236A8E90fF2FC3
Now that you've explored the blockchain with these, here's how you can bypass the DevFee without incurring a penalty or installing some malware if you don't think Claymore deserves this fee. It isn't for noobs, so don't ask me details if you don't understand. Pay the man and learn.
1. Don't try anything on your Windows box where Claymore runs. Claymore can detect local, 'private net' addresses (proxies), and can even detect if you 'spoof' a pool's public IP locally by examining the route or the network response times etc... Claymore will penalize you by introducing a several seconds delay between the time a share is found and the time it submitted to the pool. You'll get a decent hash rate still, but your stale shares will increase dramatically. It will also warn you about local pools.
2. Familiarize yourself with how a transparent 'Squid' HTTP proxy works on a NAT-router/gateway.
3. Set up the networking on your NAT-router/gateway similar for Squid, except you're not going to intercept port 80 HTTP traffic, but TCP traffic to port 4444. (Eg: ethermine's port)
4. Get familiar with a Unix program called 'netsed' - network stream editor. It's available only as source code, sorry noobs. Set it up to listen on the NAT-router/gateway port that you have redirected 4444 traffic to and have it send output to eu1.ethermine.org:4444 or whatever your pool is. You're going to want to have it substitute the addresses above with that of your own. Claymore will probably change these with each version, so you're on your own when that happens.
5. Set the default gateway on your miner box to the ip of the NAT-router. (Hint: virtual machines.)
6. If you've got a large farm, you might want to explore the source code of netsed, or other programs, to make your own version that can handle more connections and any future DevFee addresses Claymore might add.
7. I'm not going to help you. Don't ask.
If you don't want to pay DevFee use some other miner. Don't cheat. Just image how you would feel if someone not pay you for your work. 0xB9cF2dA90Bdff1BC014720Cc84F5Ab99d7974EbA
0x3509F7bd9557F8a9b793759b3E3bfA2Cd505ae31
0xdE088812A9c5005b0dC8447B37193c9e8b67a1fF
0x7Fb21ac4Cd75d9De3E1c5D11D87bB904c01880fc
0x34FAAa028162C4d4E92DB6abfA236A8E90fF2FC3
Now that you've explored the blockchain with these, here's how you can bypass the DevFee without incurring a penalty or installing some malware if you don't think Claymore deserves this fee. It isn't for noobs, so don't ask me details if you don't understand. Pay the man and learn.
1. Don't try anything on your Windows box where Claymore runs. Claymore can detect local, 'private net' addresses (proxies), and can even detect if you 'spoof' a pool's public IP locally by examining the route or the network response times etc... Claymore will penalize you by introducing a several seconds delay between the time a share is found and the time it submitted to the pool. You'll get a decent hash rate still, but your stale shares will increase dramatically. It will also warn you about local pools.
2. Familiarize yourself with how a transparent 'Squid' HTTP proxy works on a NAT-router/gateway.
3. Set up the networking on your NAT-router/gateway similar for Squid, except you're not going to intercept port 80 HTTP traffic, but TCP traffic to port 4444. (Eg: ethermine's port)
4. Get familiar with a Unix program called 'netsed' - network stream editor. It's available only as source code, sorry noobs. Set it up to listen on the NAT-router/gateway port that you have redirected 4444 traffic to and have it send output to eu1.ethermine.org:4444 or whatever your pool is. You're going to want to have it substitute the addresses above with that of your own. Claymore will probably change these with each version, so you're on your own when that happens.
5. Set the default gateway on your miner box to the ip of the NAT-router. (Hint: virtual machines.)
6. If you've got a large farm, you might want to explore the source code of netsed, or other programs, to make your own version that can handle more connections and any future DevFee addresses Claymore might add.
7. I'm not going to help you. Don't ask.
February 15, 2018, 07:24:05 PM
...
Now that you've explored the blockchain with these, here's how you can bypass the DevFee
...
Now that you've explored the blockchain with these, here's how you can bypass the DevFee
...
Parasite. Pay the man for his work.
February 15, 2018, 07:01:34 PM
has the dust settled on a pool for Verge yet or any other ?
Thought I would wait a few days till it got a little more stable before starting up the dual mining
Thanks
Thought I would wait a few days till it got a little more stable before starting up the dual mining
Thanks
antpool works fine for me.
that pool disconnects each my rig few times an hour
Unimining is working nice for me. They created a dedicated address to verge.
February 15, 2018, 06:44:35 PM
Here are a few of the DevFee addresses found within v11:
0xB9cF2dA90Bdff1BC014720Cc84F5Ab99d7974EbA
0x3509F7bd9557F8a9b793759b3E3bfA2Cd505ae31
0xdE088812A9c5005b0dC8447B37193c9e8b67a1fF
0x7Fb21ac4Cd75d9De3E1c5D11D87bB904c01880fc
0x34FAAa028162C4d4E92DB6abfA236A8E90fF2FC3
Now that you've explored the blockchain with these, here's how you can bypass the DevFee without incurring a penalty or installing some malware if you don't think Claymore deserves this fee. It isn't for noobs, so don't ask me details if you don't understand. Pay the man and learn.
1. Don't try anything on your Windows box where Claymore runs. Claymore can detect local, 'private net' addresses (proxies), and can even detect if you 'spoof' a pool's public IP locally by examining the route or the network response times etc... Claymore will penalize you by introducing a several seconds delay between the time a share is found and the time it submitted to the pool. You'll get a decent hash rate still, but your stale shares will increase dramatically. It will also warn you about local pools.
2. Familiarize yourself with how a transparent 'Squid' HTTP proxy works on a NAT-router/gateway.
3. Set up the networking on your NAT-router/gateway similar for Squid, except you're not going to intercept port 80 HTTP traffic, but TCP traffic to port 4444. (Eg: ethermine's port)
4. Get familiar with a Unix program called 'netsed' - network stream editor. It's available only as source code, sorry noobs. Set it up to listen on the NAT-router/gateway port that you have redirected 4444 traffic to and have it send output to eu1.ethermine.org:4444 or whatever your pool is. You're going to want to have it substitute the addresses above with that of your own. Claymore will probably change these with each version, so you're on your own when that happens.
5. Set the default gateway on your miner box to the ip of the NAT-router. (Hint: virtual machines.)
6. If you've got a large farm, you might want to explore the source code of netsed, or other programs, to make your own version that can handle more connections and any future DevFee addresses Claymore might add.
7. I'm not going to help you. Don't ask.
0xB9cF2dA90Bdff1BC014720Cc84F5Ab99d7974EbA
0x3509F7bd9557F8a9b793759b3E3bfA2Cd505ae31
0xdE088812A9c5005b0dC8447B37193c9e8b67a1fF
0x7Fb21ac4Cd75d9De3E1c5D11D87bB904c01880fc
0x34FAAa028162C4d4E92DB6abfA236A8E90fF2FC3
Now that you've explored the blockchain with these, here's how you can bypass the DevFee without incurring a penalty or installing some malware if you don't think Claymore deserves this fee. It isn't for noobs, so don't ask me details if you don't understand. Pay the man and learn.
1. Don't try anything on your Windows box where Claymore runs. Claymore can detect local, 'private net' addresses (proxies), and can even detect if you 'spoof' a pool's public IP locally by examining the route or the network response times etc... Claymore will penalize you by introducing a several seconds delay between the time a share is found and the time it submitted to the pool. You'll get a decent hash rate still, but your stale shares will increase dramatically. It will also warn you about local pools.
2. Familiarize yourself with how a transparent 'Squid' HTTP proxy works on a NAT-router/gateway.
3. Set up the networking on your NAT-router/gateway similar for Squid, except you're not going to intercept port 80 HTTP traffic, but TCP traffic to port 4444. (Eg: ethermine's port)
4. Get familiar with a Unix program called 'netsed' - network stream editor. It's available only as source code, sorry noobs. Set it up to listen on the NAT-router/gateway port that you have redirected 4444 traffic to and have it send output to eu1.ethermine.org:4444 or whatever your pool is. You're going to want to have it substitute the addresses above with that of your own. Claymore will probably change these with each version, so you're on your own when that happens.
5. Set the default gateway on your miner box to the ip of the NAT-router. (Hint: virtual machines.)
6. If you've got a large farm, you might want to explore the source code of netsed, or other programs, to make your own version that can handle more connections and any future DevFee addresses Claymore might add.
7. I'm not going to help you. Don't ask.
Jump to: