Under Attack Again
-
[quote name=“groll” post=“22167” timestamp=“1374210374”]
at 52236: network is time DOS for 2 hours a head for means of the last 11 blocks, so attacker has control unless he generate less then 6 block per 2 hours or everyone change time to 2 hours ahead.the attacker was able to generate 6 blocks 2 hour ahead in 11 blocks so no block with current time enter the chain, only blocks ahead of current time can enter.
[/quote]Explains a lot. Been mining on D2’s pool and just noticed every share over the past 130 minutes has been a reject…
-
[quote name=“raptorak” post=“22169” timestamp=“1374215103”]
[quote author=groll link=topic=2847.msg22167#msg22167 date=1374210374]
at 52236: network is time DOS for 2 hours a head for means of the last 11 blocks, so attacker has control unless he generate less then 6 block per 2 hours or everyone change time to 2 hours ahead.the attacker was able to generate 6 blocks 2 hour ahead in 11 blocks so no block with current time enter the chain, only blocks ahead of current time can enter.
[/quote]Explains a lot. Been mining on D2’s pool and just noticed every share over the past 130 minutes has been a reject…
[/quote]You still having the issues?
What needs to be done to fix?
-
jamestown on the trollbox was a former miner and believer in Feathercoin. He is now lost to us because of the “5th attack” again a few hours ago. He is saying that he is about to dump a lot of Feathercoin on to the BTC-e exchange and this makes me sad.
If he was just a troll I wouldn’t care but he seems smart and heart broken. That was another attack after the one yesterday?
-
What doesn’t kill us makes us stronger :).
I believe in our dev’s that they will come with a clever solution!
-
I will continue mining feathercoin forever. No matter even after 100000000th attack. For me it is this awesome community that makes me continue my belief in feathercoin. Whatever you want to do now, keep your dev team and we will support you.
-
[quote name=“groll” post=“22167” timestamp=“1374210374”]
at 52236: network is time DOS for 2 hours a head for means of the last 11 blocks, so attacker has control unless he generate less then 6 block per 2 hours or everyone change time to 2 hours ahead.the attacker was able to generate 6 blocks 2 hour ahead in 11 blocks so no block with current time enter the chain, only blocks ahead of current time can enter.
[/quote]He has started it at [url=http://explorer.feathercoin.com/block/65a157fcbd2a941fb9245fea365a25acebd0db80ebaa43204d89d840bf92b165]#52229[/url]. GetMedianTimePast() uses 11 previous blocks to calculate the median time stamp, and AcceptBlock() rejects any new blocks with time stamps lower than calculated. So, once he set up a chain of blocks which shifted GetMedianTimePast() way ahead into the future, no valid blocks with actual time are accepted by the network. I have expected a trick like that.
We need to reduce the future time allowance between blocks. Why 2 hours if our block target is 2.5 minutes? We had ~1 hour between blocks only when trapped at very high difficulty before #33000, but that’s not going to happen again, so 1 hour limit is more than enough.
[code] // Check timestamp
if (GetBlockTime() > GetAdjustedTime() + 2 * 60 * 60)
return error(“CheckBlock() : block timestamp too far in the future”);[/code]It’s worth to increase nMedianTimeSpan, too.
-
This comes from Bitcoin as 6 block every 10 minutes so 1 hour of block. this require 51% to sustain as 50% of the block represent 50% of the window. this is different in FTC with 2.5 minutes
2 things: make it the other sustains it
The first seems nearly ok you need >50% of the block to do so. a 40% with luck can do. but should be short live if not sustained.
to sustain you should need >50% of the block at current diff so for 2.5 it’s not 6 but 24 so median should be calculated on 49 blocks not 11. reducing the window to 6X2.5 can also be a solution, this will lead to some block rejected for time diff but 15 minutes seems ok. I don’t have time to check this exactly but i think GetAdjustedTime() is current time adjusted by the network time adjustement message. if it’s the case the adlustment should be lower then this to prevent DOS on time. (gettime() + adjust maxed at 35 *60)
note: dayligth saving times should not change anything as it’s UTC so this should have no impact. This was the reason in old time we puts 2h window in time validation of transaction in banking. even so 1-2 blocks would be rejected that is less problematic then what we currently have.
so my correction proposal is to replace the 2 * 60 * 60 by 15*60.
p.s. sorry for the attack posting with just some info not complete when the attack occur. I was going to bed when I see it so posted it in haste.
-
[quote name=“chrisj” post=“22189” timestamp=“1374223625”]
jamestown on the trollbox was a former miner and believer in Feathercoin. He is now lost to us because of the “5th attack” again a few hours ago. He is saying that he is about to dump a lot of Feathercoin on to the BTC-e exchange and this makes me sad.If he was just a troll I wouldn’t care but he seems smart and heart broken. That was another attack after the one yesterday?
[/quote]I understand his frustration. With that being said, he could pull up coinchoose, close his eyes, point to any coin and it will be more likely to compromise. We’re attacked because of the status of the coin. [b]We hate to lose people[/b], we’re doing everything we can to resolve it . This isn’t something that was put on the back burner… it’s not a simple solution and we’ll need to be the first Scrypt coin to implement one.
-
[quote name=“Justabitoftime” post=“22227” timestamp=“1374243731”]
[quote author=chrisj link=topic=2847.msg22189#msg22189 date=1374223625]
jamestown on the trollbox was a former miner and believer in Feathercoin. He is now lost to us because of the “5th attack” again a few hours ago. He is saying that he is about to dump a lot of Feathercoin on to the BTC-e exchange and this makes me sad.If he was just a troll I wouldn’t care but he seems smart and heart broken. That was another attack after the one yesterday?
[/quote]Current Network Speed 842,750,247 KHash/s (60 block avg.)!
I understand his frustration. With that being said, he could pull up coinchoose, close his eyes, point to any coin and it will be more likely to compromise. We’re attacked because of the status of the coin. [b]We hate to lose people[/b], we’re doing everything we can to resolve it . This isn’t something that was put on the back burner… it’s not a simple solution and we’ll need to be the first Scrypt coin to implement one.
[/quote] -
Obviously something isn’t being reported correctly on the stats page, I notified Bush.
-
block explorer is showing low difficulty and blocks being generated within seconds of each other. even if the stats page isn’t reporting correctly, the block explorer should be and what it is showing is truly disturbing.
-
I wish i knew what was going on?
Hope it can be fixed ;D
-
Also noticed, that the timestamps of the latest blocks are not in normal order.
If you start at the current block and move backward, the creation times of previous blocks are later than those of following blocks
Example:
Block 52514 timestamp 1374248324 (2013-07-19 15:38:44)
Block 52515 timestamp 1374248320 (2013-07-19 15:38:40)Strange…
-
I’m afraid we have to act quickly. Either with advanced checkpointing or something else. People start to panic.
-
[quote name=“ghostlander” post=“22239” timestamp=“1374247221”]
I’m afraid we have to act quickly. Either with advanced checkpointing or something else. People start to panic.
[/quote]right now ftc is starting to get dumped on btc-e.
-
[quote name=“jeremiel” post=“22242” timestamp=“1374247675”]
[quote author=ghostlander link=topic=2847.msg22239#msg22239 date=1374247221]
I’m afraid we have to act quickly. Either with advanced checkpointing or something else. People start to panic.
[/quote]right now ftc is starting to get dumped on btc-e.
[/quote]Cant wait to buy cheap ftc when the time comes, hopefully right before we’re able to get out of this shitstorm. What i can say is that when ftc survives this one there truly is high hopes for this coin and the comunity!
-
[quote name=“ghostlander” post=“22239” timestamp=“1374247221”]
I’m afraid we have to act quickly. Either with advanced checkpointing or something else. People start to panic.
[/quote]I agree. It looks like the attacker has done something to the block chain to lower the difficulty and is proceeding with a 51% attack. Lower difficulty means confirmations are faster, therefore attacker could potentially cash in before the exchanges can react.
-
[quote name=“svennand” post=“22244” timestamp=“1374248184”]
[quote author=jeremiel link=topic=2847.msg22242#msg22242 date=1374247675]
[quote author=ghostlander link=topic=2847.msg22239#msg22239 date=1374247221]
I’m afraid we have to act quickly. Either with advanced checkpointing or something else. People start to panic.
[/quote]right now ftc is starting to get dumped on btc-e.
[/quote]Cant wait to buy cheap ftc when the time comes, hopefully right before we’re able to get out of this shitstorm. What i can say is that when ftc survives this one there truly is high hopes for this coin and the comunity!
[/quote]I was hoping to do that on cryptsy but we’ll see. That also could be the reason for the attacks. They know that ftc will bounce back so they’ll get to buy real cheap ftc. though these attacks the last couple days seem to be going after the foundations of ftc. I mean how do you cause the block chain to go down in difficulty but the hash go up?
-
[quote name=“jeremiel” post=“22242” timestamp=“1374247675”]
[quote author=ghostlander link=topic=2847.msg22239#msg22239 date=1374247221]
I’m afraid we have to act quickly. Either with advanced checkpointing or something else. People start to panic.
[/quote]right now ftc is starting to get dumped on btc-e.
[/quote]Being dumped and going straight back up, people know its still cheap.
-
[url=http://explorer.feathercoin.com/address/71om8JdKi72gihUwpsbzHNifmRpot8pv7u]http://explorer.feathercoin.com/address/71om8JdKi72gihUwpsbzHNifmRpot8pv7u[/url]
This look like one of the attackers. Notice what happens at block 52423.
