jc12345
Legendary
Offline
Activity: 1638
Merit: 1013
|
|
October 29, 2017, 08:33:53 PM |
|
Is there a plan to get onto exchanges and what is the timeline?
|
|
|
|
cryptonomicon25
Member
Offline
Activity: 460
Merit: 12
|
|
October 29, 2017, 08:38:58 PM |
|
Hello Amd fx 8320e 8 cores I have not resolved blocks
I would just solo mine with your setup, you should easily be able to find blocks. Now I'm mining with the wallet getmininginfo 17:27:18  { "blocks" : 763, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : 0.00302854, "errors" : "", "genproclimit" : -6, "networkhashps" : 86587, "pooledtx" : 0, "testnet" : false, "generate" : true, "hashespersec" : 241 } It's strange that your proclimit is showing -6, it should be -1 for all processors or a positive number for anything less. If you just type "setgenerate true" it should automatically use all 6 threads.
|
|
|
|
Angelo38
|
|
October 29, 2017, 08:42:21 PM |
|
Hello Amd fx 8320e 8 cores I have not resolved blocks
I would just solo mine with your setup, you should easily be able to find blocks. Now I'm mining with the wallet getmininginfo 17:27:18  { "blocks" : 763, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : 0.00302854, "errors" : "", "genproclimit" : -6, "networkhashps" : 86587, "pooledtx" : 0, "testnet" : false, "generate" : true, "hashespersec" : 241 } It's strange that your proclimit is showing -6, it should be -1 for all processors or a positive number for anything less. If you just type "setgenerate true" it should automatically use all 6 threads. This appears to me setgenerate true  getmininginfo 17:40:34  { "blocks" : 772, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : 0.00264232, "errors" : "", "genproclimit" : -1, "networkhashps" : 92049, "pooledtx" : 0, "testnet" : false, "generate" : true, "hashespersec" : 304 }
|
|
|
|
cryptonomicon25
Member
Offline
Activity: 460
Merit: 12
|
|
October 29, 2017, 08:44:54 PM |
|
Hello Amd fx 8320e 8 cores I have not resolved blocks
I would just solo mine with your setup, you should easily be able to find blocks. Now I'm mining with the wallet getmininginfo 17:27:18  { "blocks" : 763, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : 0.00302854, "errors" : "", "genproclimit" : -6, "networkhashps" : 86587, "pooledtx" : 0, "testnet" : false, "generate" : true, "hashespersec" : 241 } It's strange that your proclimit is showing -6, it should be -1 for all processors or a positive number for anything less. If you just type "setgenerate true" it should automatically use all 6 threads. This appears to me setgenerate true  getmininginfo 17:40:34  { "blocks" : 772, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : 0.00264232, "errors" : "", "genproclimit" : -1, "networkhashps" : 92049, "pooledtx" : 0, "testnet" : false, "generate" : true, "hashespersec" : 304 } That's right, -1 means all threads are being used, but your hashrate seems low still since you were getting 2500 h/s with minerd.
|
|
|
|
Angelo38
|
|
October 29, 2017, 08:51:32 PM |
|
Hello Amd fx 8320e 8 cores I have not resolved blocks
I would just solo mine with your setup, you should easily be able to find blocks. Now I'm mining with the wallet getmininginfo 17:27:18  { "blocks" : 763, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : 0.00302854, "errors" : "", "genproclimit" : -6, "networkhashps" : 86587, "pooledtx" : 0, "testnet" : false, "generate" : true, "hashespersec" : 241 } It's strange that your proclimit is showing -6, it should be -1 for all processors or a positive number for anything less. If you just type "setgenerate true" it should automatically use all 6 threads. This appears to me setgenerate true  getmininginfo 17:40:34  { "blocks" : 772, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : 0.00264232, "errors" : "", "genproclimit" : -1, "networkhashps" : 92049, "pooledtx" : 0, "testnet" : false, "generate" : true, "hashespersec" : 304 } That's right, -1 means all threads are being used, but your hashrate seems low still since you were getting 2500 h/s with minerd. thanks for your help My Doubt is. if I'm really mining https://ibb.co/j5FQO6
|
|
|
|
cryptonomicon25
Member
Offline
Activity: 460
Merit: 12
|
|
October 29, 2017, 08:58:29 PM |
|
I think the pool is not working correctly right now, if it was you would see yay!! after each share. Instead just mine solo and stop running minerd, if you are doing both at the same time it explains why your solo hashrate is so low.
|
|
|
|
joblo
Legendary
Offline
Activity: 1470
Merit: 1114
|
|
October 29, 2017, 08:58:42 PM |
|
woaw which cpu is that? my i7 thread 0: 8852 hashes, 0.16 khash/s and cant solve any block .test pool or solo doesnt mather I just built this algo in to yiimp,
Please test it at stratum+tcp://vdiff.thecryptopool.com:6234 -u <YOUR WALLET> -p c=YTN
PLEASE NOTE THIS IS A BETA TEST ON THIS ALGO.
Ill be monitoring to see and may take the stratum offline if coins are failing.
Hi, I'm mining in your pool I am doing it right? [2017-10-29 16:50:35] Accepted 6/6 (100%), 61.04 kH, 2535.41 H/s [2017-10-29 16:50:38] CPU #0: 18.55 kH, 431.87 H/s [2017-10-29 16:50:39] Accepted 7/7 (100%), 71.09 kH, 2552.67 H/s [2017-10-29 16:50:52] CPU #4: 24.19 kH, 428.96 H/s [2017-10-29 16:50:52] CPU #5: 24.60 kH, 433.61 H/s [2017-10-29 16:50:53] CPU #5: 292 H, 437.10 H/s [2017-10-29 16:50:53] Accepted 8/8 (100%), 78.43 kH, 2605.53 H/s [2017-10-29 16:50:55] CPU #1: 26.12 kH, 439.24 H/s [2017-10-29 16:50:55] CPU #2: 26.09 kH, 437.50 H/s [2017-10-29 16:50:58] CPU #1: 1459 H, 438.24 H/s [2017-10-29 16:50:58] Accepted 9/9 (100%), 87.63 kH, 2611.17 H/s Hello Amd fx 8320e 8 cores I have not resolved blocks You won't, those are yescrypt shares. Yet another pool configured for yescrypt instead of yescryptr16. You also need to use a yescryptr16 miner.
|
|
|
|
ir.hn
Member
Offline
Activity: 322
Merit: 54
Consensus is Constitution
|
|
October 29, 2017, 09:04:19 PM |
|
Yes, gen=1 will mine through the wallet. Remove it if you want to use minerd because otherwise minerd will throw an error since your port will already be in use. You can also just forget about minerd by opening the yenten-qt and navigating to Help > Debug window > Console and type:
setgenerate true 1
(1 because you are wanting to only run one thread. Change this number if you want to run more) This will allow you to mine directly through the wallet.
Thanks everyone who helped! I5 3230M [2017-10-29 13:58:24] thread 1: 483 hashes, 0.09 khash/s [2017-10-29 13:58:29] thread 0: 474 hashes, 0.09 khash/s [2017-10-29 13:58:29] thread 1: 473 hashes, 0.09 khash/s [2017-10-29 13:58:34] thread 0: 472 hashes, 0.09 khash/s [2017-10-29 13:58:35] thread 1: 473 hashes, 0.09 khash/s [2017-10-29 13:58:39] thread 1: 361 hashes, 0.09 khash/s [2017-10-29 13:58:39] thread 0: 449 hashes, 0.09 khash/s [2017-10-29 13:58:43] thread 1: 457 hashes, 0.10 khash/s [2017-10-29 13:58:44] thread 0: 452 hashes, 0.10 khash/s [2017-10-29 13:58:44] thread 1: 100 hashes, 0.10 khash/s [2017-10-29 13:58:49] thread 0: 483 hashes, 0.10 khash/s [2017-10-29 13:58:49] thread 1: 493 hashes, 0.10 khash/s [2017-10-29 13:58:54] thread 0: 493 hashes, 0.10 khash/s [2017-10-29 13:58:54] thread 1: 495 hashes, 0.10 khash/s [2017-10-29 13:58:59] thread 0: 497 hashes, 0.10 khash/s [2017-10-29 13:58:59] thread 1: 486 hashes, 0.10 khash/s [2017-10-29 13:59:04] thread 0: 482 hashes, 0.10 khash/s [2017-10-29 13:59:04] thread 1: 493 hashes, 0.10 khash/s [2017-10-29 13:59:09] thread 0: 484 hashes, 0.10 khash/s [2017-10-29 13:59:09] thread 1: 489 hashes, 0.10 khash/s
|
|
|
|
Angelo38
|
|
October 29, 2017, 09:12:29 PM |
|
Yes, gen=1 will mine through the wallet. Remove it if you want to use minerd because otherwise minerd will throw an error since your port will already be in use. You can also just forget about minerd by opening the yenten-qt and navigating to Help > Debug window > Console and type:
setgenerate true 1
(1 because you are wanting to only run one thread. Change this number if you want to run more) This will allow you to mine directly through the wallet.
Thanks everyone who helped! I5 3230M [2017-10-29 13:58:24] thread 1: 483 hashes, 0.09 khash/s [2017-10-29 13:58:29] thread 0: 474 hashes, 0.09 khash/s [2017-10-29 13:58:29] thread 1: 473 hashes, 0.09 khash/s [2017-10-29 13:58:34] thread 0: 472 hashes, 0.09 khash/s [2017-10-29 13:58:35] thread 1: 473 hashes, 0.09 khash/s [2017-10-29 13:58:39] thread 1: 361 hashes, 0.09 khash/s [2017-10-29 13:58:39] thread 0: 449 hashes, 0.09 khash/s [2017-10-29 13:58:43] thread 1: 457 hashes, 0.10 khash/s [2017-10-29 13:58:44] thread 0: 452 hashes, 0.10 khash/s [2017-10-29 13:58:44] thread 1: 100 hashes, 0.10 khash/s [2017-10-29 13:58:49] thread 0: 483 hashes, 0.10 khash/s [2017-10-29 13:58:49] thread 1: 493 hashes, 0.10 khash/s [2017-10-29 13:58:54] thread 0: 493 hashes, 0.10 khash/s [2017-10-29 13:58:54] thread 1: 495 hashes, 0.10 khash/s [2017-10-29 13:58:59] thread 0: 497 hashes, 0.10 khash/s [2017-10-29 13:58:59] thread 1: 486 hashes, 0.10 khash/s [2017-10-29 13:59:04] thread 0: 482 hashes, 0.10 khash/s [2017-10-29 13:59:04] thread 1: 493 hashes, 0.10 khash/s [2017-10-29 13:59:09] thread 0: 484 hashes, 0.10 khash/s [2017-10-29 13:59:09] thread 1: 489 hashes, 0.10 khash/s which miner is using what is the configuration of your bat file tanks
|
|
|
|
Nillecram
|
|
October 29, 2017, 09:20:12 PM |
|
crombiecrunch, could you share what i missed ?
|
|
|
|
Angelo38
|
|
October 29, 2017, 09:25:23 PM |
|
woaw which cpu is that? my i7 thread 0: 8852 hashes, 0.16 khash/s and cant solve any block .test pool or solo doesnt mather I just built this algo in to yiimp,
Please test it at stratum+tcp://vdiff.thecryptopool.com:6234 -u <YOUR WALLET> -p c=YTN
PLEASE NOTE THIS IS A BETA TEST ON THIS ALGO.
Ill be monitoring to see and may take the stratum offline if coins are failing.
Hi, I'm mining in your pool I am doing it right? [2017-10-29 16:50:35] Accepted 6/6 (100%), 61.04 kH, 2535.41 H/s [2017-10-29 16:50:38] CPU #0: 18.55 kH, 431.87 H/s [2017-10-29 16:50:39] Accepted 7/7 (100%), 71.09 kH, 2552.67 H/s [2017-10-29 16:50:52] CPU #4: 24.19 kH, 428.96 H/s [2017-10-29 16:50:52] CPU #5: 24.60 kH, 433.61 H/s [2017-10-29 16:50:53] CPU #5: 292 H, 437.10 H/s [2017-10-29 16:50:53] Accepted 8/8 (100%), 78.43 kH, 2605.53 H/s [2017-10-29 16:50:55] CPU #1: 26.12 kH, 439.24 H/s [2017-10-29 16:50:55] CPU #2: 26.09 kH, 437.50 H/s [2017-10-29 16:50:58] CPU #1: 1459 H, 438.24 H/s [2017-10-29 16:50:58] Accepted 9/9 (100%), 87.63 kH, 2611.17 H/s Hello Amd fx 8320e 8 cores I have not resolved blocks You won't, those are yescrypt shares. Yet another pool configured for yescrypt instead of yescryptr16. You also need to use a yescryptr16 miner. thanks for your help
|
|
|
|
vingaard
Legendary
Offline
Activity: 1246
Merit: 1011
|
|
October 29, 2017, 09:33:05 PM |
|
I just built this algo in to yiimp,
Please test it at stratum+tcp://vdiff.thecryptopool.com:6234 -u <YOUR WALLET> -p c=YTN
PLEASE NOTE THIS IS A BETA TEST ON THIS ALGO.
Ill be monitoring to see and may take the stratum offline if coins are failing.
You can't get any block because you are using a yescrypt algo and you must use the new algo yescryptr16. There isn't a pool for this coin yet?
|
|
|
|
Angelo38
|
|
October 29, 2017, 09:38:58 PM |
|
I just built this algo in to yiimp,
Please test it at stratum+tcp://vdiff.thecryptopool.com:6234 -u <YOUR WALLET> -p c=YTN
PLEASE NOTE THIS IS A BETA TEST ON THIS ALGO.
Ill be monitoring to see and may take the stratum offline if coins are failing.
You can't get any block because you are using a yescrypt algo and you must use the new algo yescryptr16. There isn't a pool for this coin yet? in the last place it says yenten (yescrypt) https://thecryptopool.com/site/miningBut I'm not sure
|
|
|
|
|
andronikos
|
|
October 29, 2017, 10:12:08 PM |
|
Question. How do you unlock your wallet since there is no unlock option?
|
|
|
|
coinhunter_mt2
Newbie
Offline
Activity: 56
Merit: 0
|
|
October 29, 2017, 10:17:57 PM |
|
I just built this algo in to yiimp,
Please test it at stratum+tcp://vdiff.thecryptopool.com:6234 -u <YOUR WALLET> -p c=YTN
PLEASE NOTE THIS IS A BETA TEST ON THIS ALGO.
Ill be monitoring to see and may take the stratum offline if coins are failing.
You can't get any block because you are using a yescrypt algo and you must use the new algo yescryptr16. There isn't a pool for this coin yet? waiting for the official launch of Yenten coin
|
|
|
|
crombiecrunch
Member
Offline
Activity: 98
Merit: 10
|
|
October 30, 2017, 12:04:37 AM |
|
still working on getting this built in. its being a pain
|
|
|
|
cyberspacemonkey
Legendary
Offline
Activity: 1288
Merit: 1002
|
|
October 30, 2017, 12:09:52 AM |
|
Is this a "new" algo? looks interesting, I might give it a try specially if it's intended to give advantage to CPU miners.
|
|
|
|
ir.hn
Member
Offline
Activity: 322
Merit: 54
Consensus is Constitution
|
|
October 30, 2017, 12:15:37 AM |
|
Yes, gen=1 will mine through the wallet. Remove it if you want to use minerd because otherwise minerd will throw an error since your port will already be in use. You can also just forget about minerd by opening the yenten-qt and navigating to Help > Debug window > Console and type:
setgenerate true 1
(1 because you are wanting to only run one thread. Change this number if you want to run more) This will allow you to mine directly through the wallet.
Thanks everyone who helped! I5 3230M [2017-10-29 13:58:24] thread 1: 483 hashes, 0.09 khash/s [2017-10-29 13:58:29] thread 0: 474 hashes, 0.09 khash/s [2017-10-29 13:58:29] thread 1: 473 hashes, 0.09 khash/s [2017-10-29 13:58:34] thread 0: 472 hashes, 0.09 khash/s [2017-10-29 13:58:35] thread 1: 473 hashes, 0.09 khash/s [2017-10-29 13:58:39] thread 1: 361 hashes, 0.09 khash/s [2017-10-29 13:58:39] thread 0: 449 hashes, 0.09 khash/s [2017-10-29 13:58:43] thread 1: 457 hashes, 0.10 khash/s [2017-10-29 13:58:44] thread 0: 452 hashes, 0.10 khash/s [2017-10-29 13:58:44] thread 1: 100 hashes, 0.10 khash/s [2017-10-29 13:58:49] thread 0: 483 hashes, 0.10 khash/s [2017-10-29 13:58:49] thread 1: 493 hashes, 0.10 khash/s [2017-10-29 13:58:54] thread 0: 493 hashes, 0.10 khash/s [2017-10-29 13:58:54] thread 1: 495 hashes, 0.10 khash/s [2017-10-29 13:58:59] thread 0: 497 hashes, 0.10 khash/s [2017-10-29 13:58:59] thread 1: 486 hashes, 0.10 khash/s [2017-10-29 13:59:04] thread 0: 482 hashes, 0.10 khash/s [2017-10-29 13:59:04] thread 1: 493 hashes, 0.10 khash/s [2017-10-29 13:59:09] thread 0: 484 hashes, 0.10 khash/s [2017-10-29 13:59:09] thread 1: 489 hashes, 0.10 khash/s which miner is using what is the configuration of your bat file tanks No miner, no bat file. just the minerd thing. see my past posts for more info how I set it up
|
|
|
|
gawajn
|
|
October 30, 2017, 12:21:58 AM |
|
Nice to see a coin where it is worthwhile to mine with a cpu. What are the blockrewards after the first block? Still 50 YTN?
|
|
|
|
|