Topic: TERRACOIN ATTACK OVER 1.2TH ATTACK CONFIRMD - page 2. (Read 28159 times)
I think we'll know a lot more when those mined coins start getting moved
The only plus side is he seems to be only burst mining and not outright destroying the network like he had been.
Maybe the attacker didn't want the coin dead. He wouldn't have stopped even after the fix if he wanted it to die. The burst mining is just to accumulate more coins at this point
If I were a guessing type of person I would guess, that maybe the attacker was simply testing out a newly modified Time Warp attack on the best SHA256 coin to test on since the exploit hasn't been used in over two years and before it's modded any further to work on scrypt based coins. Just guessing but I think TRC had the perfect testing environment, a high but not too high hash rate, a dev team that would counter and user base that wouldn't just fold.
All of this just theory of course but you're probably correct, the attacker didn't want to kill TRC.
~BCX~
The idea is interesting but if the purpose of the attack was to test it on a strong sha256 coin, why bother continuing to mine even after the fix was put in place? The only purpose for doing that is to generate more coins for themselves while network hash power and difficulty are low...but for what purpose would they need the coins if they wanted it dead?
Then again, maybe you are right and he's not out to kill it, after all, at current exchange rates, he's earning ~.27 BTC for 2 minutes work whenever he decides to.
The only plus side is he seems to be only burst mining and not outright destroying the network like he had been.
Maybe the attacker didn't want the coin dead. He wouldn't have stopped even after the fix if he wanted it to die. The burst mining is just to accumulate more coins at this point
If I were a guessing type of person I would guess, that maybe the attacker was simply testing out a newly modified Time Warp attack on the best SHA256 coin to test on since the exploit hasn't been used in over two years and before it's modded any further to work on scrypt based coins. Just guessing but I think TRC had the perfect testing environment, a high but not too high hash rate, a dev team that would counter and user base that wouldn't just fold.
All of this just theory of course but you're probably correct, the attacker didn't want to kill TRC.
~BCX~
The idea is interesting but if the purpose of the attack was to test it on a strong sha256 coin, why bother continuing to mine even after the fix was put in place? The only purpose for doing that is to generate more coins for themselves while network hash power and difficulty are low...but for what purpose would they need the coins if they wanted it dead?
The only plus side is he seems to be only burst mining and not outright destroying the network like he had been.
Maybe the attacker didn't want the coin dead. He wouldn't have stopped even after the fix if he wanted it to die. The burst mining is just to accumulate more coins at this point
Recent difficulty graph:
Each of those up-swings were prefaced by the attacker mining again. 1pan mined 17 blocks between 175000 and 175025, 13fk mined 175027-175038 and diff spiked through the roof. After diff came down(53 hours!), 13fk mined 175064-175080 in 122 seconds. Again after diff dropped(22.5 hours), 13fk mined 175107-175121 in 51 seconds. Difficulty only took 2.5 hours to come down, then he mined 175152-175158 in 67 seconds, 12 hours later he mined 175188-175197 in 123 seconds and another 3 hours before he mined 175220-175228 in 133 seconds. It's only been 2 hours, but he'll prob strike again soon.The only plus side is he seems to be only burst mining and not outright destroying the network like he had been.
Latest peak was only 22287 and next dip appears less shallow than prior one. Things are about as stable difficulty-wise as they are going to get I imagine, until a large amount of hash power pours in to rock the boat.
It'd be nice to get total network hash power up higher. At these difficulties mining is more profitable than BTC. (22287 is about 140% of BTC profit.) To match BTC I imagine avg difficulty needs to be somewhere in the 30Ks. More hash power means less profit, but also more stability.
It'd be nice to get total network hash power up higher. At these difficulties mining is more profitable than BTC. (22287 is about 140% of BTC profit.) To match BTC I imagine avg difficulty needs to be somewhere in the 30Ks. More hash power means less profit, but also more stability.
Recent difficulty graph:
CoinChoose has right block # but showing wrong difficulty, so the profit % is off. Dustcoin has correct block # and difficulty, showing TRC around 245% a few minutes ago.
We should start attracting back more miners I'd think with difficulty floating between this level and ~90% of BTC at prior peak.
Wish CoinChoose had correct difficulty on their site though.
We should start attracting back more miners I'd think with difficulty floating between this level and ~90% of BTC at prior peak.
Wish CoinChoose had correct difficulty on their site though.
i'm affraid network is way too small to resist any chain hoppers or regular spikes from relatively heavy miners joining the party
EDIT : profit indicators sites are also starting to mark it as "green green green!" "Boogidy boogidy boogidy, lets go racin"
EDIT : profit indicators sites are also starting to mark it as "green green green!" "Boogidy boogidy boogidy, lets go racin"
13kf popped in with diff got down to 10K. On the way back up a bit now.
He might have the hash power for a 51% attack, don't know. Only way to prevent that is for more people to mine, but that's true for every coin.
He might have the hash power for a 51% attack, don't know. Only way to prevent that is for more people to mine, but that's true for every coin.
yay current block diff down to 45657 ... i guess 1 or 2 more blocks to reach positive ROI levels...
Then the attacker will dump his systems onto the coin and cause another spike.Very possible but not happening atm it seems. I'm interested to see how difficulty will work long-term without the halving code in there.
In the last 13 blocks we've stayed between 33783 - 39113 in spite of two peaks. So the direction changes and speed of difficulty adjustment has mellowed out at last.
yay current block diff down to 45657 ... i guess 1 or 2 more blocks to reach positive ROI levels...
Then the attacker will dump his systems onto the coin and cause another spike.But... since time wrap exploit has been fixed... they wont be able to do as much damage as before...
1PAnMKuTs9R4U9FF7xdQSmQc655d2r9zeB sent 6279.8705 to 13kfKR1BS9gtsxppMeqDTx4rAvbwWjvYSL in block 174999. According to the block chain, 13kfKR1BS9gtsxppMeqDTx4rAvbwWjvYSL has since mined blocks 175027-175037, 175064-175074 and 175076-175080. Sure looks like he's stil 51%ing the network when he wants to with those numbers.
yay current block diff down to 45657 ... i guess 1 or 2 more blocks to reach positive ROI levels...
Then the attacker will dump his systems onto the coin and cause another spike.But... since time wrap exploit has been fixed... they wont be able to do as much damage as before...
yay current block diff down to 45657 ... i guess 1 or 2 more blocks to reach positive ROI levels...
Then the attacker will dump his systems onto the coin and cause another spike.
yay current block diff down to 45657 ... i guess 1 or 2 more blocks to reach positive ROI levels...
I have seen five "end-block" values in all my downloading... none that are valid, and matching any of the block-explorers, so the block-explorer is on the wrong side of the fence too.)
Remember that the "Processing X of Y" message in the TRC wallet doesn't mean Y is correct or that you are on a chain with Y. It means you have processed up to block X, and some peer is trying to send you a chain ending in block Y. A peer with a short chain is silently and immediately ignore. A peer with a longer chain your client will talk to, to see if it has better info that you do. However, if you are synced properly it'll recognize they are wrong and ban that peer for 24 hours. Of course, the "of Y" message in the tooltip returns every time a new peer tries to give you newer blocks that aren't correct.
If your wallet says "Processing block 175097 of Y" then I'd say you are on the right chain, no matter what the value of Y is. Y might change to various numbers as various forked peers try to lead you astray. But it won't work, and you'll sit on 175097 until the next block is found.
Current block 175098 with difficulty 63031 is the correct chain.
http://trc.cryptocoinexplorer.com/block/000000000000db5e0afa0cc2b30a08c11ffa41429597f2252477694dab5ec60f
Is the correct block 175097.
RoyMiningCo, Redpoint, Multipool, Hynodeva are all working on 175098. P2Pool nodes using the github patch to support Terracoin -44 are working this chain as well. Coinotron hasn't resumed mining yet but we know he's upgraded to new client via IRC.
DustCoin and CoinChoose web sites show this as the correct block.
If you see any crypto web sites that aren't on this chain you should let them know to install -44 and run -reindex. If you want to pop into IRC later tonight, maybe someone can zip up the block chain for you to download directly if you just can't seem to sync properly off the peers.
http://trc.cryptocoinexplorer.com/block/000000000000db5e0afa0cc2b30a08c11ffa41429597f2252477694dab5ec60f
Is the correct block 175097.
RoyMiningCo, Redpoint, Multipool, Hynodeva are all working on 175098. P2Pool nodes using the github patch to support Terracoin -44 are working this chain as well. Coinotron hasn't resumed mining yet but we know he's upgraded to new client via IRC.
DustCoin and CoinChoose web sites show this as the correct block.
If you see any crypto web sites that aren't on this chain you should let them know to install -44 and run -reindex. If you want to pop into IRC later tonight, maybe someone can zip up the block chain for you to download directly if you just can't seem to sync properly off the peers.
Well, I am not golden, nor are many of the pools... And I think you only "think" you are golden... (You might have gotten on the right chain, by luck. But I assume you are on the chain that I was, when it looked "golden" to me... but was a dud-chain, producing blocks that were useless and invalid, though they showed in the wallet, as if they were valid.)
Doing all the above, results in fail.
Being 8 days behind, and not being able to mine, and when I can mine, the blocks that were valid, later disappear... is not "golden".
I will laugh when you find you have mined all week long, and all the coins you think you have mined, are all gone, the next time you restart the wallet.
Which block-explorer is right.... there are two, not the same results. Every pool I see is generating all orphans.
Current diffs showing as... 71960.69, 5183.834, and 5432311.847...
Which fork are you on, that you "think" is the right one?
Doing all the above, results in fail.
Being 8 days behind, and not being able to mine, and when I can mine, the blocks that were valid, later disappear... is not "golden".
I will laugh when you find you have mined all week long, and all the coins you think you have mined, are all gone, the next time you restart the wallet.
Which block-explorer is right.... there are two, not the same results. Every pool I see is generating all orphans.
Current diffs showing as... 71960.69, 5183.834, and 5432311.847...
Which fork are you on, that you "think" is the right one?
If you upgrade to the latest client, and re-sync the blockchain, im pretty sure ull end up with the same chain as http://trc.cryptocoinexplorer.com/ . Tried it twice, same results.
Well, I am not golden, nor are many of the pools... And I think you only "think" you are golden... (You might have gotten on the right chain, by luck. But I assume you are on the chain that I was, when it looked "golden" to me... but was a dud-chain, producing blocks that were useless and invalid, though they showed in the wallet, as if they were valid.)
Doing all the above, results in fail.
Being 8 days behind, and not being able to mine, and when I can mine, the blocks that were valid, later disappear... is not "golden".
I will laugh when you find you have mined all week long, and all the coins you think you have mined, are all gone, the next time you restart the wallet.
Which block-explorer is right.... there are two, not the same results. Every pool I see is generating all orphans.
Current diffs showing as... 71960.69, 5183.834, and 5432311.847...
Which fork are you on, that you "think" is the right one?
Doing all the above, results in fail.
Being 8 days behind, and not being able to mine, and when I can mine, the blocks that were valid, later disappear... is not "golden".
I will laugh when you find you have mined all week long, and all the coins you think you have mined, are all gone, the next time you restart the wallet.
Which block-explorer is right.... there are two, not the same results. Every pool I see is generating all orphans.
Current diffs showing as... 71960.69, 5183.834, and 5432311.847...
Which fork are you on, that you "think" is the right one?
Great, you compile the code yourselves... but do you actually look at the code? That is the whole purpose of compiling yourself... so you can be sure you are compiling something that is not tainted.
https://github.com/terracoin/terracoin/commits/master
I always skim over the diffs.
Anyone can read the full source if they wanted and raise an alarm if something was off. Thats the advantage of opensource, and compiling your own binaries. Im pretty sure if something malicious made it into the repo it would be noticed and made public immediately.... but i cant say the same for binaries...
Jump to: