Don't roll back the chain = Feathercoin stuffed.
Do roll back the chain = Feathercoin stuffed.
Topic: delete - page 2. (Read 3987 times)
We have lots of orphan blocks created by the attacker. The network is not running two version of the block chain as some people believe.
That's total BS and you know it. The whole reason you don't want to roll back is because of the volume traded on BTC-e before you decided "hey, this is a real attack". Setting a CK post attack is stupid when it's not a post attack LOL
What you're doing is praying to god that whatever fork BTC-e is on becomes the dominant fork and I'm sure that's the one you hard coded into the new client. Screw the rest of the people on the smaller fork huh?
You shouldn't worry about pissing of an exchange and do the right thing. Hard code at the first point of attack and roll back.
Just my .02 ftc and wish you luck.
~BCX~
Are you the infamous BitcoinEXpress that threatened Litecoin with a 51% attack all that time ago and ended up crashing the market? I though you went into hiding.
Anyway yes, undoing all that trade over the last couple of days to spite an attacker would be very damaging. Check the block chain explorer if you want to see the chain that everyone is using, orphans can be viewed there two, you can verify that the orphans are incorporated into the blockchain and are not left running out there. If there were multiple version then miners would not have seen orphan blocks on the pools, they would have showed as genuine on the fork. Fork did not happen, orphans happened. I hope this is clear to you know.
Please keep misinformation to the trollbox. It is a shame to see BitcoinTalk slowly turn into a troll sanctuary
Dear Mr Bushstar.
cryptoexplorer, wemineftc, coinotron - those are on a different chains than BTC-E .
No one got their coins. The chain is still forked or completely fckd.
cryptoexplorer, wemineftc, coinotron - those are on a different chains than BTC-E .
No one got their coins. The chain is still forked or completely fckd.
I am not sure what BTC-e are doing. I have never been able to make contact with them. They may be suspending their daemons and double checking everything manually before updating. They are a major target and I'm sure they are doing everything they can to safe guard themselves. I would like them to be a bit more upfront about things as we are left guessing.
it is ironic when I see people trying to comfort their selves about what is happening!! it is a huge problem, you are just so ignorant, or the new FTC pump made you risk everything for nothing, unbelievable !!!!
it's greed, I'm sure that the developers or the few insiders that hold FTC don't want the chain fixed.
it is ironic when I see people trying to comfort their selves about what is happening!! it is a huge problem, you are just so ignorant, or the new FTC pump made you risk everything for nothing, unbelievable !!!!
Rolling back would be very hard to achieve and would be incredibly damaging to the coin. There was over 4000BTC volume on Feathercoin at BTC-e. I doubt you could convince them that we need to roll back.
You know what else is very damaging to the coin? Not rolling back. FTC's reputation is on the line
You see if you allow the attacking chain to persist then the attack wins. It also sends a message to all other potential attackers that your coin network condones this behavior. Which means FTC will get attacked again. FTC will lose hashing power in the future and will be ripe for another attack based on this attack and response I refuse to mine FTC and I'm sure there are others. Coinchoose has already delisted FTC and I expect that other services will do the same in time.
FTC is broken if you don't fix it then the block chain will have this attack in its history and FTCs future as a potential currency will forever be tarnished.
*hides in closet*
FTC isn't 51ed and an updated client is available.
http://forum.feathercoin.com/index.php?topic=1525.0
http://forum.feathercoin.com/index.php?topic=1525.0
Quote
Checkpoints have been added to the client set to after the attacks stopped
SO yes, it was successfully 51%'ed.
FTC isn't 51ed and an updated client is available.
http://forum.feathercoin.com/index.php?topic=1525.0
http://forum.feathercoin.com/index.php?topic=1525.0
*grabs popcorn*
Dear Mr Bushstar.
cryptoexplorer, wemineftc, coinotron - those are on a different chains than BTC-E .
No one got their coins. The chain is still forked or completely fckd.
cryptoexplorer, wemineftc, coinotron - those are on a different chains than BTC-E .
No one got their coins. The chain is still forked or completely fckd.
you can add BigVerns fcpoool to that list too.
We have lots of orphan blocks created by the attacker. The network is not running two version of the block chain as some people believe.
That's total BS and you know it. The whole reason you don't want to roll back is because of the volume traded on BTC-e before you decided "hey, this is a real attack". Setting a CP post attack is stupid when it's not a post attack LOL
What you're doing is praying to god that whatever fork BTC-e is on becomes the dominant fork.
The only way the attacker doesn't succeed in killing FTC is if you don't fix it right.
~BCX~
+100000000000
Dear Mr Bushstar.
cryptoexplorer, wemineftc, coinotron - those are on a different chains than BTC-E .
No one got their coins. The chain is still forked or completely fckd.
cryptoexplorer, wemineftc, coinotron - those are on a different chains than BTC-E .
No one got their coins. The chain is still forked or completely fckd.
Welcome to my world.
We have lots of orphan blocks created by the attacker. The network is not running two version of the block chain as some people believe. Clients see one chain with a fair few orphan blocks after the attack. Our orphans are a result of an attack no doubt but these things do occur naturally. Some of the faster block chain manage to generate huge orphan chain.
Rolling back would be very hard to achieve and would be incredibly damaging to the coin. There was over 4000BTC volume on Feathercoin at BTC-e. I doubt you could convince them that we need to roll back.
I imagine that the attacker would take great delight watching someone try to rollback a coin after they attacked it and would endeavour to attack it again to make all efforts fruitless. Rolling back is not a practical or sensible solution for this situation.
We are investigating technical solutions that everyone can use. In the short term we are safe guarded by the large hash power coming to Feathercoin. The Feathercoin source code has been updated to include new checkpoint to make sure that none of are subsequent work after the attacks can be challenged. You can get the updated client from the Official Feathercoin website.
Official Feathercoin Website
Rolling back would be very hard to achieve and would be incredibly damaging to the coin. There was over 4000BTC volume on Feathercoin at BTC-e. I doubt you could convince them that we need to roll back.
I imagine that the attacker would take great delight watching someone try to rollback a coin after they attacked it and would endeavour to attack it again to make all efforts fruitless. Rolling back is not a practical or sensible solution for this situation.
We are investigating technical solutions that everyone can use. In the short term we are safe guarded by the large hash power coming to Feathercoin. The Feathercoin source code has been updated to include new checkpoint to make sure that none of are subsequent work after the attacks can be challenged. You can get the updated client from the Official Feathercoin website.
Official Feathercoin Website
If there are no split forks, how come transactions are 'lost' even after >200 confirmations?
We have lots of orphan blocks created by the attacker. The network is not running two version of the block chain as some people believe. Clients see one chain with a fair few orphan blocks after the attack. Our orphans are a result of an attack no doubt but these things do occur naturally. Some of the faster block chain manage to generate huge orphan chain.
Rolling back would be very hard to achieve and would be incredibly damaging to the coin. There was over 4000BTC volume on Feathercoin at BTC-e. I doubt you could convince them that we need to roll back.
I imagine that the attacker would take great delight watching someone try to rollback a coin after they attacked it and would endeavour to attack it again to make all efforts fruitless. Rolling back is not a practical or sensible solution for this situation.
We are investigating technical solutions that everyone can use. In the short term we are safe guarded by the large hash power coming to Feathercoin. The Feathercoin source code has been updated to include new checkpoint to make sure that none of are subsequent work after the attacks can be challenged. You can get the updated client from the Official Feathercoin website.
Official Feathercoin Website
Rolling back would be very hard to achieve and would be incredibly damaging to the coin. There was over 4000BTC volume on Feathercoin at BTC-e. I doubt you could convince them that we need to roll back.
I imagine that the attacker would take great delight watching someone try to rollback a coin after they attacked it and would endeavour to attack it again to make all efforts fruitless. Rolling back is not a practical or sensible solution for this situation.
We are investigating technical solutions that everyone can use. In the short term we are safe guarded by the large hash power coming to Feathercoin. The Feathercoin source code has been updated to include new checkpoint to make sure that none of are subsequent work after the attacks can be challenged. You can get the updated client from the Official Feathercoin website.
Official Feathercoin Website
Wonder how much time until FTC is dead at btc-e.
delete
Jump to: