 Show Posts
|
|
Pages: [1]
|
|
Can we send multiple transactions from a single wallet that total 100ETH to limit our risk in case the smart contract has an exploit in it? Send 10ETH, wait for return of ETH and associated AUT, repeat 9 more times. Or does the smart contract hold all of the ETH until the end of the deployment which would make this approach to limiting risk impossible?
|
|
|
|
v7.0:
- improved speed by about 15-25% (depends on card model). About 230H/s on stock 390X.
- added "-benchmark" option.
Is there any chance to upgrade miner versions using remote manager? Updating 2 or 3 miners is easy, but in case of big farm it takes lots of time. I'm not complaining or something you have super speed and great miners, but this option would make it even better! Thanks! You could use the "Execute reboot.bat" option in the miner manager to do it with something like this: taskkill /f /im ZecMiner64.exe robocopy \\server\share\claymore C:\claymore /XF config.txt shutdown.exe /r /t 00 I haven't tested this but it should get you close. I'm assuming reboot.bat goes on each mining rig. Make sure each rig is logged in as a user with access to the network share. /XF config.txt skips the config file so you don't lose your worker names. It makes sense, but in that case I will have to update config files anyway. I'm thinking about active directory there are 78 host PCs already.. You don't already have working config.txt files? Robocopy would leave them there. Other option is to use a start.bat file without config.txt so you can set each worker name to %computername% That is one thing I don't like about config.txt. No option (that I know of) to use computer name as worker name since env variables don't work with it. With 76 pc's active directory and powershell would make sense though. Even having to click reboot 76 times would be annoying. |
|
|
|
v7.0:
- improved speed by about 15-25% (depends on card model). About 230H/s on stock 390X.
- added "-benchmark" option.
Is there any chance to upgrade miner versions using remote manager? Updating 2 or 3 miners is easy, but in case of big farm it takes lots of time. I'm not complaining or something you have super speed and great miners, but this option would make it even better! Thanks! You could use the "Execute reboot.bat" option in the miner manager to do it with something like this: taskkill /f /im ZecMiner64.exe robocopy \\server\share\claymore C:\claymore /XF config.txt shutdown.exe /r /t 00 I haven't tested this but it should get you close. I'm assuming reboot.bat goes on each mining rig. Make sure each rig is logged in as a user with access to the network share. /XF config.txt skips the config file so you don't lose your worker names. |
|
|
|
I just uploaded a new version of my Windows build of SILENTARMY v5: https://mega.nz/#F!iwYQhI6S!2vl0D3jz3fH3-bZxHUurBg This *should* work with NVIDIA cards. If it doesn't, please let me know with as much information as possible. R2 made my old gtx 680 work. Was already working great on my rx 470s. Does R2 fix anything other than nvidia support? In other words, any point updating my amd rigs? |
|
|
|
|
Silent Army 5 is beating claymore now. 80 sol/s on rx 470 4gb and low CPU/PCI-E bus usage. Hope Claymore v5 comes out soon because I like his mgmt features.
|
|
|
|
is there any possibility to upgrade miner versions on all rigs at once ?
it would be damn helpful because I have to spend 3+ hrs a day to keep up with updates
I'm not complaining, I'm glad that speed is growing and growing
There are many ways to keep your Rigs up to date: special Software that can handle scripted SW Updates, full API Access miners through eg. Awesome Miner, write your own scripts when the files are on same place on all rigs, ..... Isnīt it a fulltime Job to manage (update, cleaning, repairing) so many rigs ? 147 x RX480 a 70 SOLs = 10290 SOLs 31KW @ 20 Cent/KWh thats means round about 10.ooo Dollar p.M. income ^^ there's a catch, I have only own % from this farm + maintaining fee, but awesome miner makes sense and does really good job, I'll think about it It would be really easy to add a section to your startup.bat file that would check a network share for new files every time you reboot. Then it could copy that over to the machine before launching claymore. Just leave config.txt off of the network share so you don't overwrite your worker names. Then write a powershell script to reboot your machines one at a time with a short timeout between each system to avoid too much inrush or overloading your network share. |
|
|
|
Any advice on which port to use for 330 sol/s rigs?
PORT (VARDIFF): 7007
HIGH DIFF PORT (VARDIFF): 7077
STATIC PORT (DIFF20): 8008
STATIC PORT (DIFF500): 8088
HIGH DIFF PORT (VARDIFF): 7077 - the best in my opinion  Reason I like to use a vardiff port is to try and get a share within a few seconds. I prefer to have my rig run about double to triple diff to hash. So if I have a 100 sol/s rig my diff would be around 200-300. That way when I have a block change and shares are rejected I don't loose as much work. I'd rather a 300 diff share be rejected vs 6400. That is my reasoning. To each their own. It really boils down to how your rig performs on each port. Everyone will have different results if only perspective. BR I tried port 7007 and after a little while the dashboard showed that my worker was adjusted from 500H all the way up to 6000H. I then tried port 7077 and it very quickly adjusted my worker back down down to 6000H from 6400H. I guess it doesn't make much difference but it looks like port 7077 gets my worker where the pool wants it faster. If you really want a lower difficulty then you would need to use one of the static ports (8088). Yes your not giving it enough time. It freaks out a bit a first since you bombard it with shares on 7007. Then after adjusting high as heck it will start to correct down. Give it about an hour and it will be settled in. Again it's what works best for you. BR Thanks, will let each one run for a few hours to see where they stabilize and then pick one. Maybe they need a third vardiff port that starts at ~2000 |
|
|
|
Any advice on which port to use for 330 sol/s rigs?
PORT (VARDIFF): 7007
HIGH DIFF PORT (VARDIFF): 7077
STATIC PORT (DIFF20): 8008
STATIC PORT (DIFF500): 8088
HIGH DIFF PORT (VARDIFF): 7077 - the best in my opinion Reason I like to use a vardiff port is to try and get a share within a few seconds. I prefer to have my rig run about double to triple diff to hash. So if I have a 100 sol/s rig my diff would be around 200-300. That way when I have a block change and shares are rejected I don't loose as much work. I'd rather a 300 diff share be rejected vs 6400. That is my reasoning. To each their own. It really boils down to how your rig performs on each port. Everyone will have different results if only perspective. BR I tried port 7007 and after a little while the dashboard showed that my worker was adjusted from 500H all the way up to 6000H. I then tried port 7077 and it very quickly adjusted my worker back down down to 6000H from 6400H. I guess it doesn't make much difference but it looks like port 7077 gets my worker where the pool wants it faster. If you really want a lower difficulty then you would need to use one of the static ports (8088). |
|
|
|
To those mining on flypool. MOVE immediately. I was getting 30% less than Calcs on fly. Moved to coinmine.pl and haven't looked back. Making very close to calcs now. Test it for yourselves.
Rednow. That and the fact that now that we are surpassing their speeds they are losing their cool. Cause well they have investors breathing down their neck. Hope that was lesson to those that buy/sell cloud contracts before price and hashrate settle in. 50 BTC for 500s/s. Wow my 390x rig does that alone. A fool and his money! Really does give crypto a bad wrap.
BR
d57heinz
Any advice on which port to use for 330 sol/s rigs? PORT (VARDIFF): 7007 HIGH DIFF PORT (VARDIFF): 7077 STATIC PORT (DIFF20): 8008 STATIC PORT (DIFF500): 8088 |
|
|
|
HW:
- 6x Reference Sapphire RX 470 OC 4GB (5x Elpida memory/1x Hynix memory)
- Gigabyte GA-Z97X-Gaming 3, Rev 1.0, Bios F8d (disabled USB3, lan, serial, audio, virtualization, and on chip vga)
- G1840 CPU
- 4G DDR3 1600MHz Single Channel
- 120GB Micron m600 m.2 Sata SSD
- RT73 USB wireless-n
- PSU: 1200W Corsair AX1200i
- 6x powered USB risers v006
SW:
- Win10 Pro 64-bit version 1607 (anniversary edition) fully updated, stripped out a little bloatware
- Crimson 16.10.3
- Claymore v 3.1 (-i 2 -dbg -1 -colors 0)
Results:
- Reported Hashrate: 335 sol/s (56 sol/s per card)
- Power: 610W
BIOS Settings
- GPU 1100 @ 900mV
- Mem 1900 @ 900mv with timings from 1500MHz
- Fan 3800RPM / 60%
Stable for a few hours with 47C card temps. Will retry with an i5 4690k and 8gb 2133 mhz ram tomorrow. Also tempted to try 16.11.x drivers.
How did you edit bios for elipda cards? It doesnt work in PolarisBiosEditor, right? PolarisBiosEditor worked fine for me with both memory types. Maybe it was a different card that other people were having problems with Elpida on. If you have one of those cards there is a thread on the ethereum community forum on how to edit it with a hex editor. |
|
|
|
|
HW:
- 6x Reference Sapphire RX 470 OC 4GB (5x Elpida memory/1x Hynix memory)
- Gigabyte GA-Z97X-Gaming 3, Rev 1.0, Bios F8d (disabled USB3, lan, serial, audio, virtualization, and on chip vga)
- G1840 CPU
- 4G DDR3 1600MHz Single Channel
- 120GB Micron m600 m.2 Sata SSD
- RT73 USB wireless-n
- PSU: 1200W Corsair AX1200i
- 6x powered USB risers v006
SW:
- Win10 Pro 64-bit version 1607 (anniversary edition) fully updated, stripped out a little bloatware
- Crimson 16.10.3
- Claymore v 3.1 (-i 2 -dbg -1 -colors 0)
Results:
- Reported Hashrate: 335 sol/s (56 sol/s per card)
- Power: 610W
BIOS Settings
- GPU 1100 @ 900mV
- Mem 1900 @ 900mv with timings from 1500MHz
- Fan 3800RPM / 60%
Stable for a few hours with 47C card temps. Will retry with an i5 4690k and 8gb 2133 mhz ram tomorrow. Also tempted to try 16.11.x drivers.
|
|
|
|
|
