Bitcoin Forum
April 26, 2019, 03:05:46 PM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 [265] 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 »
  Print  
Author Topic: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record  (Read 660488 times)
cbuchner1
Hero Member
*****
Offline Offline

Activity: 756
Merit: 500


View Profile
December 22, 2017, 04:00:34 PM
 #5281

But it's usually the case that following the money is the path. Smiley

So... have you actually tried to follow the money? You know, for science.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1556291146
Hero Member
*
Offline Offline

Posts: 1556291146

View Profile Personal Message (Offline)

Ignore
1556291146
Reply with quote  #2

1556291146
Report to moderator
dga
Hero Member
*****
Offline Offline

Activity: 737
Merit: 511


View Profile WWW
December 22, 2017, 04:36:47 PM
 #5282

But it's usually the case that following the money is the path. Smiley

So... have you actually tried to follow the money? You know, for science.


I traced some of the major solo addresses that showed up around the DDoS start to their Poloniex deposit addresses and reported them to a contact in law enforcement to see if there were any leads they could follow up on.  Haven't heard back, but I wouldn't expect to.  I posted about the analysis about six months ago. 

ziiip
Full Member
***
Offline Offline

Activity: 249
Merit: 101

uBlock.it Admin


View Profile WWW
December 28, 2017, 01:33:53 AM
Last edit: December 29, 2017, 03:21:26 AM by ziiip
 #5283

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

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

Riecoin Pool http://uBlock.it/
rammy2k2
Legendary
*
Offline Offline

Activity: 1554
Merit: 1002


Free Crypto in Stake.com Telegram t.me/StakeCasino


View Profile
January 03, 2018, 01:31:00 AM
 #5284

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

Pon13
Full Member
***
Offline Offline

Activity: 573
Merit: 123



View Profile WWW
January 03, 2018, 07:21:56 AM
 #5285

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

In Bill Hicks we trust....
Robin37s
Member
**
Offline Offline

Activity: 124
Merit: 10


View Profile
January 03, 2018, 09:10:09 AM
 #5286

it seems that the accumulation of ric is insane on poloniex and waiting for its halving.
~Money~
Hero Member
*****
Offline Offline

Activity: 1001
Merit: 515


View Profile
January 03, 2018, 05:30:35 PM
 #5287

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

FREE for a while ...
dga
Hero Member
*****
Offline Offline

Activity: 737
Merit: 511


View Profile WWW
January 03, 2018, 06:29:46 PM
 #5288

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
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile WWW
January 05, 2018, 05:57:12 AM
Last edit: January 05, 2018, 06:43:27 AM by simba841
 #5289

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

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.  Roll Eyes

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!
Bitmenbcn
Newbie
*
Offline Offline

Activity: 68
Merit: 0


View Profile
January 05, 2018, 01:54:42 PM
 #5290

Why are deposits and withdrawals disabled in Poloniex? What is the problem with the network?
dga
Hero Member
*****
Offline Offline

Activity: 737
Merit: 511


View Profile WWW
January 05, 2018, 01:56:25 PM
 #5291

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

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.  Roll Eyes

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
Hero Member
*****
Offline Offline

Activity: 737
Merit: 511


View Profile WWW
January 05, 2018, 02:00:37 PM
 #5292

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:

Quote
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
Hero Member
*****
Offline Offline

Activity: 737
Merit: 511


View Profile WWW
January 05, 2018, 03:41:00 PM
 #5293

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:

Quote
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
Jr. Member
*
Offline Offline

Activity: 66
Merit: 3


View Profile
January 05, 2018, 04:33:31 PM
 #5294

I have set up two nodes hosted on OVH

176.31.136.231
176.31.210.206
dga
Hero Member
*****
Offline Offline

Activity: 737
Merit: 511


View Profile WWW
January 05, 2018, 06:06:58 PM
 #5295

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
Hero Member
*****
Offline Offline

Activity: 737
Merit: 511


View Profile WWW
January 05, 2018, 07:09:03 PM
 #5296

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
Jr. Member
*
Offline Offline

Activity: 66
Merit: 3


View Profile
January 05, 2018, 07:28:31 PM
 #5297

How often do these forks happen?
dga
Hero Member
*****
Offline Offline

Activity: 737
Merit: 511


View Profile WWW
January 05, 2018, 08:09:15 PM
 #5298

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
Hero Member
*****
Offline Offline

Activity: 737
Merit: 511


View Profile WWW
January 06, 2018, 01:13:03 AM
 #5299

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
Hero Member
*****
Offline Offline

Activity: 737
Merit: 511


View Profile WWW
January 06, 2018, 02:02:57 PM
 #5300

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. Smiley

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.

Pages: « 1 ... 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 [265] 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!