Latest posts of: ndimario

Show Posts
Pages: [1]

Alternate cryptocurrencies / Mining (Altcoins) / Re: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows)

on: June 15, 2019, 09:32:37 PM

Just started running this software now to see if I can get it to work. It seems to have the same issue as EWBFs miner. Every share seem to be getting rejected. I cannot find any help on this subject.

Specs:
Running a ryzen 1600 with a gtx 1080 on Windows 10 64-bit and nothing is overclocked.

[ZM.CFG]:

Code:

intensity=0:0.9
temp-target=0:65

[POOL]
server=mine-btcz-na.equipool.1ds.us
port=50063
user=address.gtx1080
pass=minpayout=500

[OUTPUT]:

Code:

2019-06-15 5:16:55 PM|#  zm 0.6.2
2019-06-15 5:16:55 PM|#  GPU0 + GeForce GTX 1080         MB: 8192  PCI: 9:0
2019-06-15 5:16:55 PM|
2019-06-15 5:16:55 PM|#  using configuration file zm.cfg
2019-06-15 5:16:55 PM|#  pool1 mine-btcz-na.equipool.1ds.us:50063
2019-06-15 5:16:55 PM|
2019-06-15 5:16:55 PM|#  GPU0 temperature target 65C
2019-06-15 5:16:55 PM|#  GPU0 intensity 0.9000
2019-06-15 5:16:55 PM|
2019-06-15 5:16:55 PM|#  telemetry server listening on 0.0.0.0:2222
2019-06-15 5:16:56 PM|#  connected to: mine-btcz-na.equipool.1ds.us:50063 [1/1]
2019-06-15 5:16:57 PM|#  server set difficulty to: 0.24999952 [0020000000000000000000000000000...]
2019-06-15 5:16:58 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:02 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:07 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:07 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:07 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:07 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:08 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:13 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:18 PM|>  GPU0  55C  44% |  553.8 Sol/s   553.8 Avg   295.0 I/s | 3.08 S/W  174 W | 23.92   0.0 . ++++++++
2019-06-15 5:17:27 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:34 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:38 PM|   GPU0  60C  49% |  520.4 Sol/s   537.1 Avg   278.6 I/s | 3.02 S/W  179 W | 14.95   0.0 . ++
2019-06-15 5:17:44 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:50 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:51 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:52 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:55 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:55 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:56 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:58 PM|>  GPU0  63C  52% |  451.3 Sol/s   508.5 Avg   241.0 I/s | 2.88 S/W  175 W | 16.95   0.0 . +++++++
2019-06-15 5:17:59 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:00 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:08 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:12 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:16 PM|#  GPU0  reached temperature target 65C
2019-06-15 5:18:16 PM|#  GPU0  enabling temperature controller
2019-06-15 5:18:18 PM|   GPU0  65C! 53% |  449.8 Sol/s   493.8 Avg   244.1 I/s | 2.81 S/W  179 W | 15.70   0.0 . ++++
2019-06-15 5:18:22 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:24 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:35 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:36 PM|#  server set difficulty to: 0.83606398 [00099191924ae864000000000000000...]
2019-06-15 5:18:38 PM|>  GPU0  65C! 55% |  476.9 Sol/s   490.4 Avg   252.1 I/s | 2.80 S/W  145 W | 14.36   0.0 . +++
2019-06-15 5:18:43 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:58 PM|   GPU0  65C! 55% |  353.0 Sol/s   467.5 Avg   188.6 I/s | 2.74 S/W  144 W | 12.46   0.0 . +
2019-06-15 5:19:18 PM|   GPU0  65C! 55% |  334.0 Sol/s   448.5 Avg   176.7 I/s | 2.70 S/W  148 W | 10.68   0.0 .
2019-06-15 5:19:21 PM|#  GPU0  rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]

Note: Nevermind just found out that at some point BTCZ started using an algorithm that DSTM doesn't support, so rip.

Alternate cryptocurrencies / Mining (Altcoins) / Re: EWBF's Cuda Equihash Miner 0.6

on: June 15, 2019, 07:32:50 PM

I'm currently trying to get the 0.6 Equihash cuda miner software to work using the 210_9 algorithm. It claims to produce over 200sol/sec on a gtx 1080. I'm giving this a shot but so far all the shares are being rejected without any red text or warnings (aside from the rejected shares).

Originally I used the EquiMiner.exe and it defaulted to algorithm 144 and produced 35-45sol/sec. My gtx 1080 is not overclocked or tweaked, it's running stock and is capable of mining without problems 24/7 (as I have been doing now with the GUI software at a much lower sol/sec rate.

bat file:

Code:

miner  --algo 210_9 --pers BitcoinZ --server mine-btcz-na.equipool.1ds.us --port 50063 --user address_here.gtx1080 --pass minpayout=400

output:

Code:

+-------------------------------------------------+
|         EWBF's Eqihash CUDA miner. v0.6         |
+-------------------------------------------------+
15:33:26 INFO: Configured pools: 1
15:33:26 INFO: Selected pool: mine-btcz-na.equipool.1ds.us:50063
15:33:26 INFO: Algorithm: 210_9 "BitcoinZ"
15:33:26 INFO: Devices: All.
15:33:26 INFO: Temperature limit: 90
15:33:26 INFO: Api: Disabled
---------------------------------------------------
15:33:26 INFO: Target: 0020000000000000...
15:33:26 INFO: Detected new work: f72e
15:33:26 CUDA: Device: 0 GeForce GTX 1080, 8192 MB i:64
15:33:32 INFO: GPU0 Rejected share 45ms [A:0, R:1]
15:33:38 INFO: GPU0 Rejected share 43ms [A:0, R:2]
15:33:51 INFO: GPU0 Rejected share 50ms [A:0, R:3]
15:33:56 Temp: GPU0: 62C
15:33:56 GPU0: 226 Sol/s
15:33:56 Total speed: 226 Sol/s
15:34:03 INFO: GPU0 Rejected share 91ms [A:0, R:4]
15:34:05 INFO: GPU0 Rejected share 51ms [A:0, R:5]
15:34:07 INFO: Detected new work: f72f
15:34:26 Temp: GPU0: 67C
15:34:26 GPU0: 216 Sol/s
15:34:26 Total speed: 216 Sol/s
15:34:29 INFO: GPU0 Rejected share 51ms [A:0, R:6]
15:34:43 INFO: GPU0 Rejected share 160ms [A:0, R:7]
15:34:44 INFO: GPU0 Rejected share 42ms [A:0, R:8]

Anyone have any ideas on why all the shares are being rejected?

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][JPC]MAKE JACKPOTCOIN GREAT AGAIN!

on: May 31, 2017, 12:53:03 AM

I've been trying to sync the wallet fully. Started with client 1.6.0 and it crashed repeatedly. Decided to give 1.4.1 a shot (due to a recommendation in one of the internets random forums) and it seems to be far more stable. However when the progress bar went away, there has been about 21 hours left to sync and it's taking literally 21 hours. I'm currently down to 9 hours however since the progress bar went away, the status bar has read "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers" I've not been able to find any help for this and I'm just letting the wallet sync. Hoping that it will somehow sort itself out if it ever reaches completion.

Pages: [1]