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

it's just an idea... I wanted to see how people felt about it....
I think we would set 1RIC = 1RIC² during the transition phase. (or maybe 1RIC = 1.2RIC² in order to favor RIC, we'll have to think about it carefully)
and you would choose if you move your coins to RIC² or stay in RIC. PoW and mining would work the same... we could even have merged mining... I wouldn't abandon RIC.

anon tx is getting attention, I agree that most attempts won't hold water, but the ring signature approach is the only one I believe that can actually work (at least the theory is sound, I haven't really verified current implementations).

maybe we could add ring signature support and do the 512 bit nonces and the 5 mins per block things as a hard fork in RIC instead of making a new coin... but that's more work...   if we like the RIC² name we could do the hard fork and rename RIC to RIC² and have nice new features without a new coin

Yea. I agree. Why make a new coin when a perfectly good coin already exist and needs improvement?

the longer numbers and block time are a great idea, not sure i would favor a riecoin 2 , I am still trying to research methods to mine riecoin

Also I am unconvinced that features of anon tx will hold water

Most that claim it are false now.

Obviously a good area for future research....


would be better to make your choice if you could check out that gpu miner on testnet of primecoin vs. see a demo

i do agree future technology will continue to increase what are the present limits of hardware ect...

Hm..What about all  the current RIC holders? How would transitioning it work? 1RIC=1RIC2?

I like Ric²

But right know I don't know how to make it more RAM demanding... (that is, without radically changing the PoW). After seeing the alleged speed of primecoin's gpu miner, I think that a Ric gpu miner will eventually be unavoidable. Newer GPUs will keep getting more and faster RAM anyway.

I was thinking of making the nonce (offset in the block's header) be 512 bits long instead of 256. This would allow for more efficient mining putting us closer to the elusive world record.

Also 5 mins per block: the wallet would sync faster and each block would have more difficulty, getting us closer to that record....

+1

...and add RAM requirements (shinycoin) to make it a truly a CPU-only coin.

if so then please write it like Ric² 

Hi! I've been a little sick  (just a flu) and I didn't touch a keyboard in like 4 days (!) that's weird for me... anyway, I'm still working but I didn't make much progress lately.


One idea I've been fantasizing about: we could make Riecoin2, based on the new ring signature anonymous coins (Monero/Bytecoin). It would be a fork of their code but using out PoW. There should be a way to transition from RIC to RIC2. Maybe we could have a burn period where we would burn RIC to transform them into RIC2, or I could just premine a lot of RIC2, sell them for at 1 RIC on an exchange and after a while just burn the unsold ones. The latter would be easier than monitoring both chains.

What do you think? those who don't like it would be allowed to continue in the current RIC, and the fact that you would be able to use it to buy RIC2 at a fixed price (for a while) would make the price (of RIC) go up. Or would it hold RIC2 down? who knows....

I have been reading the last few pages, and I just want to say, I won't abandon this coin too.  I may not be as active speaking but thats just busy summer life, but mining I still go!

Any update this week Gatra?

wow I saw 1 block mined in p2pool, is it ready?

i guess i could check on my own, do the block crawlers show many 'unredeemed outputs' of mined blocks ?

i bet not

the 'rich' list blew my mind,

Probably either poloniex or yPool

New feature to the explorer: Largest Wallets!

It's a rich list with addresses aggregated by guesstimated wallets.

Any idea who is the exchange with the #1 wallet?
(if you spot your deposit address in there, you'll know)

please please let e5 2670 config. e5 2670 and run many different ric / day?
thank

Fyi i continue to support Riecoin and if my comments above were taken I was 'abandoning' it that is not so.

I am however not going to mine if with the best hardware I have access to right now tells me it may be 75+ days on average to hit a block and difficulty is lower now that it has been.  I currently support or pay a lot of attention to very few coins other than the major accepted coins that hve been around a long time and a few that I am involved in development of myself, Riecoin is one of the few.....

For me (personally due to what I own to mine with or cloud resources I have available)  it is stoping mining 'for now' only until other alternatives are available. I never said I was dumping the Riecoin I own or would not purchase it if what I deem reasonable prices come to the market. 

When I have time, in between my own projects, i will see if I can get some type of pool code to work that would be open source and even if it is not working with the fastest miner available and I am no expert in pooled mining development it is on my list of things to give a shot to.

To the poster above who said he had solo mining working or partially developed, please put your work on github , give us a link and let everyone (including the experts here) take a look vs. a pm.  Code talks ....

I've got a solo mining proxy adapting XPT protocol. I posted it in May and seems  no one is interested....sigh.

If you're interested, PM me.

I will never abandon this coin. I chose this coin because of its potential. Good news is that I will be finish with work by the end of next week and can focus mostly on Riecoin

good coin looking so far
will watch this coin develop for a while 

Can I currently mine this coin with an AMD 8150 8 core 3.6 ghz processor, or better question.......will it be worth my time with this processor?

If so, what is best way to do and how?  I see the optimized CPU miner listed in the OP but did not see any instructions on setup.

Thanks!