[ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record

[wawaderwaran]

Finally got it working. Changes in your conf file

rpcport=28332
port=9337

And in your bat file

127.0.0.1:28332

Oh, strange. It worked for me the way it was though ^^

[EdwardWitten]

So are you guys running with ,inasne # of threads or only one thread per CPU?

[gatra]

@BChydro
Are you new to mining ? These are khash per thread.
Of course they don't vary with the number of threads ...

If you're using more threads than number of cores your cpu has, mining speed per thread should decrease. That instance has 32 cores, mining speed should max out at 32 threads. But the client reports the exact same speed per thread, even when I stuff 32 threads per core (1024 threads) That makes no sense.

That happens only in the first round when threads are initialized and tested. Leave it running 10 seconds and you'll see that if you have more threads than cores and you keep adding threads then each one starts going slower and the total mining speed does not improve.

[paulthetafy]

There has to be an optimised miner here - im not getting anywhere near what I should be with 4000 cores on it.  (Yes cores).

Who is mining this with a large farm and what stats are you getting?

[krneki]

is these ok ?mining with not the best computer and don't know if these is ok or do i have any chance for smth ?



{
"blocks" : 1206,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 2,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 40506958,
"pooledtx" : 0,
"testnet" : false
}

[cocoxxx]

have any pool?? hard to mine

[Al_Bundy]

Can't get wallet to connect with these nodes:
addnode=194.97.156.59
addnode=76.102.71.50
addnode=79.135.200.61
addnode=162.248.98.162
addnode=64.79.107.5
addnode=192.241.129.169
addnode=173.193.48.174
addnode=107.170.26.188
addnode=67.225.172.77
addnode=198.144.180.117
addnode=198.144.180.118
addnode=213.239.207.114:28333
addnode=108.161.145.12:28333
addnode=198.98.52.244:28333
addnode=198.98.52.244:28333
addnode=54.198.193.96:28333
addnode=162.243.118.47:28333
addnode=54.237.23.244:28333
addnode=107.170.32.187:28333
addnode=95.138.166.126:28333

Any others I can try?

[mmiaow]

Can't get wallet to connect with these nodes:
...
Any others I can try?

addnode=188.165.216.59
addnode=194.97.156.59
addnode=141.70.81.135
addnode=195.154.211.220
addnode=81.84.254.209
addnode=195.154.189.241
addnode=64.79.106.198
addnode=54.244.163.107
addnode=69.4.239.48
addnode=54.213.38.6
addnode=188.226.159.167
addnode=194.97.156.59
addnode=76.102.71.50
addnode=79.135.200.61
addnode=162.248.98.162
addnode=64.79.107.5
addnode=192.241.129.169
addnode=173.193.48.174
addnode=188.165.216.59:28333
addnode=194.97.156.59:28333
addnode=162.218.208.166:59945
addnode=5.83.137.131:38486
addnode=89.182.2.122:41312
addnode=195.47.113.76:39958
addnode=193.66.139.206:40381
addnode=193.87.208.3:46531
addnode=5.83.137.130:18047
addnode=144.76.225.167:56948
addnode=85.17.164.246:38590
addnode=37.128.134.156:57262
addnode=193.87.208.3:51571
addnode=193.87.208.30:59797
addnode=193.87.208.30:60328
addnode=193.166.139.206:37144
addnode=107.170.46.235:53304
addnode=106.187.91.40:28333
addnode=188.226.159.167:28333
addnode=54.213.38.6:28333
addnode=69.4.239.48:28333
addnode=54.244.163.107:28333
addnode=64.79.106.198:28333
addnode=195.154.189.241:39183
addnode=81.84.254.209:37117
addnode=195.154.211.220:50606
addnode=147.70.81.135:45041

From my conf, just replace your original ones, duplicated entries may exist.

[Al_Bundy]

Thank you sir.

Still no go. Number of connections briefly changes from 0 to 1 and back to 0. And repeat for a while
Weird.

[dinominant]

There has to be an optimised miner here - im not getting anywhere near what I should be with 4000 cores on it.  (Yes cores).

Who is mining this with a large farm and what stats are you getting?

I though I had a lot of cores going at ~100. I had problems getting more then ~100 threads mining on a single riecoind instance, so in desperation I switched to solomining on each host. I'll have to merge the wallets later, but I am getting about 500000 to 1200000 knumbers/s (per host) and from the few wallets I am monitoring I have found zero blocks.

[micryon]

There has to be an optimised miner here - im not getting anywhere near what I should be with 4000 cores on it.  (Yes cores).

Who is mining this with a large farm and what stats are you getting?

I though I had a lot of cores going at ~100. I had problems getting more then ~100 threads mining on a single riecoind instance, so in desperation I switched to solomining on each host. I'll have to merge the wallets later, but I am getting about 500000 to 1200000 knumbers/s (per host) and from the few wallets I am monitoring I have found zero blocks.

I had the same problem as you did.. but i ended up just just solomining on each host using the same wallet..  It seems to work..

[paulthetafy]

There has to be an optimised miner here - im not getting anywhere near what I should be with 4000 cores on it.  (Yes cores).

Who is mining this with a large farm and what stats are you getting?

I though I had a lot of cores going at ~100. I had problems getting more then ~100 threads mining on a single riecoind instance, so in desperation I switched to solomining on each host. I'll have to merge the wallets later, but I am getting about 500000 to 1200000 knumbers/s (per host) and from the few wallets I am monitoring I have found zero blocks.

Edit: yes I solo mine on each host.  Much easier.

the easiest approach so this is to use the same copy of wallet.dat on each instance.  you should generate is with more keys first though (launch riecoind -keypool=<n> ).  I usually suggest 1000, though in practice with this coin 100 should be plenty (thats 100 blocks mined per instance before wallet deviation).

That's the way I approach it anyway.

I'm still convinced there is an opimised miner out there.  I should be getting blocks every 14 mins now, and I'm not.  I have had 4 blocks since launch with 4000 cores

[Al_Bundy]

Thank you sir.

Still no go. Number of connections briefly changes from 0 to 1 and back to 0. And repeat for a while
Weird.

Sample of my debug log:
2014-02-12 03:17:44 trying connection 64.79.106.198:28333 lastseen=358937.5hrs
2014-02-12 03:17:44 connected 64.79.106.198:28333
2014-02-12 03:17:44 send version message: version 10070001, blocks=0, us=74.73.87.245:28333, them=64.79.106.198:28333, peer=64.79.106.198:28333
2014-02-12 03:17:45 socket closed


I appreciate your suggestions.

Thanks

[Walking Glitch]

There has to be an optimised miner here - im not getting anywhere near what I should be with 4000 cores on it.  (Yes cores).

Who is mining this with a large farm and what stats are you getting?

I'm mining 64 cores since before the diff had hit 100, and I have still to find a block.

[dinominant]

There has to be an optimised miner here - im not getting anywhere near what I should be with 4000 cores on it.  (Yes cores).

Who is mining this with a large farm and what stats are you getting?

I though I had a lot of cores going at ~100. I had problems getting more then ~100 threads mining on a single riecoind instance, so in desperation I switched to solomining on each host. I'll have to merge the wallets later, but I am getting about 500000 to 1200000 knumbers/s (per host) and from the few wallets I am monitoring I have found zero blocks.

Edit: yes I solo mine on each host.  Much easier.

the easiest approach so this is to use the same copy of wallet.dat on each instance.  you should generate is with more keys first though (launch riecoind -keypool=<n> ).  I usually suggest 1000, though in practice with this coin 100 should be plenty (thats 100 blocks mined per instance before wallet deviation).

That's the way I approach it anyway.

I'm still convinced there is an opimised miner out there.  I should be getting blocks every 14 mins now, and I'm not.  I have had 4 blocks since launch with 4000 cores

I had a wallet with 10000 keys pre-generated prior to the launch but I didn't have it distributed to the various hosts, and with all the attempts at restarting riecoind I didn't trust it's integrity. Also, what's to say each host is not testing the same pseudoprimes? How are the candidate numbers chosen and how is the PRNG seeded? Is it seeded with your receiving address and the previous block hash? If so, then you might have 4000 hosts all testing the exact same numbers.

[avesdude]

I get nothing but timeouts too. Can't sync.

[paulthetafy]

There has to be an optimised miner here - im not getting anywhere near what I should be with 4000 cores on it.  (Yes cores).

Who is mining this with a large farm and what stats are you getting?

I though I had a lot of cores going at ~100. I had problems getting more then ~100 threads mining on a single riecoind instance, so in desperation I switched to solomining on each host. I'll have to merge the wallets later, but I am getting about 500000 to 1200000 knumbers/s (per host) and from the few wallets I am monitoring I have found zero blocks.

Edit: yes I solo mine on each host.  Much easier.

the easiest approach so this is to use the same copy of wallet.dat on each instance.  you should generate is with more keys first though (launch riecoind -keypool=<n> ).  I usually suggest 1000, though in practice with this coin 100 should be plenty (thats 100 blocks mined per instance before wallet deviation).

That's the way I approach it anyway.

I'm still convinced there is an opimised miner out there.  I should be getting blocks every 14 mins now, and I'm not.  I have had 4 blocks since launch with 4000 cores

I had a wallet with 10000 keys pre-generated prior to the launch but I didn't have it distributed to the various hosts, and with all the attempts at restarting riecoind I didn't trust it's integrity. Also, what's to say each host is not testing the same pseudoprimes? How are the candidate numbers chosen and how is the PRNG seeded? Is it seeded with your receiving address and the previous block hash? If so, then you might have 4000 hosts all testing the exact same numbers.

THAT is a very very good point.  Checking the source now.  also I am using an image to replicate across my farm.  that might not be helping things (though has been fine for other coins)

[see360]

6456 seconds down, only 703,000 seconds (8 days, 3 hours) to go :-)


i7 3820 @ 3.6 GHz, So far I've only tried this with minerd.

[6strings]

At this difficulty, I think a price of at least 0.005-0.01 each seems sensible.  They are HARD to mine

0.006-0.008 is where i'd put it. this is difficult to mine. holy hell with what im throwing at it i expected much more. awesome though.

[gatra]

I'll leave you some nodes and go to sleep...

addnode=107.170.26.188
addnode=107.170.32.187:28333
addnode=107.170.37.13
addnode=107.170.40.168:28333
addnode=108.161.145.12:28333
addnode=162.243.118.47:28333
addnode=162.243.208.55
addnode=162.248.98.162
addnode=173.193.48.174
addnode=182.32.194.1
addnode=192.241.129.169
addnode=194.97.156.59:28333
addnode=195.47.113.76:28333
addnode=198.144.180.117
addnode=198.144.180.118
addnode=198.98.52.244:28333
addnode=213.239.207.114:28333
addnode=5.83.137.130:28333
addnode=5.83.137.131:28333
addnode=54.197.67.63
addnode=54.198.193.96:28333
addnode=54.204.214.12
addnode=54.234.17.173
addnode=54.237.23.244:28333
addnode=62.210.141.204:28333
addnode=64.79.107.5
addnode=67.225.172.77
addnode=76.102.71.50
addnode=77.172.93.38:28333
addnode=79.135.200.61
addnode=81.27.206.10:28333
addnode=95.138.166.108
addnode=95.138.166.126:28333
addnode=98.121.202.169