[ANN] a new coin based on Litecoin - CHNCoin

[Mushoz]

First time solo here... I have a quick question about it.

my miner is connected to my solo server, so... finding new blocks are purely based on luck? is it normal that i have nothing for like 20minutes?

Yes, completely normal. It depends a lot on your hashrate how long it is expected to take to find a block.

[megablue]

First time solo here... I have a quick question about it.

my miner is connected to my solo server, so... finding new blocks are purely based on luck? is it normal that i have nothing for like 20minutes?

Yes, completely normal. It depends a lot on your hashrate how long it is expected to take to find a block.

Thanks! I was afraid of i did something wrong.

[Doono]

First time solo here... I have a quick question about it.

my miner is connected to my solo server, so... finding new blocks are purely based on luck? is it normal that i have nothing for like 20minutes?

Yep, I have had 2 blocks in 20 minutes and at the moment I'm on zero blocks for about 2 hours. Complete luck, this coin is particularly bad due to the amount of orphans that are generated. Think I get roughly 1 in 3 confirmed block as genuine and not an orphan

[Blue_oxen]

I use reaper since I've always had issues with cgminer


QT settings

Code:

rpcuser= ****
rpcpassword= ***
rpcallowip=127.0.0.*
rpcport=8844
daemon=1
server=1

reaper config

host 127.0.0.1
port 8844
user xxxxx
pass xxxxx

protocol litecoin

worksize 256
aggression 17
threads_per_gpu 1
sharethreads 32
lookup_gap 2
gpu_thread_concurrency 22392
long_polling yes

Thanks man I am finding coins now that im using reaper instead of cgminer.

[Doono]

Thanks man I am finding coins now that im using reaper instead of cgminer.

No worries, glad I could help 

[megablue]

First time solo here... I have a quick question about it.

my miner is connected to my solo server, so... finding new blocks are purely based on luck? is it normal that i have nothing for like 20minutes?

Yep, I have had 2 blocks in 20 minutes and at the moment I'm on zero blocks for about 2 hours. Complete luck, this coin is particularly bad due to the amount of orphans that are generated. Think I get roughly 1 in 3 confirmed block as genuine and not an orphan

A moment ago, I just got 3 rejected, 1 Accepted... anyhow it is good to know it is working fine

[md34ma]

We need to get a hold of the OP and help him improve his site, forum, image, promote, advertise. etc.

https://github.com/CHNCoin

^_^

[noyvpom]

So, I have seen multiple diff jumps from when this was released. The OP says it should be a 60sec block target, I think he must have screwed up tho, I have never seen it less than a few seconds. Is this correct?

If it is always going to be just a few seconds, then the mining will slowly migrate to a specific location / country and mining outside of that area will not be worth it due to latency, rejects and orphans.

[fendlestick]

I'm mining at the EU pool and getting avg 88 CNC every ten minutes from the UK, pretty good at the moment.

[Mushoz]

I'm mining at the EU pool and getting avg 88 CNC every ten minutes from the UK, pretty good at the moment.

What's your hashrate? That's very good indeed!

[tidus_13]

I'm mining at the EU pool and getting avg 88 CNC every ten minutes from the UK, pretty good at the moment.

What pool and how many kh/s

[Doono]

So, I have seen multiple diff jumps from when this was released. The OP says it should be a 60sec block target, I think he must have screwed up tho, I have never seen it less than a few seconds. Is this correct?

If it is always going to be just a few seconds, then the mining will slowly migrate to a specific location / country and mining outside of that area will not be worth it due to latency, rejects and orphans.

I imagine it should begin to fix itself once the difficulty begins to rise significantly. I imagine an enormous amount of hashing power is joining the network constantly skewing the block rate. The difficulty has continued to rise considerably at each refocusing, my mining rate has plummeted over the last few hours.

[noyvpom]

So, I have seen multiple diff jumps from when this was released. The OP says it should be a 60sec block target, I think he must have screwed up tho, I have never seen it less than a few seconds. Is this correct?

If it is always going to be just a few seconds, then the mining will slowly migrate to a specific location / country and mining outside of that area will not be worth it due to latency, rejects and orphans.

I imagine it should begin to fix itself once the difficulty begins to rise significantly. I imagine an enormous amount of hashing power is joining the network constantly skewing the block rate. The difficulty has continued to rise considerably at each refocusing.

I thought this was the case originally, and correct me if I'm wrong, every time the diff jumps it should change to around 60 seconds and then, as hashing power come on board, gets back down to 1-4 seconds etc. But I haven't seen this, it always seem to be be continually 1-4 seconds per block, even right after a diff jump? Makes m think the code is wrong, 6 seconds instead of 60 etc

[fendlestick]

2.6MH @ chn.bounceme.net:44397

[Mushoz]

So, I have seen multiple diff jumps from when this was released. The OP says it should be a 60sec block target, I think he must have screwed up tho, I have never seen it less than a few seconds. Is this correct?

If it is always going to be just a few seconds, then the mining will slowly migrate to a specific location / country and mining outside of that area will not be worth it due to latency, rejects and orphans.

I imagine it should begin to fix itself once the difficulty begins to rise significantly. I imagine an enormous amount of hashing power is joining the network constantly skewing the block rate. The difficulty has continued to rise considerably at each refocusing.

I thought this was the case originally, and correct me if I'm wrong, every time the diff jumps it should change to around 60 seconds and then, as hashing power come on board, gets back down to 1-4 seconds etc. But I haven't seen this, it always seem to be be continually 1-4 seconds per block, even right after a diff jump? Makes m think the code is wrong, 6 seconds instead of 60 etc

Difficulty cannot increase by more than a factor of 4. That's why the difficulty re-target cannot keep up at the moment with the ever increasing hashpower pointed to CHNcoin. It will catch up eventually, though.

[md34ma]

http://s1.postimg.org/gh5yd1lez/cnc1.jpg

2.6MH @ chn.bounceme.net:44397

That's another pool?

[fendlestick]

Aye its in EU so it's nice and close.

[noyvpom]

So, I have seen multiple diff jumps from when this was released. The OP says it should be a 60sec block target, I think he must have screwed up tho, I have never seen it less than a few seconds. Is this correct?

If it is always going to be just a few seconds, then the mining will slowly migrate to a specific location / country and mining outside of that area will not be worth it due to latency, rejects and orphans.

I imagine it should begin to fix itself once the difficulty begins to rise significantly. I imagine an enormous amount of hashing power is joining the network constantly skewing the block rate. The difficulty has continued to rise considerably at each refocusing.

I thought this was the case originally, and correct me if I'm wrong, every time the diff jumps it should change to around 60 seconds and then, as hashing power come on board, gets back down to 1-4 seconds etc. But I haven't seen this, it always seem to be be continually 1-4 seconds per block, even right after a diff jump? Makes m think the code is wrong, 6 seconds instead of 60 etc

Difficulty cannot increase by more than a factor of 4. That's why the difficulty re-target cannot keep up at the moment with the ever increasing hashpower pointed to CHNcoin. It will catch up eventually, though.

Oh right, thanks, that explains it, I did not realize difficulty could only do a factor of 4, is that just a made up constraint, or something to do with how the crypto actually works? In that case, assuming the code is correct, I guess the constant 1-4 second blocks are just reflecting the insane increase of hashing power pouring in to CHNCoin!

[Doono]

Oh right, thanks, that explains it, I did not realize difficulty could only do a factor of 4, is that just a made up constraint, or something to do with how the crypto actually works? In that case, assuming the code is correct, I guess the constant 1-4 second blocks are just reflecting the insane increase of hashing power pouring in to CHNCoin!

This I didn't realise myself but it makes total sense, this prevent the difficulty from rising to ludicrous levels if for a brief period of time someone points an obscene amount of hashing power just before the retarget

[md34ma]

Difficulty just went up guys!

It's now 1.