 Show Posts
|
|
Pages: [1] 2 3 4 »
|
The first release of the MinerPro for Nicehash is published. Very interested in your opinion about the application. https://github.com/EvgeniyKorepov/MinerPro-for-NiceHashShort demo video https://youtu.be/zN5rWmuU2mcYou must download and run the Excavator yourself on your farms. The application does not start the excavator, it controls local or remote instances of the miner. Features - The calculation of profits is made taking into account the cost of electricity. Including different cost of electricity during the day.
- Individual overclocking GPUs for each algorithm.
- Fine-tuning the parameters of algorithms.
- Ability to change parameters of the overclocking during operation.
- Fast, less than one second, switch between algorithms.
- Failover - switching to other locations when the stratum server fails.
- Dev fee 0.8% (one minute in two hours).
 |
|
|
|
Hi there,
I'd like to create a docker image to give excavator a try. I saw the huge disclamer saying it's not allowed to redistribute. What a pity...
Would you consider changing your mind ? Otherwise I'll only publish the Dockerfile and people will have to build the image themself which is quite unefficient...
Regards, Adam.
Sorry, we're not changing our EULA. If I create an application of the analogue of NHM and will distribute it (but the users will have to install the Excavator themselves) - this will not violate EULA? |
|
|
|
|
Dear administration, make API for the pool. Thank you in advance!
|
|
|
|
For miningpoolhub pools - resolve domain name to IP, and insert to Excavator json config - Profit!
I suspect it's more than that - as that would be a pretty trivial bypass. I wouldn't be surprised of some part of the Stratum protocol probably includes some host field and that's what it's working off of. You may suspect that, but did you try it? You might be surprised. yes i was try replace named adress with IP & yes it wroking BUT is more about trivial bypass, coz invalid share it will be many  aka let give you a expample > Your Invalid: 676.0354 (26.58%) for equihash algo on one rownd, it was not a problem if was 1-2% but 25% to much. I any other pool invalid share are 0 or max 1% soo my conclusion is yes is more that trivial bypass special if i run other miner like dstm 0% bad share or EWBF anyway for me is clear excavator & miningpoolhub not work togheter = https://github.com/nicehash/excavator/issues/51On https://monacoin.miningpoolhub.com : Your Valid 179.3412 Your Invalid 2.7619 (1.52%) |
|
|
|
For miningpoolhub pools - resolve domain name to IP, and insert to Excavator json config - Profit!
I suspect it's more than that - as that would be a pretty trivial bypass. I wouldn't be surprised of some part of the Stratum protocol probably includes some host field and that's what it's working off of. Excavator (3 rigs) works on the pool https://monacoin.miningpoolhub.com for a week without problems. instead {"id":1,"method":"algorithm.add","params":["lyra2rev2","hub.miningpoolhub.com:20593","***********"]} use {"id":1,"method":"algorithm.add","params":["lyra2rev2","52.6.227.167:20593","***********"]} |
|
|
|
|
For miningpoolhub pools - resolve domain name to IP, and insert to Excavator json config - Profit!
|
|
|
|
Hi All, How do I make excavator work with p2pool, or what I need to change in the pool to make excavator to work> CC Miner works fine but has slightly lower hash rate. I'm getting "error" not expected type: Array [23:20:00][0x00004010][info] Log started [23:20:00][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti [23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti [23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti [23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti [23:20:02][0x00004010][info] core | Initialized! [23:20:02][0x00003948][info] net | Connecting to 127.0.0.1:9171 (127.0.0.1) [23:20:02][0x00002078][info] net | Connected! [23:20:02][0x00003948][warning] net | Net error: JSON member "error" not expected type: Array [23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error" [23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error" [23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error" [23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error" Thanks!  Here are the specifications of the protocol stratum, the pool should support them https://github.com/nicehash/Specifications |
|
|
|
Dear Zawawa, is it planned to add new algorithms to the Excavator?
Good question - now I need ethash algorithm too, but on AMD and Ubuntu 14.04 LTS Dear Zawawa, help us!  EXCAVATOR DOES ETH-HASH (DAGGER-HASHIMOTO)-- You may read on pages 48-50 or so for example configurations. Excavator dual-mines with no fee. Detailed configuration docs are on the GitHub site. --scryptr I saw 48-50 pages before and config dual-mining for ZEC and XMR. But I didn't know what algorithm is for ETH in Excavator miner. Thnx! Now I can't config web stats for Excavator on Ubuntu 16.04 LTS. Where can I put the "index.html" file to get stats on web? I start excavator with -wp and -wi parameters (not local IP bind) and get on web "404 Not Found", but when I do "api?..." to binded IP and port I can get stats in JSON format. Thnx! Лекс, спроси вот тут https://github.com/nicehash/excavator/issues/60 , сам не знаю, на линуксе не запускал. Ask here https://github.com/nicehash/excavator/issues/60, I do not know, I did not run it on Linux. |
|
|
|
Anyone
I am trying to implement the "device.list" command in my config file but failing.
I have already read the Readme and Master documents. It is not clear to me how this command is implemented.
I added the following to my config file and caused the system to freeze.
{"id":1,"method":"device.list","params":[]}
I am currently mining ZEC on Excavator. I have 5x GTX1080TI GPUS on my rig. It works fine until I add the "device.list" and then it crashes.
Has any of you used this function when running excavator? If yes can you show your config entries related to "device.list" functionality.
I ran the telnet call for the device info. I entered the device results into a text file.
Can anyone show how the "device.list" command works in the config file and where does the results of this command show up?
Best regards
device.list works only via API. In the configuration file it does not work. Via Telnet - only type on keyboard {"id":1,"method":"device.list","params":[]} and press Enter. With the HTTP - http://Excavator_IP:Excavator_Port/api?command={"id":1,"method":"algorithm.list","params":[]} For example: Linux: wget --quiet -O - http://10.0.0.9:38080/api?command={"id":1,"method":"algorithm.list","params":[]} Windows: use PowerShell (.Net) or wget for windows or browser |
|
|
|
Hello all
i try to switch from ETH Mining to Zcash Mining but have problem with the OC
i have some GTX 1070's
running on ewbf-0.3.4b / simple mining / linux
i put OC
Core Empty, Memory +500, Power limit : 120 watt
i get 420 Sol/s but my GTX 1070's are getting very very hot about 80 C
i am lost
does somebody have an OC stable with GTX 1070's under 70 C ?
thank you all for your help sincerely.
tdp 77, core_delta 120, memory_delta 680 :  Miner - Excavator |
|
|
|
|
Dear Zawawa, is it planned to add new algorithms to the Excavator?
|
|
|
|
Version 1.3.6 alpha NVIDIA - API is broken?
In web interface:
"equihash | FAIL | undefined | 607.460 H/s | 0.000 H/J"
This is fixed. Wrong web file was attached. Please re-download the archive. Yes, web is fine, thank you! |
|
|
|
|
Version 1.3.6 alpha NVIDIA - API is broken?
In web interface:
"equihash | FAIL | undefined | 607.460 H/s | 0.000 H/J"
|
|
|
|
Thanks for the new version Version 1.3.5 alpha NVIDIA !
On 1.3.4 - frost the screen at five 1070? on 1.3.5 - fixed!
CryptoNight GTX 1070 - 660.0 !!!
CryptoNight GTX 1080Ti - 800.0 !
CryptoNight GTX 1080 - 530.0 :-( Still low speed. Apparently the video memory is to blame?
What is expected with CryptoNight GTX 1060 3GB? Also what settings? 1 worker per card with default settings (no paremeters) don't give good performance in exevator... Thanks in advance! {"id":1,"method":"worker.add","params":["0","0","30","32"]} It is not difficult to adjust, the second parameter is always 32, select the first parameter within 10-30 |
|
|
|
|
