Deleting the chain and redownloading, it's now on 175038 like I hear it should be, but it still says "14 hours behind".
Topic: TERRACOIN ATTACK OVER 1.2TH ATTACK CONFIRMD - page 5. (Read 28159 times)
Deleting the chain and redownloading, it's now on 175038 like I hear it should be, but it still says "14 hours behind".
I installed the 0.1.3-44 update, and it shows me at block 175200.
start your client with following parameter :
Code:
-reindex
Did not work. It got stuck reindexing 175009 (I assume that's where the chains diverge).
Deleting the chain and redownloading, it's now on 175038 like I hear it should be, but it still says "14 hours behind".
Halving removed, old times of dead blockchain back.
Can anybody give a small summary of what happened? Seems confusing at the moment. I have some TRCs and am wondering whether they will be worthless.
This seems to be the most concise explanation, crucially there are two things going on; the timewarp bug and the attacker currently has >50% hashing power on the TRC network:
Since TRC is based off the BTC source, is the 6 hour thing something BTC fixed previously that TRC never copied? Or is it a TRC-specific bug?
TRC not only didn't copy the fix, it made it worse. Asymmetrical difficulty changes (where difficulty can go down more than it can go up) allows the attacker to amplify the effects of the attack. No serious crypto-currency can have an asymmetrical difficulty system. It is trivial to exploit.
how's the attack? is it over?
if the attacker has all these coins he wouldn't want the coin to die I guess, cause he'd lose all, wouldn't he?
You are assuming the motive of the attacker(s) is to make money.
weird that with all these problems price actually rose on btc-e up to 160 and now currently at 146 well above yesterday prices. so what's with block 038? are we stuck there, any chance for the block chain to resume regularly? if the attacker has all these coins he wouldn't want the coin to die I guess, cause he'd lose all, wouldn't he?
Reindex doesn't help, it just gets confused on the more recent blocks and doesn't process them. Even with deleting the other files. I think the problem is out of our hands, hopefully the dev(s) can sort something out, although I wonder if the coin can ever continue on from here.
start your client with following parameter :
(append it to your shortcut command), it should do the trick.
Code:
-reindex
loaded only 108222 blocks
upd.
deleted all files (except wallet and conf.) in appdata
loaded only 175038 blocks on 0.1.3-44 client
I installed the 0.1.3-44 update, and it shows me at block 175200.
start your client with following parameter :
Code:
-reindex
I installed the 0.1.3-44 update, and it shows me at block 175200.
Don't understand how that's possible. All pools and explorer that are running new client are on 175039 at the moment. Devs confirmed p2pool is on wrong chain with wrong hash for block 175038.
Ah. He downloaded the new client -after- block 175,000 so invalid blocks already in his data files.
Confirmed by someone in BTC-E chat that BTC-E is on the forked chain. Deposits/withdrawals working with forked chain, not with official chain.
I installed the 0.1.3-44 update, and it shows me at block 175200.
From the announce mailing list:
I see in my debug log peers trying to submit blocks well past where the official chain is actually at. People need to update!
Quote
Important info : some p2pool users aren't running the latest client
build, if you're running p2pool, please download last TRC client and/or
update your client source code prior to new compilation
build, if you're running p2pool, please download last TRC client and/or
update your client source code prior to new compilation
I see in my debug log peers trying to submit blocks well past where the official chain is actually at. People need to update!
what block am I suppose to be on I'm showing 175038?
Yes that was correct.
http://sourceforge.net/mailarchive/message.php?msg_id=31222636
Specifically
height: 175038
hash: 00000000000010fc5dc8c16d2e8edf721ffbc450ee325ed3515192db11f0469d
time : 1374955622 (2013-07-27 20:07:02)
nonce : 2584811947
bits : "1a421cf5"
That's the block you should see in your terracoind if you are on latest version and in sync with official chain.
175027-175037 were all mined by the old attacker in succession, using address 13kfKR1BS9gtsxppMeqDTx4rAvbwWjvYSL. This address accepted a deposit from 1PAnMKuTs9R4U9FF7xdQSmQc655d2r9zeB at block 174999. Looks like he is still affecting the network and still orphaning massive blocks.
Stuck on 175031 on several different PC's. 
It's weird, it looks like p2pool isn't following the same scheme ; i guess p2pool users are not up to date
Yes, they are on a different chain, probably since block 175000.With 54 GH/s
Just let TRC die already IMO
what block am I suppose to be on I'm showing 175038?
i tried direct connection to a seednode, and that's what i am at too.
It's weird, it looks like p2pool isn't following the same scheme ; i guess p2pool users are not up to date
Jump to: