Topic: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record - page 184. (Read 685214 times)

2 or 3 a day and what are they worth a coin?

Im holding long term. I hope it gets to, if not surpassed, Primecoin because I think it is better than Primecoin (personal opinion). I think you can get maybe 2-3 RIC a day?

Hey guys i'm new and am going to start mining tonight. How many coins should i make with my home pc? i get about 20KHS about 200 ebt a day. My RIC add  RWyTCa4xHyTz6hkzQAyFLa2KnqSeWp4U67 .

This is a very innovative sounding coin. Can anyone give any pointers and time to hold? what kind of price do u all hope to get out of this?

+1

Why price riecoin down 

Dropping? The price has been around .2 for about a week...

I guess it's a good time to buy...

Still working on cpuminers and on new client version. I want to include all changes from bitcoin 0.9.0 plus continuous difficulty adjustments, but I have to be very carefull no to mess up anything.

I think this would be a nice time to update dev. When prices are still dropping.

I think this would be a nice time to update dev. When prices are still dropping.

Memory usage is related to the sieve size (-s), and by the amount of cores your CPU has, or threads you use. Default sieve size is -s 500000000. If you find it is using too much memory, or freezes or crashes upon running the program, just decrease the sieve amount to a lower size. If you have more memory you might want to increase it, it may help performance. For reference i'm using -s 675000000 for the 8 core i7, which uses about 6.5 GB of RAM. On other systems with 4 core i5's i can use -s 900000000 which uses about 6 GB.


https://www.cs.cmu.edu/~dga/crypto/ric/readme.html

The ypool chat room was full of people noticing that b12 slowed down too much, so I've pushed b13 as a compromise between safety and speed.  But it also includes an important bug fix (which should be masked by the other one, but fixing bugs is good).

 http://www.cs.cmu.edu/~dga/crypto/ric/
and in github:
 https://github.com/dave-andersen/fastrie/

Also, there's now a ChangeLog that covers all of this stuff:  https://github.com/dave-andersen/fastrie/blob/master/ChangeLog

It may be slightly slower than b11 when a block takes a long time, but it's not too far off.  It might even be a little faster for fast blocks, but overall, it's probably 5% slower than b11, but it won't get into the "invalid prime" problem.

There were two bugs in b11:
  - If it went too long before a new block was found, it could overflow the 256 bit riecoin nonce field -- I changed some constants and didn't re-do the math on them.  This is now computed based upon those constants, so the bug shouldn't reappear.

  - It could run for too long without updating its block time field, which would cause ypool to reject it even if it contained a valid share or block.  I've mostly kinda sorta fixed this, but the current version reflects a compromise between safety (updating the time field frequently) and efficiency (running as long as possible after computing a target).  This one's a "let's run it and see how it does" kind of thing.

For people who like to read the source of these things, the internals have gotten a little cleaner, which hopefully makes the logic a bit more clear.  In particular, I think the offset computation should be easier to read and understand now, for those seeking to understand what makes these miners tick.

  -Dave