<p>11/12 March 2013 Chain Fork at block height 225,430.It's 31 blocks long.</p>

CC BY-SA 4.0
2018-09-19T14:49:57.887Z
Wow, was that a brute PoW fork? Or was that a bug / protocol patch or similar?
MaiaVictor
CC BY-SA 4.0
2018-09-19T14:53:18.173Z
It was an issue with version of bitcoin client.Miner mined with the version 0.8.0 which wasn't compatible with version 0.7
VforVendetta
CC BY-SA 4.0
2018-09-19T14:48:54.733Z
2018-09-19T14:48:54.733Z
VforVendetta
<p>On <a href="https://www.google.com.br/search?q=longest+blockchain+fork+that+has+been+site:bitcoin.stackexchange.com&amp;sa=X&amp;ved=2ahUKEwib29-WocfdAhUGhpAKHfIzCG4QrQIoBDAAegQICRAM&amp;biw=1680&amp;bih=971" rel="nofollow noreferrer">this</a> thread, the user asked what is the longest unintentional fork that Bitcoin had suffered. From the answers present, Bitcoin never had a >4 block fork until 2012. </p>

<p>It has been 6 years though, and I wonder if there is a more up-to-date statistics on that question, and if any study has been done so far.</p>

<blockchain-fork><history><stale-block>
What is the longnest blockchain fork that has been orphaned to date?
MaiaVictor
# What is the longnest blockchain fork that has been orphaned to date?

(Asked by: username_0 on 2018-09-19)

On [this](https://www.google.com.br/search?q=longest+blockchain+fork+that+has+been+site:bitcoin.stackexchange.com&sa=X&ved=2ahUKEwib29-WocfdAhUGhpAKHfIzCG4QrQIoBDAAegQICRAM&biw=1680&bih=971) thread, the user asked what is the longest unintentional fork that Bitcoin had suffered. From the answers present, Bitcoin never had a >4 block fork until 2012.

It has been 6 years though, and I wonder if there is a more up-to-date statistics on that question, and if any study has been done so far.

**Tags:** blockchain-fork, history, stale-block


---

## 1 answers

### Answer by username_1 on 2018-09-19. Score: 1

11/12 March 2013 Chain Fork at block height 225,430.It's 31 blocks long.

> **Comments:**
> **username_0**: Wow, was that a brute PoW fork? Or was that a bug / protocol patch or similar?  
> **username_1**: It was an issue with version of bitcoin client.Miner mined with the version 0.8.0 which wasn't compatible with version 0.7  

---

