Topic: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record - page 265. (Read 685216 times)
February 11, 2014, 09:53:02 PM
Throw some cores on it anyway, you just may get lucky. I got a good feeling about this coin.
February 11, 2014, 09:50:07 PM
one quick question:
should i mine from the wallet or with rminerd?
should i mine from the wallet or with rminerd?
February 11, 2014, 09:48:02 PM
@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.Are you new to mining ? These are khash per thread.
Of course they don't vary with the number of threads ...
Yeah, while I don't think its evidence of any nefarious activity, I've been confused by this all evening.
If I use an insane amount of threads, my knumbers/s goes ridiculously high - with 1 thread per core, I'm at about 1m knumbers/s - with 64 threads per core, i get about 100m knumbers/s, but CPU utilization drops right off. Guessing its a buggy miner rather than a botnet though lmfao.
February 11, 2014, 09:46:01 PM
AVERAGE TIME TO BLOCK 481274.165898 seconds
Are you kidding me? That's like 5.5 days!
Are you kidding me? That's like 5.5 days!
chin up, I'm on 6.8 days
That's nothing! I got 16 days
wow...sucks
should i even bother?
honestly, I would say no.. in this case, "pool or nothing"
February 11, 2014, 09:44:05 PM
Thx guys for the nodes posted! i am now able to sync the wallet.
Cheers
Cheers
February 11, 2014, 09:43:19 PM
@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. Are you new to mining ? These are khash per thread.
Of course they don't vary with the number of threads ...
February 11, 2014, 09:42:29 PM
should i even bother?
February 11, 2014, 09:42:18 PM
AVERAGE TIME TO BLOCK 481274.165898 seconds
Are you kidding me? That's like 5.5 days!
Are you kidding me? That's like 5.5 days!
And blocks are still being generated waaay too fast... 14 in 5 minutes (should be 2)
Soon it will be 1 block / 30 days...
So either there is an insane amount of hashrate being thrown at this coin (around 200k threads), or someone has highly optimized miner.
February 11, 2014, 09:41:45 PM
AVERAGE TIME TO BLOCK 481274.165898 seconds
Are you kidding me? That's like 5.5 days!
Are you kidding me? That's like 5.5 days!
chin up, I'm on 6.8 days
That's nothing! I got 16 days
February 11, 2014, 09:40:45 PM
Getting errors. Help?
[2014-02-11 18:38:29] allocated space for 49965 primes in table
[2014-02-11 18:38:29] using 43390 primes, largest prime in table is 524287
[2014-02-11 18:38:29] 4 miner threads started, using 'primesr' algorithm.
[2014-02-11 18:38:29] HTTP request failed: Empty reply from server
[2014-02-11 18:38:29] json_rpc_call failed, retry after 30 seconds
[2014-02-11 18:38:59] HTTP request failed: Recv failure: Connection was reset
[2014-02-11 18:38:59] json_rpc_call failed, retry after 30 seconds
[2014-02-11 18:39:29] HTTP request failed: Recv failure: Connection was reset
[2014-02-11 18:39:29] json_rpc_call failed, retry after 30 seconds
[2014-02-11 18:38:29] allocated space for 49965 primes in table
[2014-02-11 18:38:29] using 43390 primes, largest prime in table is 524287
[2014-02-11 18:38:29] 4 miner threads started, using 'primesr' algorithm.
[2014-02-11 18:38:29] HTTP request failed: Empty reply from server
[2014-02-11 18:38:29] json_rpc_call failed, retry after 30 seconds
[2014-02-11 18:38:59] HTTP request failed: Recv failure: Connection was reset
[2014-02-11 18:38:59] json_rpc_call failed, retry after 30 seconds
[2014-02-11 18:39:29] HTTP request failed: Recv failure: Connection was reset
[2014-02-11 18:39:29] json_rpc_call failed, retry after 30 seconds
February 11, 2014, 09:38:45 PM
AVERAGE TIME TO BLOCK 481274.165898 seconds
Are you kidding me? That's like 5.5 days!
Are you kidding me? That's like 5.5 days!
chin up, I'm on 6.8 days
February 11, 2014, 09:38:42 PM
can anyone post some nodes? i get no block source available message on the win wallet
i have those. not sure if those are legit.
addnode=67.225.172.77
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=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
February 11, 2014, 09:38:37 PM
Updated nodes list worked super fast for me
addnode=62.210.208.8
addnode=54.83.5.13
addnode=209.126.75.75
addnode=188.226.144.147
addnode=194.97.156.49
addnode=76.102.71.51
addnode=79.135.200.21
addnode=162.248.98.152
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=188.165.216.59
addnode=194.97.156.59
addnode=162.218.208.166
addnode=5.83.137.131
addnode=89.182.2.122
addnode=62.210.208.8
addnode=54.83.5.13
addnode=209.126.75.75
addnode=188.226.144.147
addnode=194.97.156.49
addnode=76.102.71.51
addnode=79.135.200.21
addnode=162.248.98.152
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=188.165.216.59
addnode=194.97.156.59
addnode=162.218.208.166
addnode=5.83.137.131
addnode=89.182.2.122
February 11, 2014, 09:37:54 PM
can anyone post some nodes? i get no block source available message on the win wallet
February 11, 2014, 09:37:36 PM
Quote
Instructions for use for Win 7 please..thanks
https://www.dropbox.com/s/9vokz1vdwo0tdsg/riecoin.zipzip which includes 64bit miner, start.bat with 2 threads activated (edit for more), riecoin.conf and riecoin-qt
move riecoin.conf to your appdata/riecoin/ folder
start riecoin-qt, wait for synchronization, then run start.bat -> done!
Virustotal shows botnet positive for the miner though which is probably false positive
Donate RIC when you find any
! RSxLPaQCBfEhtiPEWCB26iHNtR4tmf4Ed7
Thank you!!!!
February 11, 2014, 09:37:05 PM
@BChydro
Are you new to mining ? These are khash per thread.
Of course they don't vary with the number of threads ...
edit :
Are you new to mining ? These are khash per thread.
Of course they don't vary with the number of threads ...
edit :
You're all idiots, the detached miner is clearly a botnet.
Proof --->> You can change the threads to anything from 1 to infinity and it will still report the same amount of knumbers/s per thread! It's just showing you bigger numbers than the built in miner so you think its better!
Damn you're really a troll. I shouldn't have bothered answering you ... Proof --->> You can change the threads to anything from 1 to infinity and it will still report the same amount of knumbers/s per thread! It's just showing you bigger numbers than the built in miner so you think its better!
February 11, 2014, 09:36:07 PM
AVERAGE TIME TO BLOCK 481274.165898 seconds
Are you kidding me? That's like 5.5 days!
Are you kidding me? That's like 5.5 days!
February 11, 2014, 09:35:33 PM
You're all idiots, the detached miner is clearly a botnet.
Proof --->> You can change the threads to anything from 1 to infinity and it will still report the same amount of knumbers/s per thread! It's just showing you bigger numbers than the built in miner so you think its better!
Proof --->> You can change the threads to anything from 1 to infinity and it will still report the same amount of knumbers/s per thread! It's just showing you bigger numbers than the built in miner so you think its better!
On what piece of crap did u generate that "proof" ? It's not true for my i7.
And how come I just found a block with that miner?
http://sourceforge.net/projects/riecoin/files/cpuminer%20rminerd%203.0.0/rminerd_win64.zip/download
Can anyone explain this?
Threads too high?
February 11, 2014, 09:31:34 PM
People shouting virus just want you to stop mining so they have more of a chance at getting coins.
If you have doubts, run on an isolated machine or compile from source. The diffs on github show this is clean.
If you have doubts, run on an isolated machine or compile from source. The diffs on github show this is clean.
February 11, 2014, 09:28:05 PM
You're all idiots, the detached miner is clearly a botnet.
Proof --->> You can change the threads to anything from 1 to infinity and it will still report the same amount of knumbers/s per thread! It's just showing you bigger numbers than the built in miner so you think its better!
Proof --->> You can change the threads to anything from 1 to infinity and it will still report the same amount of knumbers/s per thread! It's just showing you bigger numbers than the built in miner so you think its better!
On what piece of crap did u generate that "proof" ? It's not true for my i7.
And how come I just found a block with that miner?
http://sourceforge.net/projects/riecoin/files/cpuminer%20rminerd%203.0.0/rminerd_win64.zip/download
32 threads
1024 threads
Can anyone explain this?
Jump to: