shall I stop mining the new version of miner? and go to B9 version?
what shall I do?
Topic: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record - page 190. (Read 685214 times)
March 21, 2014, 12:45:50 AM
March 21, 2014, 12:40:36 AM
The difficulty is going to crash if ypool doesn't start running again. 
Is that why I am getting a connection server error with dga's new miner?
Is there a new Minerd for solo mining?
Or is it possible to set up B10 for solo mining? If so then what settings
a00k's miner is good for solo mining. I believe it is as good as dga's B10 pool miner. B10 didn't improve on finding blocks, it only improved on finding shares.Or is it possible to set up B10 for solo mining? If so then what settings
Also: it's been 40 minutes since a block was found. No significant computing power is going towards solo mining. The only entity finding blocks currently is ric.upcpu.com. This needs to be fixed asap or no transactions will be confirmed
gatra: I think this shows we should reduce difficulty adjustment to 1 block.
March 21, 2014, 12:20:12 AM
The difficulty is going to crash if ypool doesn't start running again.
Is that why I am getting a connection server error with dga's new miner?
March 21, 2014, 12:18:56 AM
March 21, 2014, 12:16:13 AM
ypool is down right?
March 21, 2014, 12:09:52 AM
Is there a new Minerd for solo mining?
Or is it possible to set up B10 for solo mining? If so then what settings
Or is it possible to set up B10 for solo mining? If so then what settings
March 21, 2014, 12:02:31 AM
The difficulty is going to crash if ypool doesn't start running again.
March 20, 2014, 10:40:26 PM
I don't see a memory leak on my Linux machines (equivalent of CentOS 6.4). On my 4GB machines it is using about 68% of the memory, on my machines with > 32GB it is using about 15%. I running the raw binary, not rebuilding.
Unfortunately ypool seems stuck on block 23373
Unfortunately ypool seems stuck on block 23373
March 20, 2014, 10:08:23 PM
Binary releases:
http://www.cs.cmu.edu/~dga/crypto/ric/
http://www.cs.cmu.edu/~dga/crypto/ric/
First of all, thank you for the great work on the miner. I was using b8 for a few days and it worked nicely.
b10 however has a huge memory leak it get killed by the os pretty instantly. Can you fix your build?
Also tried building b10 out of the source you provided. But the build fails as well with
Code:
xptMiner/main.cpp:7:18: error: atomic: No such file or directory
It is currently 4am and I haven't investigated anything yet ... my guess is that my standard CentOS gmp version is too old.UPDATE1: Bizarrely enough b10 works on some machines but not on others. The machine will the most memory 32 GB crashes within 3 seconds, so does a VM with 1 GB. But one with 8GB works fine! any advice?
UPDATE2: The build still fails with a missing atomic include, despite the GMP upgrade.
All the best!
one4many
March 20, 2014, 08:42:41 PM
Thanks for the tip about b10's behavior being normal, switching back to it.
March 20, 2014, 08:30:07 PM
Agreed. In my experience, B10 is shaky at first, but then settles down after the first 10 shares or so and is significantly faster than B9 thereafter.
March 20, 2014, 08:25:44 PM
You should mine with b10 for sure. It is at least 10 times faster at finding shares. Even if the beginning ones are rejected (that issue happens to everyone).
March 20, 2014, 08:00:42 PM
Had to go back to sse4 b9 from b10
On all my Linux machines I started getting lots and lots of invalid shares, mostly of this type:
[00:05:37] Share found! (Blockheight: 23302)
Invalid share
Reason: Share double submission or work unknown
[00:05:42] Share found! (Blockheight: 23302)
Invalid share
Reason: Share double submission or work unknown
Also a few like this:
[00:01:41] Share found! (Blockheight: 23302)
Invalid share
Reason: Merkleroot is invalid or corrupted. Update your miner.
All is well once I went back to sse4 b9
These are a variety of Linux boxes with Xeon processors, no issues with previous software releases
On all my Linux machines I started getting lots and lots of invalid shares, mostly of this type:
[00:05:37] Share found! (Blockheight: 23302)
Invalid share
Reason: Share double submission or work unknown
[00:05:42] Share found! (Blockheight: 23302)
Invalid share
Reason: Share double submission or work unknown
Also a few like this:
[00:01:41] Share found! (Blockheight: 23302)
Invalid share
Reason: Merkleroot is invalid or corrupted. Update your miner.
All is well once I went back to sse4 b9
These are a variety of Linux boxes with Xeon processors, no issues with previous software releases
March 20, 2014, 07:02:59 PM
Hi, all -
As promised, with ypool's update to address the share-vs-block
fairness issue, I'm releasing as open source my miner code.
I've also placed online binaries with the usual dev fee structure:
2% default, which can be disabled from the command line.
Thanks to everyone who supported this with dev fees over the last
few days. I've taken the time to clean up the code modestly -
it still needs work, but it's not the total mess it was yesterday.
I've integrated the windows/mingw build into the main line and
added -s parameter on the command line to replace
the former set of multiple builds.
Binary releases:
http://www.cs.cmu.edu/~dga/crypto/ric/
Source release:
https://github.com/dave-andersen/fastrie
(in the xptMiner subdirectory)
Note: If you're running any other miner, it's important to
upgrade to this one ASAP in order to ensure that you're getting
a fair share of the blocks you find! The change from "first four"
to "any four" means that the miners will all be finding MANY more
shares per block -- so if you're running old code, you will be at
a serious disadvantage. Something like 30 to 1. Upgrade ASAP.
The miner will report a different number of chains/sec than it
did before because of the change to shares, but it's roughly the
same code as before - maybe 1% or less slower because of testing
for multiple primes.
Happy mining, and thanks as always to Gatra for creating a great
proof of work, to jh and clintar for the starting codebase,
and to everyone for participating in it.
Note also that jh is releasing a new miner - compare and find the best
one, I don't know which one is faster.
As promised, with ypool's update to address the share-vs-block
fairness issue, I'm releasing as open source my miner code.
I've also placed online binaries with the usual dev fee structure:
2% default, which can be disabled from the command line.
Thanks to everyone who supported this with dev fees over the last
few days. I've taken the time to clean up the code modestly -
it still needs work, but it's not the total mess it was yesterday.
I've integrated the windows/mingw build into the main line and
added -s
the former set of multiple builds.
Binary releases:
http://www.cs.cmu.edu/~dga/crypto/ric/
Source release:
https://github.com/dave-andersen/fastrie
(in the xptMiner subdirectory)
Note: If you're running any other miner, it's important to
upgrade to this one ASAP in order to ensure that you're getting
a fair share of the blocks you find! The change from "first four"
to "any four" means that the miners will all be finding MANY more
shares per block -- so if you're running old code, you will be at
a serious disadvantage. Something like 30 to 1. Upgrade ASAP.
The miner will report a different number of chains/sec than it
did before because of the change to shares, but it's roughly the
same code as before - maybe 1% or less slower because of testing
for multiple primes.
Happy mining, and thanks as always to Gatra for creating a great
proof of work, to jh and clintar for the starting codebase,
and to everyone for participating in it.
Note also that jh is releasing a new miner - compare and find the best
one, I don't know which one is faster.
Any chance of 32 bit miners, windows and linux?
I'm currently GPU mining scrypt under a windows 32 system and would love to mine RIC alongside. Don't have too much faith on being able to compile for linux either when I finally reboot.
March 20, 2014, 06:26:15 PM
Wow..great progress we are making.
March 20, 2014, 05:50:52 PM
now time to work on stratum miner? 
March 20, 2014, 05:49:16 PM
Hi, all -
As promised, with ypool's update to address the share-vs-block
fairness issue, I'm releasing as open source my miner code.
I've also placed online binaries with the usual dev fee structure:
2% default, which can be disabled from the command line.
Thanks to everyone who supported this with dev fees over the last
few days. I've taken the time to clean up the code modestly -
it still needs work, but it's not the total mess it was yesterday.
I've integrated the windows/mingw build into the main line and
added -s parameter on the command line to replace
the former set of multiple builds.
Binary releases:
http://www.cs.cmu.edu/~dga/crypto/ric/
Source release:
https://github.com/dave-andersen/fastrie
(in the xptMiner subdirectory)
Note: If you're running any other miner, it's important to
upgrade to this one ASAP in order to ensure that you're getting
a fair share of the blocks you find! The change from "first four"
to "any four" means that the miners will all be finding MANY more
shares per block -- so if you're running old code, you will be at
a serious disadvantage. Something like 30 to 1. Upgrade ASAP.
The miner will report a different number of chains/sec than it
did before because of the change to shares, but it's roughly the
same code as before - maybe 1% or less slower because of testing
for multiple primes.
Happy mining, and thanks as always to Gatra for creating a great
proof of work, to jh and clintar for the starting codebase,
and to everyone for participating in it.
Note also that jh is releasing a new miner - compare and find the best
one, I don't know which one is faster.
As promised, with ypool's update to address the share-vs-block
fairness issue, I'm releasing as open source my miner code.
I've also placed online binaries with the usual dev fee structure:
2% default, which can be disabled from the command line.
Thanks to everyone who supported this with dev fees over the last
few days. I've taken the time to clean up the code modestly -
it still needs work, but it's not the total mess it was yesterday.
I've integrated the windows/mingw build into the main line and
added -s
the former set of multiple builds.
Binary releases:
http://www.cs.cmu.edu/~dga/crypto/ric/
Source release:
https://github.com/dave-andersen/fastrie
(in the xptMiner subdirectory)
Note: If you're running any other miner, it's important to
upgrade to this one ASAP in order to ensure that you're getting
a fair share of the blocks you find! The change from "first four"
to "any four" means that the miners will all be finding MANY more
shares per block -- so if you're running old code, you will be at
a serious disadvantage. Something like 30 to 1. Upgrade ASAP.
The miner will report a different number of chains/sec than it
did before because of the change to shares, but it's roughly the
same code as before - maybe 1% or less slower because of testing
for multiple primes.
Happy mining, and thanks as always to Gatra for creating a great
proof of work, to jh and clintar for the starting codebase,
and to everyone for participating in it.
Note also that jh is releasing a new miner - compare and find the best
one, I don't know which one is faster.
March 20, 2014, 05:04:08 PM
new status update posted
https://bitcointalksearch.org/topic/ric-riecoin-status-update-20140320-524095
also here: http://riecointalk.com/index.php/topic,177.0.html
please let me know if I missed something!
https://bitcointalksearch.org/topic/ric-riecoin-status-update-20140320-524095
also here: http://riecointalk.com/index.php/topic,177.0.html
please let me know if I missed something!
Excellent! Thanks Gatra
March 20, 2014, 04:56:51 PM
new status update posted
https://bitcointalksearch.org/topic/ric-riecoin-status-update-20140320-524095
also here: http://riecointalk.com/index.php/topic,177.0.html
please let me know if I missed something!
https://bitcointalksearch.org/topic/ric-riecoin-status-update-20140320-524095
also here: http://riecointalk.com/index.php/topic,177.0.html
please let me know if I missed something!
March 20, 2014, 04:22:29 PM
As expected..price dropped. No worries 
Jump to: