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?
Topic: TERRACOIN ATTACK OVER 1.2TH ATTACK CONFIRMD - page 10. (Read 28166 times)
Someone got an ASIC working on TRC?
asics have always worked with TRC. I use my asics for it but this shit right now is insane....
If this is a design problem (vulnerability) with the source, and if the developers have forsaken it, and the code is still publicly available, it behooves anyone with vested interest in the coin and sufficient programming skills (mine are insufficient) to address this. Even if that means pulling the newest source from an unmaintained repository (is it maintained?), making the fix, and uploading the source to some other new, maintained repository.
I'm not sure whether it started with miner software using sha256d to describe the double sha-256 hash or if it came from outside of bitcoin circles. A quick google is inconclusive. I know the term has become pretty common and since it's the switch for algo selection in several miners it's probably here to stay.
Sha-2 and sha-256 are the related like squares and rectangles. All sha-256 is sha-2 but not all sha-2 is sha-256.
I haven't seen shaw-256 but it reads like a phonetic typo. I'm sure I'll notice it now.
Sha-2 and sha-256 are the related like squares and rectangles. All sha-256 is sha-2 but not all sha-2 is sha-256.
I haven't seen shaw-256 but it reads like a phonetic typo. I'm sure I'll notice it now.
I've seen it on a thread here, and I think I even made a "SHAWty got low" comment. People speak out of ignorance without bothering to do even basic research.
This seems to be a bug or a exploit regarding the "RETARGET: artificially lowered diff; hard time mining current block..." change from April.
Block generation rate is very high and so this special retarget should NOT happen.
The block generation rate in the last hour was 4.6 blocks a minute!!!
Block generation rate is very high and so this special retarget should NOT happen.
The block generation rate in the last hour was 4.6 blocks a minute!!!
The security model is pretty simple brute force: have more block-confirming computation power than all the supercomputers/competitors in the world all put together, by several times over.
That is not conducive to having umpteen chains that are not merging the same computer-power. By far the majority of the relevant computer-power on the planet needs to all achieve consensus as to the correct blockchain. Deliberately creating alternative blockchains undermines the very basis of the blockchain-security concept.
-MarkM-
That is not conducive to having umpteen chains that are not merging the same computer-power. By far the majority of the relevant computer-power on the planet needs to all achieve consensus as to the correct blockchain. Deliberately creating alternative blockchains undermines the very basis of the blockchain-security concept.
-MarkM-
t what is up with the "D". For the first couple years nobody got the hashing algorithm wrong and then recently there has been this poliferation of "SHA-256D" and "SHAW-256". Once could be a typo, one person multiple times could been someone who is repeating a mistake but multiple people over multiple threads.
It is SHA-2 or SHA-256 (or without the hyphen SHA2, SHA256).
It is SHA-2 or SHA-256 (or without the hyphen SHA2, SHA256).
I'm not sure whether it started with miner software using sha256d to describe the double sha-256 hash or if it came from outside of bitcoin circles. A quick google is inconclusive. I know the term has become pretty common and since it's the switch for algo selection in several miners it's probably here to stay.
Sha-2 and sha-256 are the related like squares and rectangles. All sha-256 is sha-2 but not all sha-2 is sha-256.
I haven't seen shaw-256 but it reads like a phonetic typo. I'm sure I'll notice it now.
Someone got an ASIC working on TRC?
You can use Asic on TRC and others that are sha256D
Off topic but what is up with the "D". For the first couple years nobody got the hashing algorithm wrong and then recently there has been this poliferation of "SHA-256D" and "SHAW-256". Once could be a typo, one person multiple times could been someone who is repeating a mistake but multiple people over multiple threads.
It is SHA-2 or SHA-256 (or without the hyphen SHA2, SHA256).
Someone got an ASIC working on TRC?
They are already available. TRC is SHA-256
The main factor seems to its relation to Bitcoin and its standing armies of asic. So maybe it has to become more similar in its defense by raising difficulty in time
As far as I can tell, the devs aren't active any more. Hoping I'm wrong. But someone posted a serious big report a month or two ago about the 32 bit version of the client being able to download/sync the block chain, and it was never replied to or fixed.
Are the Devs gonna fix this? Kinda worried for Terracoin. No activity on Git for over three months now.
Devs?
The last time TRC's difficulty adjustment was made was because the network hash rate was pretty low and someone would mine with an ASIC getting tons of blocks, difficulty skyrocket, and they move to a new coin until it was back down. Other coins have had that problem too (like FRC). That's not an attack per se, just someone optimizing their mining efforts but disrupting the whole coin because they have such a large % of the network hash rate.
I'm not sure that is happening now or not though, or if it some other sort of exploit. When the difficulty drops to the minimum 5k for quite a while, even if the 'attacker' wasn't mining, it should never go that low. There was a DDOS attack on TRC pools about a week ago but that seems over with at the moment.
Coinotron has 363.4 GH mining TRC right now. Even someone with 2-3 60GH/s miners should not be able to disrupt the difficulty that badly, or conduct a 51% attack. Maybe someone has way more than that? (A BFL minirig?)
The only solution, which is pretty much always the solution, is for more people to mine on the established pools so the "attackers" make up a smaller % of the network hashrate.
I'm not sure that is happening now or not though, or if it some other sort of exploit. When the difficulty drops to the minimum 5k for quite a while, even if the 'attacker' wasn't mining, it should never go that low. There was a DDOS attack on TRC pools about a week ago but that seems over with at the moment.
Coinotron has 363.4 GH mining TRC right now. Even someone with 2-3 60GH/s miners should not be able to disrupt the difficulty that badly, or conduct a 51% attack. Maybe someone has way more than that? (A BFL minirig?)
The only solution, which is pretty much always the solution, is for more people to mine on the established pools so the "attackers" make up a smaller % of the network hashrate.
So in an attempt to make diff adjust more often due to ASIC attacks they still have another issue.
I still say a big part of the problem is they chose sha256 as the hash algorithm which there is now an army of ASICs to rape it at no cost to the attacker...well not much.
Maybe it's a repeat of this?
https://bitcointalksearch.org/topic/trc-disclosure-terracoin-difficulty-collapse-exploit-167493
https://bitcointalksearch.org/topic/trc-disclosure-terracoin-difficulty-collapse-exploit-167493
Sure acts like it... I wonder if they found a way to do the same exploit even after the patch that was done in April.
The last time TRC's difficulty adjustment was made was because the network hash rate was pretty low and someone would mine with an ASIC getting tons of blocks, difficulty skyrocket, and they move to a new coin until it was back down. Other coins have had that problem too (like FRC). That's not an attack per se, just someone optimizing their mining efforts but disrupting the whole coin because they have such a large % of the network hash rate.
I'm not sure that is happening now or not though, or if it some other sort of exploit. When the difficulty drops to the minimum 5k for quite a while, even if the 'attacker' wasn't mining, it should never go that low. There was a DDOS attack on TRC pools about a week ago but that seems over with at the moment.
Coinotron has 363.4 GH mining TRC right now. Even someone with 2-3 60GH/s miners should not be able to disrupt the difficulty that badly, or conduct a 51% attack. Maybe someone has way more than that? (A BFL minirig?)
The only solution, which is pretty much always the solution, is for more people to mine on the established pools so the "attackers" make up a smaller % of the network hashrate.
I'm not sure that is happening now or not though, or if it some other sort of exploit. When the difficulty drops to the minimum 5k for quite a while, even if the 'attacker' wasn't mining, it should never go that low. There was a DDOS attack on TRC pools about a week ago but that seems over with at the moment.
Coinotron has 363.4 GH mining TRC right now. Even someone with 2-3 60GH/s miners should not be able to disrupt the difficulty that badly, or conduct a 51% attack. Maybe someone has way more than that? (A BFL minirig?)
The only solution, which is pretty much always the solution, is for more people to mine on the established pools so the "attackers" make up a smaller % of the network hashrate.
How many scrypt ASICs are you aware of?
We are talking apples and oranges here. Gpus vs ASICs are a factor of 10 in speeds. Two totally different scenarios.
We are talking apples and oranges here. Gpus vs ASICs are a factor of 10 in speeds. Two totally different scenarios.
Yeah, and Scrypt vs SHA-256 is a factor of 1000 in speeds. For a lot less than what it costs to put together a 1.2TH attack on Terracoin you could put together a 1.2GH attack on, say, Feathercoin with GPUs. It would cost a lot more in electricity, but an attacker wouldn't care about keeping the farm going on an ongoing basis.
Correct me if I'm making faulty assumptions or if my seat-of-the-pants math has led me astray.
However, the part about messing with the difficulty level is actually relevant. The attacker could have made it easier to attack by making the difficulty so unpredictable that miners gave up on it. I know I gave up on it for that reason. Difficulty would be enticingly low so I'd mine for about a half hour when I'd notice the difficulty had gone through the roof. After a while I learned not to pay any attention if TRC had a low difficulty. It wouldn't be worth my time to switch. Enough people give up and you keep the fluctuations going, eventually you can catch the network with its total hashrate down.
I'd be surprised if there weren't already a name for that tactic.
Dem 10 second blocks: 
Code:
[2013-07-25 11:58:00] LONGPOLL from pool 4 detected new block
[2013-07-25 11:58:04] LONGPOLL from pool 4 detected new block
[2013-07-25 11:58:07] LONGPOLL from pool 4 detected new block
[2013-07-25 11:58:13] LONGPOLL from pool 4 detected new block
[2013-07-25 11:58:26] Stratum from pool 1 detected new block
[2013-07-25 11:58:27] Stratum from pool 3 detected new block
[2013-07-25 11:58:30] LONGPOLL from pool 4 detected new block
[2013-07-25 11:58:38] Stratum from pool 1 detected new block
[2013-07-25 11:58:49] Stratum from pool 1 detected new block
[2013-07-25 11:58:58] Stratum from pool 2 detected new block
[2013-07-25 11:59:13] LONGPOLL from pool 4 detected new block
[2013-07-25 11:59:36] Stratum from pool 1 detected new block
Are the Devs gonna fix this? Kinda worried for Terracoin. No activity on Git for over three months now.
This has nothing to do with hash algorithm. FTC using scrypt didn't prevent someone showing up with 51% attack.
It's always been a problem in the implementation of terracoin's difficulty adjustment. Difficulty adjustment shouldn't be too fast.
It's always been a problem in the implementation of terracoin's difficulty adjustment. Difficulty adjustment shouldn't be too fast.
How many scrypt ASICs are you aware of?
We are talking apples and oranges here. Gpus vs ASICs are a factor of 10 in speeds. Two totally different scenarios.
When I first mentioned this issue was before they changed the difficulty adjustment, back then the same issues still applies.
Difficulty adjustment is a moot point when it comes to 51% attack. If it was an issue then a new sha256 chain with adjustment every week would still have the same issues of a 51% attack because 1 sha256 ASIC would be enough to 51% attack it.
To be clear this is assuming fact someone is 51% attacking TRC, which I'm not sure is true.
This has nothing to do with hash algorithm. FTC using scrypt didn't prevent someone showing up with 51% attack.
It's always been a problem in the implementation of terracoin's difficulty adjustment. Difficulty adjustment shouldn't be too fast.
It's always been a problem in the implementation of terracoin's difficulty adjustment. Difficulty adjustment shouldn't be too fast.
Jump to: