Search content
Sort by

Showing 20 of 26 results by monote
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] BitBean is Now Bean Cash | First v3 POS | First 20MB Max Blocks | 7+ Yrs.
by
monote
on 17/09/2022, 20:23:38 UTC
We are all here Cheesy
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] [BYTC] BYTECHCOIN | LAUNCHED | NO ICO | NO PREMINE |
by
monote
on 27/04/2019, 19:32:16 UTC
And now? Anything new or coming?? Cheesy
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] [KSN] KOSON - NO ICO | NO Airdrop | CryptoNight | POW | ASIC Resistant
by
monote
on 16/01/2019, 17:05:46 UTC
Is this project dead??
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 02/11/2018, 18:32:30 UTC
guys! i recently got a rx550, 2gb. Any idea if i can get more than 300h/s on cn-heavy? Cheesy
No, 2Gb too small amount to have normal speed on cn-heavy. You can increase speed only by use overclocking and editing memory straps in bios.

Yeah! I know, i have the bios modded and tried some different configurations of OC without luck...
Maybe someone had good ones Wink
Thanks man!
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 01/11/2018, 16:01:25 UTC
guys! i recently got a rx550, 2gb. Any idea if i can get more than 300h/s on cn-heavy? Cheesy
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 09/10/2018, 13:12:37 UTC
Hey hey hey! Maybe it was asked before (at least i couldn't find it).
Any plan of adding webchain to the list of supported coins? Cheesy

Cheers!
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 07/09/2018, 13:12:19 UTC
Finally get it working!!!!!! Cheesy

Before I was modifying the start.bat in the wallet section putting address.diff
apparently the WALLET = blabla doesn't take the .diff...
So running the thingy from command line it worked perfectly or adding the .diff
at the end of the bat file like %WALLET%.diff!

Thanks guys!
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 07/09/2018, 12:52:25 UTC
Okay man! Thanks for your feedback. I've tried 25k and 50k without no luck...it goes up to 350k super fast...
I'll try with higher values of diff to see if something changes!

The usual minimum value is about 5000.
25000 isn't a low difficulty so it should have been accepted by the pool.

But didn't you write it like this: wallet.25K instead of wallet.25000 ?
Only numbers (with numerical characters) are accepted.

I'm getting shares accepted by the pool, problem is that diff keeps increasing.
And of course I write 25000, i put here 25k cause i'm lazy :p

I'll try right now! Cheesy
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 07/09/2018, 12:04:57 UTC
I know! This pool does support it.
I'm here:
https://bxc.mine2gether.com

I'm giving it a try. I've only mined for ~15 minutes so far with a CPU and one GPU but the fixed diff works fine to me.

Perhaps the diff you typed was ignored because the value is too low.

My actual successful test is with 60000 with this command line:

jce_cn_gpu_miner64.exe -c configCN_6C.txt -o ctl.pool.mine2gether.com:4444 -u cxorzSavc8QRe6ryCXZ7dZPzjEQG7VFRkEuTdzYc9HLFZ11J8G7MzRMgjDvKppu13s2vPcECs2fRu5o RJ8GVjPrG12xBUyVY7.60000 -p PC40 --variation 3

And here is the result's log:
Code:
Analyzing Processors topology...
AMD Ryzen 7 1700 Eight-Core Processor
Assembly codename: ryzen
  SSE2          : Yes
  SSE3          : Yes
  SSE4          : Yes
  AES           : Yes
  AVX           : Yes
  AVX2          : Yes
Found CPU 0, with:
  L1 Cache:    32 KB, shared with CPU 1
  L2 Cache:   512 KB, shared with CPU 1
  L3 Cache:  8192 KB, shared with CPU 1, 2, 3, 4, 5, 6, 7
Found CPU 1, with:
  L1 Cache:    32 KB, shared with CPU 0
  L2 Cache:   512 KB, shared with CPU 0
  L3 Cache:  8192 KB, shared with CPU 0, 2, 3, 4, 5, 6, 7
Found CPU 2, with:
  L1 Cache:    32 KB, shared with CPU 3
  L2 Cache:   512 KB, shared with CPU 3
  L3 Cache:  8192 KB, shared with CPU 0, 1, 3, 4, 5, 6, 7
Found CPU 3, with:
  L1 Cache:    32 KB, shared with CPU 2
  L2 Cache:   512 KB, shared with CPU 2
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 4, 5, 6, 7
Found CPU 4, with:
  L1 Cache:    32 KB, shared with CPU 5
  L2 Cache:   512 KB, shared with CPU 5
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 3, 5, 6, 7
Found CPU 5, with:
  L1 Cache:    32 KB, shared with CPU 4
  L2 Cache:   512 KB, shared with CPU 4
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 3, 4, 6, 7
Found CPU 6, with:
  L1 Cache:    32 KB, shared with CPU 7
  L2 Cache:   512 KB, shared with CPU 7
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 3, 4, 5, 7
Found CPU 7, with:
  L1 Cache:    32 KB, shared with CPU 6
  L2 Cache:   512 KB, shared with CPU 6
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 3, 4, 5, 6
Found CPU 8, with:
  L1 Cache:    32 KB, shared with CPU 9
  L2 Cache:   512 KB, shared with CPU 9
  L3 Cache:  8192 KB, shared with CPU 9, 10, 11, 12, 13, 14, 15
Found CPU 9, with:
  L1 Cache:    32 KB, shared with CPU 8
  L2 Cache:   512 KB, shared with CPU 8
  L3 Cache:  8192 KB, shared with CPU 8, 10, 11, 12, 13, 14, 15
Found CPU 10, with:
  L1 Cache:    32 KB, shared with CPU 11
  L2 Cache:   512 KB, shared with CPU 11
  L3 Cache:  8192 KB, shared with CPU 8, 9, 11, 12, 13, 14, 15
Found CPU 11, with:
  L1 Cache:    32 KB, shared with CPU 10
  L2 Cache:   512 KB, shared with CPU 10
  L3 Cache:  8192 KB, shared with CPU 8, 9, 10, 12, 13, 14, 15
Found CPU 12, with:
  L1 Cache:    32 KB, shared with CPU 13
  L2 Cache:   512 KB, shared with CPU 13
  L3 Cache:  8192 KB, shared with CPU 8, 9, 10, 11, 13, 14, 15
Found CPU 13, with:
  L1 Cache:    32 KB, shared with CPU 12
  L2 Cache:   512 KB, shared with CPU 12
  L3 Cache:  8192 KB, shared with CPU 8, 9, 10, 11, 12, 14, 15
Found CPU 14, with:
  L1 Cache:    32 KB, shared with CPU 15
  L2 Cache:   512 KB, shared with CPU 15
  L3 Cache:  8192 KB, shared with CPU 8, 9, 10, 11, 12, 13, 15
Found CPU 15, with:
  L1 Cache:    32 KB, shared with CPU 14
  L2 Cache:   512 KB, shared with CPU 14
  L3 Cache:  8192 KB, shared with CPU 8, 9, 10, 11, 12, 13, 14
Detecting OpenCL-capable GPUs...
Found GPU 0, with:
  Vendor:                         AMD
  Processor:                Ellesmere
  Device:                       0b:00
  Compute-Units:                   32
  Cache Memory:                 16 KB
  Local Memory:                 32 KB
  Global Memory:              8192 MB
  Addressing:                 64-bits
Found GPU 1, with:
  Vendor:                         AMD
  Processor:                Ellesmere
  Device:                       09:00
  Compute-Units:                   32
  Cache Memory:                 16 KB
  Local Memory:                 32 KB
  Global Memory:              4096 MB
  Addressing:                 64-bits
Found GPU 2, with:
  Vendor:                         AMD
  Processor:                Ellesmere
  Device:                       0a:00
  Compute-Units:                   36
  Cache Memory:                 16 KB
  Local Memory:                 32 KB
  Global Memory:              4096 MB
  Addressing:                 64-bits
HTTP Local Server on port 15263

Preparing 10 Mining Threads...

+-- Thread 0 config -----------------------+
| Run on CPU:             1                |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        ryzen            |
+------------------------------------------+

+-- Thread 1 config -----------------------+
| Run on CPU:             3                |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        ryzen            |
+------------------------------------------+

+-- Thread 2 config -----------------------+
| Run on CPU:             5                |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        ryzen            |
+------------------------------------------+

+-- Thread 3 config -----------------------+
| Run on CPU:             7                |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        ryzen            |
+------------------------------------------+

+-- Thread 4 config -----------------------+
| Run on CPU:             9                |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        ryzen            |
+------------------------------------------+

+-- Thread 5 config -----------------------+
| Run on CPU:             11               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        ryzen            |
+------------------------------------------+

+-- Thread 6 config -----------------------+
| Run on CPU:             13               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        ryzen            |
+------------------------------------------+

+-- Thread 7 config -----------------------+
| Run on CPU:             15               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        ryzen            |
+------------------------------------------+

+-- Thread 8 config -----------------------+
| Run on GPU:                      1       |
| Multi-hash:                    976       |
| Worksize:                        8       |
| Factor Alpha                    64       |
| Factor Beta                      8       |
+------------------------------------------+

+-- Thread 9 config -----------------------+
| Run on GPU:                      1       |
| Multi-hash:                    976       |
| Worksize:                        8       |
| Factor Alpha                    64       |
| Factor Beta                      8       |
+------------------------------------------+

Cryptonight Variation: Cryptonight V7 fork of April-2018

Low intensity.

Starting CPU Mining thread 0, affinity: CPU 1
Thread 0 successfully bound to CPU 1
Allocated shared Large Page at: 0000017baa600000
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 1 of NUMA node 0 at: 0000017baa800000

Starting CPU Mining thread 1, affinity: CPU 3
Thread 1 successfully bound to CPU 3
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 3 of NUMA node 0 at: 0000017baaa00000

Starting CPU Mining thread 2, affinity: CPU 5
Thread 2 successfully bound to CPU 5
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 5 of NUMA node 0 at: 0000017baac00000

Starting CPU Mining thread 3, affinity: CPU 7
Thread 3 successfully bound to CPU 7
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 7 of NUMA node 0 at: 0000017baae00000

Starting CPU Mining thread 4, affinity: CPU 9
Thread 4 successfully bound to CPU 9
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 9 of NUMA node 0 at: 0000017bab000000

Starting CPU Mining thread 5, affinity: CPU 11
Thread 5 successfully bound to CPU 11
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 11 of NUMA node 0 at: 0000017bab200000

Starting CPU Mining thread 6, affinity: CPU 13
Thread 6 successfully bound to CPU 13
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 13 of NUMA node 0 at: 0000017bab400000

Starting CPU Mining thread 7, affinity: CPU 15
Thread 7 successfully bound to CPU 15
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 15 of NUMA node 0 at: 0000017bab600000

Starting GPU Mining thread 8, on GPU 1
Created OpenCL Context for GPU 1 at 0000017baa037710
Created OpenCL Thread 8 Command-Queue for GPU 1 at 0000017baa05ce70
Scratchpad Allocation success for OpenCL Thread 8
Allocating big 1952MB scratchpad for OpenCL Thread 8...
Compiling kernels of OpenCL Thread 8...
Kernels of OpenCL Thread 8 compiled.

Starting GPU Mining thread 9, on GPU 1
Created OpenCL Thread 9 Command-Queue for GPU 1 at 0000017baa05c930
Scratchpad Allocation success for OpenCL Thread 9
Allocating big 1952MB scratchpad for OpenCL Thread 9...
Compiling kernels of OpenCL Thread 9...
Kernels of OpenCL Thread 9 compiled.
Connecting to mining pool ctl.pool.mine2gether.com:4444 ...
12:34:33 | Bitcedi (BXC) Mining session starts!

12:34:33 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
12:34:33 | during this time, the hashrate may be unstable and inconsistent.
12:34:33 | Let the miner warm-up if you're tuning for performance.
12:34:33 | Connected to pool. Now logging in...
12:34:33 | Successfuly logged as cxorzSavc8QRe6ryCXZ7dZPzjEQG7VFRkEuTdzYc9HLFZ11J8G7MzRMgjDvKppu13s2vPcECs2fRu5oRJ8GVjPrG12xBUyVY7.60000
12:34:33 | Pool changes Difficulty to 60000.
12:35:04 | Hashrate CPU Thread 0: 75.35 h/s
12:35:04 | Hashrate CPU Thread 1: 74.32 h/s
12:35:04 | Hashrate CPU Thread 2: 51.89 h/s
12:35:04 | Hashrate CPU Thread 3: 75.86 h/s
12:35:04 | Hashrate CPU Thread 4: 83.29 h/s
12:35:04 | Hashrate CPU Thread 5: 83.12 h/s
12:35:04 | Hashrate CPU Thread 6: 83.49 h/s
12:35:04 | Hashrate CPU Thread 7: 83.35 h/s - Total CPUs: 610.62 h/s
12:35:04 | Hashrate GPU Thread 8: 520.64 h/s
12:35:04 | Hashrate GPU Thread 9: 515.19 h/s - Total GPU 1: 1035.82 h/s
12:35:04 | Total: 1646.44 h/s - Max: 1646.44 h/s
12:35:08 | GPU 1 Thread 8 Lane 939 finds a Share, value 60000
12:35:08 | Accepted by the pool in 75 ms.
12:35:12 | GPU 1: Temp: 48C - Fan:  0% -- Shares: Good: 1 Bad: 0
12:35:13 | GPU 1 Thread 9 Lane 303 finds a Share, value 60000
12:35:13 | Accepted by the pool in 71 ms.
12:35:20 | CPU Thread 6 finds a Share, value 60000
12:35:20 | Accepted by the pool in 77 ms.
12:35:22 | GPU 1 Thread 8 Lane 354 finds a Share, value 60000
12:35:22 | Accepted by the pool in 74 ms.
12:35:36 | Pool sends a new Job.
12:36:09 | GPU 1 Thread 8 Lane 329 finds a Share, value 60000
12:36:09 | Accepted by the pool in 75 ms.
12:36:14 | CPU Thread 2 finds a Share, value 60000
12:36:14 | Accepted by the pool in 76 ms.
12:36:48 | GPU 1 Thread 8 Lane 809 finds a Share, value 60000
12:36:48 | Accepted by the pool in 82 ms.
12:36:57 | CPU Thread 7 finds a Share, value 60000
12:36:57 | Accepted by the pool in 98 ms.
12:37:10 | GPU 1 Thread 9 Lane 518 finds a Share, value 60000
12:37:10 | Accepted by the pool in 72 ms.
12:38:28 | GPU 1 Thread 9 Lane 186 finds a Share, value 60000
12:38:28 | Accepted by the pool in 84 ms.
12:38:31 | CPU Thread 1 finds a Share, value 60000
12:38:31 | Accepted by the pool in 77 ms.
12:38:36 | GPU 1 Thread 9 Lane 796 finds a Share, value 60000
12:38:36 | Accepted by the pool in 81 ms.
12:38:37 | Hashrate CPU Thread 0: 81.75 h/s
12:38:37 | Hashrate CPU Thread 1: 81.95 h/s
12:38:37 | Hashrate CPU Thread 2: 81.93 h/s
12:38:37 | Hashrate CPU Thread 3: 81.85 h/s
12:38:37 | Hashrate CPU Thread 4: 81.24 h/s
12:38:37 | Hashrate CPU Thread 5: 82.56 h/s
12:38:37 | Hashrate CPU Thread 6: 82.34 h/s
12:38:37 | Hashrate CPU Thread 7: 82.82 h/s - Total CPUs: 656.40 h/s
12:38:37 | Hashrate GPU Thread 8: 518.72 h/s
12:38:37 | Hashrate GPU Thread 9: 518.31 h/s - Total GPU 1: 1037.02 h/s
12:38:37 | Total: 1693.42 h/s - Max: 1693.42 h/s
12:38:58 | GPU 1: Temp: 52C - Fan: 19% -- Shares: Good: 8 Bad: 0
12:39:24 | Pool sends a new Job.
12:40:48 | GPU 1 Thread 8 Lane 647 finds a Share, value 60000
12:40:49 | Accepted by the pool in 79 ms.
12:41:11 | GPU 1 Thread 8 Lane 793 finds a Share, value 60000
12:41:11 | Accepted by the pool in 38 ms.
12:41:36 | GPU 1 Thread 8 Lane 590 finds a Share, value 60000
12:41:36 | Accepted by the pool in 39 ms.
12:42:10 | Hashrate CPU Thread 0: 75.99 h/s
12:42:10 | Hashrate CPU Thread 1: 76.42 h/s
12:42:10 | Hashrate CPU Thread 2: 77.06 h/s
12:42:10 | Hashrate CPU Thread 3: 76.55 h/s
12:42:10 | Hashrate CPU Thread 4: 69.60 h/s
12:42:10 | Hashrate CPU Thread 5: 72.40 h/s
12:42:10 | Hashrate CPU Thread 6: 72.01 h/s
12:42:10 | Hashrate CPU Thread 7: 72.88 h/s - Total CPUs: 592.87 h/s
12:42:10 | Hashrate GPU Thread 8: 518.54 h/s
12:42:10 | Hashrate GPU Thread 9: 518.63 h/s - Total GPU 1: 1037.16 h/s
12:42:10 | Total: 1630.03 h/s - Max: 1693.42 h/s
12:42:44 | GPU 1: Temp: 53C - Fan: 17% -- Shares: Good: 11 Bad: 0
12:43:32 | Pool ctl.pool.mine2gether.com:4444
12:43:32 | Reconnections 0
12:43:32 | Currency Bitcedi (BXC)
12:43:32 | Current pool Difficulty 60000
12:43:32 | Accepted Shares 15
12:43:32 | Total Hashes 900000
12:43:32 | Miner uptime 0:08:59
12:43:32 | Effective net hashrate 1669.76 h/s
12:43:32 | Devices results - Shares Accepted/Ignored/Rejected - Net Hashrate
12:43:32 | * CPUs  -  4/0/0 -  445.27 h/s
12:43:32 | * GPU 1 - 11/0/0 - 1224.49 h/s
12:43:41 | GPU 1 Thread 8 Lane 468 finds a Share, value 60000
12:43:41 | Accepted by the pool in 38 ms.
12:44:55 | Pool sends a new Job.
12:45:33 | CPU Thread 7 finds a Share, value 60000
12:45:33 | Accepted by the pool in 64 ms.
12:45:43 | Hashrate CPU Thread 0: 78.59 h/s
12:45:43 | Hashrate CPU Thread 1: 79.03 h/s
12:45:43 | Hashrate CPU Thread 2: 79.24 h/s
12:45:43 | Hashrate CPU Thread 3: 78.80 h/s
12:45:43 | Hashrate CPU Thread 4: 73.84 h/s
12:45:43 | Hashrate CPU Thread 5: 76.10 h/s
12:45:43 | Hashrate CPU Thread 6: 75.65 h/s
12:45:43 | Hashrate CPU Thread 7: 76.49 h/s - Total CPUs: 617.70 h/s
12:45:43 | Hashrate GPU Thread 8: 517.90 h/s
12:45:43 | Hashrate GPU Thread 9: 516.00 h/s - Total GPU 1: 1033.89 h/s
12:45:43 | Total: 1651.59 h/s - Max: 1693.42 h/s
12:46:02 | GPU 1 Thread 8 Lane 834 finds a Share, value 60000
12:46:02 | Accepted by the pool in 72 ms.
12:46:05 | GPU 1 Thread 8 Lane 394 finds a Share, value 60000
12:46:05 | Accepted by the pool in 39 ms.
12:46:19 | GPU 1 Thread 8 Lane 21 finds a Share, value 60000
12:46:19 | Accepted by the pool in 39 ms.
12:46:30 | GPU 1: Temp: 54C - Fan: 17% -- Shares: Good: 15 Bad: 0
12:46:39 | CPU Thread 6 finds a Share, value 60000
12:46:40 | Accepted by the pool in 87 ms.
12:46:55 | GPU 1 Thread 8 Lane 603 finds a Share, value 60000
12:46:55 | Accepted by the pool in 41 ms.
12:47:52 | Pool sends a new Job.
12:48:06 | CPU Thread 3 finds a Share, value 60000
12:48:06 | Accepted by the pool in 39 ms.
12:48:07 | GPU 1 Thread 8 Lane 878 finds a Share, value 60000
12:48:07 | Accepted by the pool in 38 ms.
12:48:16 | CPU Thread 7 finds a Share, value 60000
12:48:16 | Accepted by the pool in 39 ms.
12:48:54 | CPU Thread 4 finds a Share, value 60000
12:48:54 | Accepted by the pool in 39 ms.
12:48:58 | GPU 1 Thread 8 Lane 297 finds a Share, value 60000
12:48:58 | Accepted by the pool in 39 ms.
12:49:16 | Hashrate CPU Thread 0: 75.71 h/s
12:49:16 | Hashrate CPU Thread 1: 76.27 h/s
12:49:16 | Hashrate CPU Thread 2: 76.48 h/s
12:49:16 | Hashrate CPU Thread 3: 71.70 h/s
12:49:16 | Hashrate CPU Thread 4: 76.07 h/s
12:49:16 | Hashrate CPU Thread 5: 77.42 h/s
12:49:16 | Hashrate CPU Thread 6: 77.42 h/s
12:49:16 | Hashrate CPU Thread 7: 77.89 h/s - Total CPUs: 608.91 h/s
12:49:16 | Hashrate GPU Thread 8: 518.54 h/s
12:49:16 | Hashrate GPU Thread 9: 518.54 h/s - Total GPU 1: 1037.07 h/s
12:49:16 | Total: 1645.98 h/s - Max: 1693.42 h/s
12:50:16 | GPU 1: Temp: 53C - Fan: 17% -- Shares: Good: 18 Bad: 0
12:50:43 | Pool sends a new Job.
12:51:03 | GPU 1 Thread 8 Lane 493 finds a Share, value 60000
12:51:03 | Accepted by the pool in 38 ms.
12:51:24 | Pool sends a new Job.


Okay man! Thanks for your feedback. I've tried 25k and 50k without no luck...it goes up to 350k super fast...
I'll try with higher values of diff to see if something changes!

Cheers!
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 07/09/2018, 09:13:49 UTC
...fixed diff still not working for me...I really have NO clue why... Sad

Not every pools handle the fixed difficulty feature, and each one that handles it does it in its own way, usually with wallet.diff or wallet+diff in the wallet field.

Which pool are you using?

I know! This pool does support it.
I'm here:
https://bxc.mine2gether.com
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 07/09/2018, 08:41:29 UTC
I just got the last version 32k2 and it's working super stable (as happened for me with 31f)
BUT fixed diff still not working for me...I really have NO clue why... Sad
Anyone having this issue???
Cheers!
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 26/08/2018, 10:26:08 UTC
Jumps to 400k ?
It's similar to a previous bug I already fixed about the share counter (which was a cosmetical but misleading bug). And again, only for CN-Heavy. I'll take a look back once i'm done with the Watchdog.

Yeah, actually taking a closer look, it did arrive to 1.5m diff... Shocked
Btw, I'm using 32f version of the miner cause I don't know why, last version wasn't stable for me.
After some time one of the cards randomly stops and resets its clocks to 300mhz...mega weird...
Anyways, this doesn't happen (like NEVER) using 32f miner version Cheesy

Cheers mate!
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 26/08/2018, 08:39:33 UTC
Thanks Smiley

Quote
Weird part is that when using fixed diff like 25k with jce-miner, diff changes after some time but same 25k with xmr-stak, diff stays fixed...

Interresting, so it may come from my netcode. A possible explaination could be the devfee session that may get a different diff as the user pool. But the devfee sessions are Claymore-style: small randomized sessions that don't disconnect your own pool, so you may encounter a few shares with a different diff from time to time (0.9% of time average) but not a permanent change.
Also strange is that i got this problem reported on CN-Heavy coins, while of course my netcode is the same whatever the coin is (only Nicehash has dedicated netcode).

This is not a big threat since all diff are equivalent in term of efficiency, but that's still a bug. Also check pool side the shares you get are the same as the effective hashrate reported by the yellow report, within a ~2% tolerance, and after a few hours of mining. If you observe a huge result difference, so it could be a critical bug. Cry

Yeah, true that it isn't a big threat but sometimes miner stays like 7 minutes without finding hashes.
For example I start at 25k diff but it increases (as far as I could see) to 400k...then moving up and down, etc.
Anyways, thanks mate!
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 25/08/2018, 21:23:55 UTC

Quote
BUT after mining a bit,
it starts to increase, decrease, etc, as if you don't put anything!
I haven't tested explicitely, but some (most?) pools will force a variable diff if you mine too fast or too slow with a fixed diff. Look at the log, if you get a message "Pool changes Difficulty to XXXX." so that's your pool's job, JCE don't change the diff by itself. I'll switch one rig to that pool for a few hours to check for that (but I mine v7 and not Heavy since i've low-mem cards).

Hi again and thanks for the answer.
So, i do get the message: "Pool changes Difficulty to XXXX." therefore as you say it's a pool's job.
Weird part is that when using fixed diff like 25k with jce-miner, diff changes after some time but same 25k with xmr-stak, diff stays fixed... :/

Cheers!
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 25/08/2018, 16:32:09 UTC

Quote
I'm mining veronite (pool.veronite.space), and yeah, I tried both "+" and "." but nothing works...
Veronite is to be added in the upcoming 0.32i, meanwhile you can mine with parameter --any --variation 5
let me check on that pool, it will be a good test for the new native Veronite support

edit, tried with current version (the wallet is a dummy one):

Code:
jce_cn_gpu_miner64.exe --auto -u VERayYXDx83WepmMzP5JWkXUqdu578QJ9dEnTpJfSKR2E5vfKM2dPnyfNACMjxLbZnYdPNf3HwTbtbxxEvDniXaGGxTurqtziGs.10000 -o pool.veronite.space:3333 -p x
Wallet does not match any of the supported currencies,
or your wallet couldn't be recognized.
Either use both the --any and --variation N parameters, with N one of:
  1 = Original Cryptonight
  2 = Original Cryptolight
  3 = Cryptonight V7 fork of April-2018
  4 = Cryptolight V7 fork of April-2018
  5 = Cryptonight-Heavy
  6 = Cryptolight-IPBC
  7 = Cryptonight-XTL fork of May-2018
  8 = Cryptonight-Alloy fork of May-2018
  9 = Cryptonight-MKT fork of May-2018
 10 = Cryptonight-Arto fork of May-2018
 11 = Cryptonight-Fast MSR fork of June-2018
 12 = Cryptonight-Haven fork of June-2018
 13 = Cryptonight-BitTube v2 of July-2018

Expected, and it says what to do: add --any --variation N with N=Cryptonight-Heavy=5

Code:
jce_cn_gpu_miner64.exe --auto -u VERayYXDx83WepmMzP5JWkXUqdu578QJ9dEnTpJfSKR2E5vfKM2dPnyfNACMjxLbZnYdPNf3HwTbtbxxEvDniXaGGxTurqtziGs.10000 -o pool.veronite.space:3333 -p x --any --variation 5
...
17:14:54 | Connected to pool. Now logging in...
17:14:54 | Successfuly logged as VERayYXDx83WepmMzP5JWkXUqdu578QJ9dEnTpJfSKR2E5vfKM2dPnyfNACMjxLbZnYdPNf3HwTbtbxxEvDniXaGGxTurqtziGs.10000
17:14:54 | Pool changes Difficulty to 10000.
17:14:57 | Pool sends a new Job.
[/quote]


Thanks for the answer man. And yes, it does set the diff to whatever you put after the ".", BUT after mining a bit,
it starts to increase, decrease, etc, as if you don't put anything!
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 25/08/2018, 14:59:54 UTC
Hey JCE-Miner (and everybody).
I'm using 32f version for GPU and static diff option (using the dot ".") after the address
doesn't seem to be working...

Someone has the same problem ?
Apparently it is supported by the miner (and also by the mining pool...)

Cheers!

which pool?
some pools want "+" instead of "."

I'm mining veronite (pool.veronite.space), and yeah, I tried both "+" and "." but nothing works...
When using other miner, for example xmr-stak, it does work...
Post
Topic
Board Mining (Altcoins)
Re: [XMR] JCE Miner Cryptonight/forks, now with GPU!
by
monote
on 25/08/2018, 13:15:36 UTC
Hey JCE-Miner (and everybody).
I'm using 32f version for GPU and static diff option (using the dot ".") after the address
doesn't seem to be working...

Someone has the same problem ?
Apparently it is supported by the miner (and also by the mining pool...)

Cheers!
Post
Topic
Board Announcements (Altcoins)
Re: 🔥🔥[ANN][WEB]🌎Webchain⚡️CPU mining⚡️DApps via Websites and IoT🚀No ICO or ASIC
by
monote
on 24/05/2018, 06:51:40 UTC
Question! What happened with the balance of the backup pool? Now that pool redirects to official one BUT balance there is
the one we had before the DDOS...
Post
Topic
Board Announcements (Altcoins)
Re: 🔥🔥[ANN][WEB]🌎Webchain⚡️CPU mining⚡️DApps via Websites and IoT🚀No ICO or ASIC
by
monote
on 23/05/2018, 17:11:02 UTC
Yes, official pool is down as well...
Post
Topic
Board Announcements (Altcoins)
Re: 🔥🔥[ANN][WEB]🌎Webchain⚡️CPU mining⚡️DApps via Websites and IoT🚀No ICO or ASIC
by
monote
on 23/05/2018, 16:55:53 UTC
Only pool working for me is: http://webchain.typemine.com

What about you guys?