[ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record

[rammy2k2]

i cant sync my wallet, no block connections .... any idea?

[1713262767]

1713262767

[1713262767]

1713262767

[Pon13]

i cant sync my wallet, no block connections .... any idea?

did you add some nodes to the conf file like the following below??

Code:

connect=51.255.207.142
connect=37.59.143.10
connect=217.182.76.201
connect=46.105.29.136
connect=5.9.39.9

[Robin37s]

it seems that the accumulation of ric is insane on poloniex and waiting for its halving.

[~Money~]

did you add some nodes to the conf file like the following below??

Code:

connect=51.255.207.142
connect=37.59.143.10
connect=217.182.76.201
connect=46.105.29.136
connect=5.9.39.9

i think using addnode will be better option here, correct me if im wrong, your commands will limit wallet to connect those nods only :-?

Code:

addnode=51.255.207.142
addnode=37.59.143.10
addnode=217.182.76.201
addnode=46.105.29.136
addnode=5.9.39.9

[dga]

did you add some nodes to the conf file like the following below??

Code:

connect=51.255.207.142
connect=37.59.143.10
connect=217.182.76.201
connect=46.105.29.136
connect=5.9.39.9

i think using addnode will be better option here, correct me if im wrong, your commands will limit wallet to connect those nods only :-?

Code:

addnode=51.255.207.142
addnode=37.59.143.10
addnode=217.182.76.201
addnode=46.105.29.136
addnode=5.9.39.9

People often use connect= so they don't get connected to whatever nodes trigger the huge DDoS floods.

As an unrelated aside:  XpoolX, your clock seems to be ahead.  The block explorer shows things like 5 min, 12 min, 6 min, 18 min... where the 6 minute old block (in block sequence, but out of time order) is an XpoolX block.  I don't think this matters in any serious way, but you might want to fix it before it gets so out of sync your blocks start getting rejected.

[simba841]

uBlock.it is running much better now. Attack is now being successfully mitigated.  

Apologies for the issues over the last week.
Happy mining.

ublock, like all those who do NOT mining under "All Others" will have major problems of orphanage, if that SOLO miner does not decide to do things properly.

Needless to lash out at RiePool without ever having any kind of evidence of what was claimed.  

The problems here are very different!

for ziiip, dga and other "idiots": I advise you to stop with your ridicolous and unfounded accusations. We have already begun to take action, if you continue we will go ahead even outside the forum... Please STOP!

[dga]

uBlock.it is running much better now. Attack is now being successfully mitigated.  

Apologies for the issues over the last week.
Happy mining.

ublock, like all those who do NOT mining under "All Others" will have major problems of orphanage, if that SOLO miner does not decide to do things properly.

Needless to lash out at RiePool without ever having any kind of evidence of what was claimed.  

The problems here are very different!

for ziiip, dga and other "idiots": I advise you to stop with your ridicolous and unfounded accusations. We have already begun to take action, if you continue we will go ahead even outside the forum... Please STOP!

I don't believe I've insulted you, so perhaps you would return the courtesy.  Nor did I accuse you, though I did mention that others have -- you'll note that I specifically said I don't know whether any of it is true.  And -- seriously, are you making threats?  Please act like an adult.  This is a geeky, prime number coin.  With the blocks per day you're mining on Riepool, it can't be worth any real money to you.  Unless, of course, you *are* in collusion with the botnet(s) that are mining most of the coins, in which case, I can understand why you'd be so upset about all of this.  But otherwise, your anger seems strangely out of proportion to the stakes involved.

In regards to this fork/orphan thing -- the last time I think it was because one of my public nodes got messed up, but it's been up and stable this time.  I'm happy to set up another DDoS-shielded node to try to help stabilize things.

Has anyone tested whether OVH's nodes are safe for Riecoin nodes?

  -Dave

[dga]

Why are deposits and withdrawals disabled in Poloniex? What is the problem with the network?

There was a 54 block fork.  It's resolved, but the wallets "pause" for 72 blocks after the fork to make sure things are stable:

2018-01-05 13:51:49 CheckForkWarningConditions: Warning: Large valid fork found
  forking the chain at height 808994 (b4fbef816d27ac56d5e4a2dc6c156612acbf5ce293968a5e98e3c2ffeea4082f)
  lasting to height 809048 (c1168dadb615f49f7ef2648b0d6b7bb07b9dfad4d1fb98a6c8a8475c82525429).

Polo and other places should be operational again by block 809120, which is 29 blocks from now.  Approximately 29 * 2.5 = 72 minutes from now.

[dga]

Why are deposits and withdrawals disabled in Poloniex? What is the problem with the network?

There was a 54 block fork.  It's resolved, but the wallets "pause" for 72 blocks after the fork to make sure things are stable:

2018-01-05 13:51:49 CheckForkWarningConditions: Warning: Large valid fork found
  forking the chain at height 808994 (b4fbef816d27ac56d5e4a2dc6c156612acbf5ce293968a5e98e3c2ffeea4082f)
  lasting to height 809048 (c1168dadb615f49f7ef2648b0d6b7bb07b9dfad4d1fb98a6c8a8475c82525429).

Polo and other places should be operational again by block 809120, which is 29 blocks from now.  Approximately 29 * 2.5 = 72 minutes from now.

Network appears stable.  Block explorer shows happy, and my wallet has stopped warning about the fork.  Don't know how long Poloniex waits.  But all appears happy.

I'll try to get another well-connected public node up in the next few days.  sigh.

[MasterQ]

I have set up two nodes hosted on OVH

176.31.136.231
176.31.210.206

[dga]

I have set up two nodes hosted on OVH

176.31.136.231
176.31.210.206

Fantastic - thank you!

Just as a heads-up, my Frantech node just got hit by something that took it offline for a minute or two (or had a hardware glitch).  Investigating, but I suspect this means the DDoS remains alive.

Expect attacks such as very large numbers of connections from many nodes to try to exhaust your numconnections= limit, bandwidth exhaustion attacks, TCP synfloods, and attempts to get your node to initiate outbound traffic.

Also, someone seems to be trying to attack the network right now with massive numbers of transactions.  They're not doing anything, but they'll use a bit more CPU and bandwidth than you may have thought you'd normally need.  This started at about block 809154 (about two hours ago).

[dga]

Wow why would someone do that just to bloat the blockchain...
At least this stupid person is paying some transactions fees...

Miners should temporarily refuse any transactions below 0.001 RIC to mitigate this

Unsure.  But we seem to have had another fork.  Not sure if it's related to that or not -- high tx volume affecting block propagation times?  Seems unlikely at 200k unless some of the nodes are already slow because of DDoS.

This one wasn't as bad as the previous, but it'll still be 72 blocks before the wallets come out of warning mode.  About 3 hours.

[MasterQ]

How often do these forks happen?

[dga]

How often do these forks happen?

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. :-)

[dga]

Someone seems to play with the difficulty too: since the last difficulty change, a block was found in less than 95 sec instead of 150 on average!
This person might have huge computing power and could mine a huge number of blocks when the difficulty is low, driving the difficulty way up while extracting easy blocks, and then stop mining and let others mine at a much higher difficulty, then mine again when the difficulty is lowered and continue the cycle

That's probably from the fork - if the network was cut in half, then half the mining output during the fork got thrown away (in practice, it won't be that much, because there's no reason for exactly half to be on each part).  So the diff drop will overcompensate this time, and then it'll bounce pretty high next time, and then start settling back down to normal for the amount of mining power that's out there.

[dga]

Someone seems to play with the difficulty too: since the last difficulty change, a block was found in less than 95 sec instead of 150 on average!
This person might have huge computing power and could mine a huge number of blocks when the difficulty is low, driving the difficulty way up while extracting easy blocks, and then stop mining and let others mine at a much higher difficulty, then mine again when the difficulty is lowered and continue the cycle

That's probably from the fork - if the network was cut in half, then half the mining output during the fork got thrown away (in practice, it won't be that much, because there's no reason for exactly half to be on each part).  So the diff drop will overcompensate this time, and then it'll bounce pretty high next time, and then start settling back down to normal for the amount of mining power that's out there.

But didn't the fork and its consequences already stop? I don't think that many miners are still mining for a wrong blockchain
The difficulty increased to an all time high of 1804 (except super blocks) and now the average block find time is about 330 sec (more than 5 minutes)!
And the hashrate distribution of "All others" here for the last 100 blocks is only 8 %, but is 71.7 % for the last 1000 blocks! I don't think that this drop is a consequence of the fork
I would think that a miner with huge computing resources stopped mining right after the difficulty rise, and will not be surprised if this person/organization resumes mining when the difficulty decreases again

I think we're both right.

The fork caused the diff drop, by making it seem as if the hashrate was actually only about 60% of what it was.

The diff dropped too low for the real hashrate, so after the fork healed, the hashrate was huge for the diff.  That caused the diff spike.

And with the diff spike, some huge miner(s?) dropped out.

And you're right - this is the kind of diff swing that newer diff salgorithms like DGW were designed to prevent.  Let's hope it settles down for now.

[crisdo98]

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?

[MasterQ]

Hopefully Riecoin development gets picked up again. It's a really neat coin IMO, anything that has real world value from POW is good.

The two nodes I set up have experienced multiple DDOS attacks in the last 24 hours but OVH eating them up with ease! BRING IT ON

176.31.136.231
176.31.210.206

[crisdo98]

I feel quite daft asking but how do I get my wallet to start syncing to the network?

I've tried running the command addnod "nodeIP" "add" as per the node list at this address https://chainz.cryptoid.info/ric/#!network

I also grabbed some of the IPs in the previous page and used the command above. I noted that people mention a config file. I'm using windows and cannot see any such file in APPDATA or Program Files.

Help much appreciated.

[crisdo98]

Wow still difficulty 1804? This one is taking forever!

I feel quite daft asking but how do I get my wallet to start syncing to the network?

I've tried running the command addnod "nodeIP" "add" as per the node list at this address https://chainz.cryptoid.info/ric/#!network

I also grabbed some of the IPs in the previous page and used the command above. I noted that people mention a config file. I'm using windows and cannot see any such file in APPDATA or Program Files.

Help much appreciated.

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

Magician! Thanks! The conf file didn't exist but I just had to create it with the nodelist from cryptoid, restarted and it's now syncing. Any idea how much disk space this will take up as I may need to move it to an external drive?