Topic: [ANN] [CPU mining] Yenten v2.0.1 [YTN] [YescryptR16] [Exchange avilable] - page 163. (Read 147137 times)

Dev please look over my post about adding wallet funcionality so people can encode a crowd-sourced exchange into the blockchain using op_return.  The full text of my whitepaper is included in the comments on the forum post

https://bitcointalksearch.org/topic/m.25870369

i’m still solo mining. anyone else?

discord: https://discord.gg/MW6aPzb

Wow nice, I tried to get it working on a pine64 which didn't work and it seemed to be missing x86 type operations so I assumed that yenten required x86 processors.  But that is interesting that you got it to work on ARM and not only that but on a non-ubuntu distro.  Would you mind writing up a little procedure on how to do it for a linux noob?  If this works on ARM it changes everything...

Also add up each core's hash/sec to get your total.

It just does, I did not do anything special.

Downloaded the source and compiled then ran the miner, no tweaks or anything and just used build.sh then make then ran it. So thats a question for the dev.

Only one invalid share overnight.

[2017-12-06 06:14:41] Accepted 1386/1387 (99.9%), 50.66 kH, 2753.15 H/s, 59C
[2017-12-06 06:14:43] CPU #9: 3752 H, 172.03 H/s
[2017-12-06 06:14:43] CPU #6: 3746 H, 171.77 H/s
[2017-12-06 06:14:43] CPU #15: 3754 H, 172.12 H/s
[2017-12-06 06:14:43] CPU #14: 3760 H, 172.39 H/s
[2017-12-06 06:14:43] CPU #8: 3716 H, 170.35 H/s
[2017-12-06 06:14:43] CPU #4: 3756 H, 172.19 H/s
[2017-12-06 06:14:43] CPU #0: 3744 H, 171.64 H/s
[2017-12-06 06:14:43] CPU #3: 3754 H, 172.09 H/s
[2017-12-06 06:14:43] CPU #2: 3763 H, 172.50 H/s
[2017-12-06 06:14:43] CPU #5: 3757 H, 172.21 H/s
[2017-12-06 06:14:43] CPU #7: 306 H, 172.39 H/s
[2017-12-06 06:14:43] CPU #1: 3759 H, 172.31 H/s
[2017-12-06 06:14:43] CPU #13: 3763 H, 172.49 H/s
[2017-12-06 06:14:43] CPU #10: 3758 H, 172.26 H/s
[2017-12-06 06:14:43] CPU #12: 3763 H, 172.49 H/s
[2017-12-06 06:14:43] CPU #11: 3763 H, 172.49 H/s
[2017-12-06 06:14:47] CPU #7: 829 H, 171.94 H/s
[2017-12-06 06:14:48] Accepted 1387/1388 (99.9%), 57.14 kH, 2753.26 H/s, 58C
[2017-12-06 06:14:50] yescryptr16 block 27393, diff 0.010

Now to solomine with 16 threads at the same time I pool mine to see what happens.


06:17:11

{
"blocks" : 27393,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00994770,
"errors" : "",
"genproclimit" : 16,
"networkhashps" : 298548,
"pooledtx" : 0,
"testnet" : false,
"generate" : true,
"hashespersec" : 1242
}

http://antminepool.com

how to show the degree? my cpu opt can't show degree info

intel core i7-2860QM from some years ago

I had the same thoughts. Bitzeny's main exchange has crashed so many times. Reminds me of cryptopia few months ago.

I would expect that the Yenten price is going to follow Bitzeny at a certain moment. Anyway wonder why the old lady (Bitzeny) is suddenly rising so fast.

So you are on which pool now.

So far so good!

[2017-12-05 21:04:40] Accepted 88/88 (100%), 133.42 kH, 2654.32 H/s, 62C
[2017-12-05 21:04:46] CPU #12: 2602 H, 170.98 H/s
[2017-12-05 21:04:46] Accepted 89/89 (100%), 127.06 kH, 2656.66 H/s, 61C

Much better.

[2017-12-05 19:44:03] CPU #24: 4152 H, 87.21 H/s
[2017-12-05 19:44:03] CPU #23: 4188 H, 87.95 H/s
[2017-12-05 19:44:03] CPU #0: 4201 H, 88.23 H/s
[2017-12-05 19:44:03] CPU #17: 4231 H, 88.85 H/s
[2017-12-05 19:44:03] CPU #3: 4205 H, 88.31 H/s
[2017-12-05 19:44:03] CPU #18: 4342 H, 91.20 H/s
[2017-12-05 19:44:03] CPU #2: 3432 H, 72.09 H/s
[2017-12-05 19:44:03] CPU #22: 4136 H, 86.86 H/s
[2017-12-05 19:44:03] CPU #25: 3997 H, 83.94 H/s
[2017-12-05 19:44:03] CPU #5: 4183 H, 87.86 H/s
[2017-12-05 19:44:03] CPU #16: 4137 H, 86.89 H/s
[2017-12-05 19:44:03] CPU #6: 4174 H, 87.65 H/s
[2017-12-05 19:44:03] CPU #4: 1603 H, 86.72 H/s
[2017-12-05 19:44:03] CPU #20: 4191 H, 88.02 H/s
[2017-12-05 19:44:03] CPU #21: 4187 H, 87.94 H/s
[2017-12-05 19:44:03] CPU #19: 4138 H, 86.91 H/s
[2017-12-05 19:44:03] CPU #1: 3902 H, 81.93 H/s
[2017-12-05 19:44:03] CPU #7: 4013 H, 84.27 H/s
[2017-12-05 19:44:03] CPU #10: 4155 H, 87.25 H/s
[2017-12-05 19:44:03] CPU #12: 4155 H, 87.25 H/s
[2017-12-05 19:44:03] CPU #27: 4121 H, 86.55 H/s
[2017-12-05 19:44:03] CPU #14: 1688 H, 87.16 H/s
[2017-12-05 19:44:03] CPU #31: 4155 H, 87.25 H/s
[2017-12-05 19:44:03] CPU #28: 4155 H, 87.25 H/s
[2017-12-05 19:44:03] CPU #15: 4154 H, 87.23 H/s
[2017-12-05 19:44:03] CPU #30: 4154 H, 87.23 H/s
[2017-12-05 19:44:03] CPU #26: 4155 H, 87.25 H/s
[2017-12-05 19:44:03] CPU #13: 4136 H, 86.85 H/s
[2017-12-05 19:44:03] CPU #11: 4163 H, 87.43 H/s
[2017-12-05 19:44:03] CPU #29: 4160 H, 87.36 H/s
[2017-12-05 19:44:03] CPU #9: 3700 H, 77.69 H/s
[2017-12-05 19:44:03] CPU #8: 4148 H, 87.11 H/s
[2017-12-05 19:44:08] CPU #1: 427 H, 88.17 H/s
[2017-12-05 19:44:08] Accepted 10/10 (100%), 123.14 kH, 2769.93 H/s, 63C
[2017-12-05 19:44:24] CPU #5: 1842 H, 88.07 H/s
[2017-12-05 19:44:24] Accepted 11/11 (100%), 120.80 kH, 2770.14 H/s, 62C
[2017-12-05 19:44:26] CPU #20: 2033 H, 88.31 H/s
[2017-12-05 19:44:26] Accepted 12/12 (100%), 118.64 kH, 2770.43 H/s, 63C
[2017-12-05 19:44:29] CPU #19: 2230 H, 87.12 H/s
[2017-12-05 19:44:29] Accepted 13/13 (100%), 116.73 kH, 2770.64 H/s, 62C

EDIT: Still having a few:

[2017-12-05 19:49:17] Rejected 3/29 (10.3%), 80.27 kH, 2752.78 H/s, 62C
[2017-12-05 19:49:17] reject reason: Invalid share

Soooo I changed it to 24 cores, that seemed to be the sweet spot solo mining, now going to run it a while.

[2017-12-05 19:51:45] Accepted 2/3 (66.7%), 14.82 kH, 2738.55 H/s, 63C
[2017-12-05 19:51:50] CPU #9: 1196 H, 170.17 H/s
[2017-12-05 19:51:50] Accepted 3/4 (75.0%), 15.00 kH, 2739.92 H/s, 62C

Only lost a tiny bit of hash rate running 24 threads.

EDIT2:

Changed to only 16 cores, have not lost much speed at all but still getting invalid shares.

Just got an invalid job id error.

{2017-12-05 20:06:31] Rejected 4/24 (16.7%), 34.45 kH, 2738.42 H/s, 63C
[2017-12-05 20:06:31] reject reason: Invalid job id
[2017-12-05 20:06:33] CPU #7: 505 H, 169.63 H/s
[2017-12-05 20:06:34] Accepted 21/25 (84.0%), 32.68 kH, 2738.36 H/s, 62C


EDIT3: Changed to running 8 cores and no invalid shares but the hash rate dropped in half.

[2017-12-05 20:16:24] CPU #0: 6952 H, 172.83 H/s
[2017-12-05 20:16:24] CPU #4: 7658 H, 172.81 H/s
[2017-12-05 20:16:24] CPU #7: 7628 H, 172.11 H/s
[2017-12-05 20:16:24] CPU #5: 7659 H, 172.81 H/s
[2017-12-05 20:16:24] CPU #3: 7656 H, 172.74 H/s
[2017-12-05 20:16:24] CPU #2: 7659 H, 172.81 H/s
[2017-12-05 20:16:25] Stratum difficulty set to 1
[2017-12-05 20:16:43] CPU #2: 3159 H, 172.07 H/s
[2017-12-05 20:16:43] CPU #5: 3159 H, 172.07 H/s
[2017-12-05 20:16:43] CPU #3: 3029 H, 164.98 H/s
[2017-12-05 20:16:43] CPU #0: 3159 H, 172.02 H/s
[2017-12-05 20:16:43] CPU #1: 3159 H, 172.01 H/s
[2017-12-05 20:16:43] CPU #6: 3159 H, 172.01 H/s
[2017-12-05 20:16:43] CPU #4: 3161 H, 172.12 H/s
[2017-12-05 20:16:43] CPU #7: 3147 H, 171.35 H/s
[2017-12-05 20:17:07] CPU #1: 4036 H, 172.79 H/s
[2017-12-05 20:17:07] Accepted 6/6 (100%), 26.01 kH, 1369.41 H/s, 58C
[2017-12-05 20:17:22] CPU #1: 2554 H, 172.71 H/s
[2017-12-05 20:17:22] Accepted 7/7 (100%), 24.53 kH, 1369.33 H/s, 59C
[2017-12-05 20:17:26] CPU #1: 720 H, 172.70 H/s
[2017-12-05 20:17:26] Accepted 8/8 (100%), 22.69 kH, 1369.33 H/s, 59C
[2017-12-05 20:17:41] CPU #3: 9900 H, 172.76 H/s
[2017-12-05 20:17:43] CPU #7: 10.28 kH, 172.28 H/s
[2017-12-05 20:17:43] CPU #0: 10.32 kH, 172.74 H/s
[2017-12-05 20:17:43] CPU #6: 10.32 kH, 172.74 H/s
[2017-12-05 20:17:43] CPU #5: 10.32 kH, 172.74 H/s
[2017-12-05 20:17:43] CPU #2: 10.32 kH, 172.74 H/s
[2017-12-05 20:17:43] CPU #4: 10.33 kH, 172.74 H/s
[2017-12-05 20:17:46] yescryptr16 block 27100, diff 0.013
[2017-12-05 20:17:46] CPU #5: 531 H, 172.79 H/s

 

EDIT4: Jut got an invalid share again.....

2017-12-05 20:23:58] Stratum difficulty set to 1
[2017-12-05 20:23:59] CPU #0: 260 H, 162.04 H/s
[2017-12-05 20:24:00] Rejected 1/16 (6.2%), 36.54 kH, 1371.26 H/s, 58C
[2017-12-05 20:24:00] reject reason: Invalid share

Sooo I'm going to try another pool just to see if thats the problem.

EDIT5: That was the problem , changed pools and now I'm back to 16 threads and ~2745 H/s  

[2017-12-05 20:37:10] CPU #6: 2137 H, 171.52 H/s
[2017-12-05 20:37:10] CPU #5: 2127 H, 170.70 H/s
[2017-12-05 20:37:10] CPU #7: 2114 H, 169.67 H/s
[2017-12-05 20:37:10] CPU #3: 2150 H, 172.55 H/s
[2017-12-05 20:37:10] CPU #0: 2134 H, 171.25 H/s
[2017-12-05 20:37:16] CPU #1: 1082 H, 170.23 H/s
[2017-12-05 20:37:17] Accepted 19/19 (100%), 33.09 kH, 2739.61 H/s, 63C
[2017-12-05 20:37:28] CPU #7: 3005 H, 170.83 H/s
[2017-12-05 20:37:28] Accepted 20/20 (100%), 33.98 kH, 2740.77 H/s, 61C
[2017-12-05 20:37:38] CPU #14: 4818 H, 171.67 H/s
[2017-12-05 20:37:38] Accepted 21/21 (100%), 36.67 kH, 2741.66 H/s, 62C

Now i'll let it run overnight.

You could try disabling Hyperthreading in the BIOS and run with 16 "full" threads. Better than losing so many invalid shares or running at half power imo.
LOL indeed.

Nope, all go no show.

Just be glad all my other dual Xeon boxes are mining other coins......at least for now.


Trying pool mining now.

./cpuminer -a yescryptr16 -t 32 -o stratum+tcp://pool.bilbotel.fr:6234 -u Yxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -p c=YTN

I get about %50 invalid shares if I use all 32 threads but if I use 30 threads it drops to %25  

The fewer threads the lower the invalid shares but lower hash rates.

Trying only 16 threads fo a while.

EDIT:  I forgot I was already mining Sumokoin on all 32 threads. LOLOLOLOLOLOLOLOLOLOLO 


Fired up 32 threads again to see what happen now.

Poser. 

Dual Xeon E5-2667 V3 cpu's

Dual Xeon cpu's.

No, just two Xeon E5-2667 V3 cpu's.
8 cores each with hyperthreading so 32 total.

Finally got my Odroid XU3 lite mining by compiling yentend, wasn't able to compile cpuminer-opt. Is the source of minerd available somewhere?
Mining on 7 of 8 cores at 93°C, Hashrate reports vary wildly: most often it's around 63 but rarely it's reported as 0 or up to 140, probably some kind of lag. Not too bad for an ARM CPU (Exynos 5422), OS is Debian Wheezy. My properly cooled and slightly overclocked FX 8320E does 650 hashes per second btw.

Had to configure with --ignore-incompatible-bdb and remove a "-msse41" from yescrypt.h in src/hash/yescrypt. More could be possible with some ARM optimization and compile option tuning, my only CXXFLAG was O3.

Too bad the hashrate almost doubled today.  

What processor(s)?