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

Hey guys,
Recently I found this project and it looks very interesting. But I have a issue with wallet - what do you suggest to use?
I tried the one on website - looks like it is not updating the blockchain...
Then I tried one web based wallet (https://cryptap.us/ric/jswallet/) - transferred 3 RIC from pool I'm mining to to that address and the coins are nowhere to be found after that...
Any suggestion where to keep my coins?

Thanks,
keep up the good work.

Hey guys,
Recently I found this project and it looks very interesting. But I have a issue with wallet - what do you suggest to use?
I tried the one on website - looks like it is not updating the blockchain...
Then I tried one web based wallet (https://cryptap.us/ric/jswallet/) - transferred 3 RIC from pool I'm mining to to that address and the coins are nowhere to be found after that...
Any suggestion where to keep my coins?

Thanks,
keep up the good work.

I'm not too sure how it works but doesn't the difficulty adjustment only factor in the last 288 blocks only?

For example if the adjustment just happened and we lost 90% hash rate then it would take 10X as long to mine the next 288 block but after that it would adjust to the current hash of 90% loss and block will be 2.5 minutes again?

How could it be this off?

Block 840000.  We're currently at 811091.  

840000 - 811091 = 28909.

Average block time is 2.5 minutes.  28909 * 2.5 / 60 / 24 = 50.18 days = March 8th.

That's slightly off from the original design projection (approximately Feb 11th).  I'm not sure if we've just had a slow period and it'll correct back to that, or if there's just a bit of slippage in the diff adjustment that will take longer to average out.

So -- definitely between Feb 11th and Mar 8.  I'd bet more towards the latter, but I'm not totally certain.

i'm really happy that despite the drama here and the constant attacks on both the network, the pools and here, the community stand strong.
this is indeed a sleeping giant.
i turned 5 cpus (from i3 to i7) more from nexus to riecoin at least until the halving.

Speaking of the halving, does anyone knows the exact date of the latter

i'm really happy that despite the drama here and the constant attacks on both the network, the pools and here, the community stand strong.
this is indeed a sleeping giant.
i turned 5 cpus (from i3 to i7) more from nexus to riecoin at least until the halving.

Speaking of the halving, does anyone knows the exact date of the latter

I remember following the launch of riecoin and even mined it in the first few weeks on ypool. I see things have changed up a little and there is not a private pool. I've contacted ziip and also messaged on the website but have not been able to get an invite. I'm currently mining on riepool and my stats are quite rubbish for an i7 running for 24 hours. I've 0.07 of a riecoin confirmed. Is there anyone that can provide an invite to the private pool?

Not very often recently, but I gather there were a lot of stability problems about a year and a half ago.  I was completely away from RIC for a while (sabbaticals are the best thing ever for academics... :-), so I wasn't really watching.  If you look back in the forum, though, you can probably find some discussions about crazy-high orphan rates when the network first started getting DDoS'd.  

Here's a fork reported in October 2017:  https://bitcointalk.org/index.php?topic=446703.msg23395787#msg23395787

Here's a discussion from 2015 about the DDoS attacks - https://bitcointalk.org/index.php?topic=446703.4080

That accusation (Xpoolx accusing Simba (RiePool.ovh) of the DDoS) is one of the ones I was referring to.

And here's a plot of the historical orphan rates (orphans are what happens when there's a race to complete the chain -- a fork is just when the race goes on for a longer time):

https://chainz.cryptoid.info/ric/orphans.dws

You can see that things got really bad in late 2016 until early 2017.  Some time around then is when several people started adding extra DDoS-protected nodes to the network to try to reduce the chaos.  The orphan rates calmed down, but there's been a new spike the last few days.  (Amusingly, the DDoS is why I started paying attention again, because whomever was doing it launched an attack strong enough it took all of Carnegie Mellon University offline -- I had left a Riecoin node running in my office for the last few years, completely forgotten about it, and then... un-forgot. :-)

Thanks but address not found

Here is a copy of the blockchain (with recent peers) if anyone has use for it.

http://176.31.136.231/Riecoin/Riecoin.zip - It will be updated every hour on the hour.

Wow still difficulty 1804? This one is taking forever!


Tried C:\Users\username\AppData\Roaming\Riecoin\riecoin.conf?