<p>The "catching up" is more a product of the theoretical scenarios posed than the technicals of the 51% attack itself. The typical scenario posed for a 51% attack is that the attacker has already spent coins and would like to reverse that transaction. In this scenario it makes sense that the attacker must start at least at the block before his/her transaction, meaning they must catch up with the network, hence the necessity of controlling at least 51% of total hash power - any less and they'll never catch up.</p>

<p>If someone weren't trying to reverse a transaction but rather wanted to double spend coins that hadn't yet been spent at all, they wouldn't need 51% of the network to do so; a Finney attack would suffice, hence scenarios in which the coins have not yet been spent tend to be considered for this attack vector instead.</p>

CC BY-SA 3.0
2012-02-10T23:36:08.013Z
2012-02-10T23:36:08.013Z
David Perry
<p>You're exactly right; there's no need to catch up if you don't start off behind.</p>

<p>As soon as I get 51% of the network's hashing power, I start building my fork in private, then buy something on the 'real' fork and allow the purchase to get as many confirmations as it needs.  It will be a lot, because I'll be buying something really expensive.  I take care not to include my transaction in the private fork.</p>

<p>Then, once the goods are shipped I publish my secret fork and get my coins back.</p>

<p>The <a href="https://en.bitcoin.it/wiki/Weaknesses#The_.22Finney.22_attack" rel="noreferrer">Finney attack</a> is only good for double spending when the recipient accepts unconfirmed transactions.</p>

CC BY-SA 3.0
2012-02-11T00:20:23.467Z
2012-02-11T00:20:23.467Z
Chris Moore
<p>There is a lot of information on the 51% attack where an attacker is able to branch the chain and "catch up" and build a new branch that is longer than the old branch. Other than requiring more than 50% of the network's computing power, the biggest thing that makes this attack infeasible is that the further behind an attacker is, the harder it is to catch up. Some places say that this means that a payment receiver can simply wait for a couple of blocks to go by and by that time is becomes infeasible for an attacker to catch up from that far behind.</p>

<p>But why would an attacker ever have to "catch up"? Couldn't an attacker with 51% of the network's power branch the chain as soon as a new block is released and work on that branch in secret? Then at any point the attacker could publish his branch, effectively reversing any transactions that occurred between the time he branched the chain and the time it is published to the network.</p>

<security><majority-attack>
Why would you need to "catch up" in the 51% attack?
Computerish
# Why would you need to "catch up" in the 51% attack?

(Asked by: username_0 on 2012-02-10)

There is a lot of information on the 51% attack where an attacker is able to branch the chain and "catch up" and build a new branch that is longer than the old branch. Other than requiring more than 50% of the network's computing power, the biggest thing that makes this attack infeasible is that the further behind an attacker is, the harder it is to catch up. Some places say that this means that a payment receiver can simply wait for a couple of blocks to go by and by that time is becomes infeasible for an attacker to catch up from that far behind.

But why would an attacker ever have to "catch up"? Couldn't an attacker with 51% of the network's power branch the chain as soon as a new block is released and work on that branch in secret? Then at any point the attacker could publish his branch, effectively reversing any transactions that occurred between the time he branched the chain and the time it is published to the network.

**Tags:** security, majority-attack


---

## 2 answers

### Answer by username_2 on 2012-02-11. Score: 5 | Accepted answer

You're exactly right; there's no need to catch up if you don't start off behind.

As soon as I get 51% of the network's hashing power, I start building my fork in private, then buy something on the 'real' fork and allow the purchase to get as many confirmations as it needs. It will be a lot, because I'll be buying something really expensive. I take care not to include my transaction in the private fork.

Then, once the goods are shipped I publish my secret fork and get my coins back.

The [Finney attack](https://en.bitcoin.it/wiki/Weaknesses#The_.22Finney.22_attack) is only good for double spending when the recipient accepts unconfirmed transactions.


---

### Answer by username_1 on 2012-02-10. Score: 4

The "catching up" is more a product of the theoretical scenarios posed than the technicals of the 51% attack itself. The typical scenario posed for a 51% attack is that the attacker has already spent coins and would like to reverse that transaction. In this scenario it makes sense that the attacker must start at least at the block before his/her transaction, meaning they must catch up with the network, hence the necessity of controlling at least 51% of total hash power - any less and they'll never catch up.

If someone weren't trying to reverse a transaction but rather wanted to double spend coins that hadn't yet been spent at all, they wouldn't need 51% of the network to do so; a Finney attack would suffice, hence scenarios in which the coins have not yet been spent tend to be considered for this attack vector instead.


---

