<p>Bitcoin-Qt is just <em>one</em> client. Yeah, it's the <em>reference</em> client, meaning that all other clients are <em>expected</em> to be compatible with it. So, the unity that Bitcoin-Qt espouses may disappear and it'd be up to the alt clients to work together with the community to decide on protocol enhancements ala BIP. I speculate that, in the worst case scenario, there may be a fork of the chain.</p>

<p>If the core development team and its resources (bitcoin.org, its github and sourceforge presence, etc.) disappeared, there are likely enough people who have touched the code and even have it cached locally that <em>someone</em> would be able to at least recompile and post a reliable package for the continuance of the reference client.</p>

<p>In its absence, though, it's likely that Bitcoin progress would shift heavily to one of the other clients or implementations, most likely BitcoinJ. This assumes that the C++ implementation -- the reference client -- is abandoned because folks picking it up don't have the expertise necessary to maintain it. This has happened with other open source projects; BitTorrent once had reference client that has since disappeared and its alternatives (Azureus/Vuze, µTorrent, Transmission, etc.) took the forefront. So, there's a precedent.</p>

CC BY-SA 3.0
2013-03-20T14:11:29.430Z
2013-03-20T14:11:29.430Z
Colin Dean
<p>If the entire core development team would be gone, a new team would need to take their place. I assume that the process might get political (some people wanting to push their agenda onto the project), and before the new devs would fully understand the system the innovation in the client might get stifled. It might also be likely that the Bitcoin Foundation would need to hire a few people to work on the project (just as they pay Gavin now). However, as there are already <a href="http://bitcoin.org/about.html">a lot of people</a> that have contributed to the project, I don't think we couldn't handle the change in the long run.</p>

CC BY-SA 3.0
2013-03-20T08:27:45.737Z
2013-03-20T08:27:45.737Z
ThePiachu
<p>I know this is an open-source project, but what happens if the core contributors are gone? How will the community decide the future of the client?</p>

CC BY-SA 3.0
2013-03-20T07:37:05.767Z
A bit related - http://bitcoin.stackexchange.com/questions/2815/what-is-the-current-feb-2012-bus-factor-of-the-standard-client
ThePiachu
CC BY-SA 3.0
2013-03-20T07:49:47.983Z
i would say that is very related!
matt
CC BY-SA 3.0
2013-03-20T12:44:14.453Z
Perhaps one may say it is a duplicate. This is a useful gateway question, though.
Gary
CC BY-SA 3.0
2013-03-20T14:00:43.183Z
I feel like that question is dated.
Colin Dean
CC BY-SA 3.0
2013-04-13T03:48:46.840Z
Same thing would happen if they were hit by a plane! :P
JavaRocky
<community>
What happens if Gavin and the other developers get hit by a truck?
matt
# What happens if Gavin and the other developers get hit by a truck?

(Asked by: username_0 on 2013-03-20)

I know this is an open-source project, but what happens if the core contributors are gone? How will the community decide the future of the client?

**Tags:** community

> **Comments:**
> **username_1**: A bit related - http://bitcoin.stackexchange.com/questions/2815/what-is-the-current-feb-2012-bus-factor-of-the-standard-client  
> **username_0**: i would say that is very related!  
> **username_2**: Perhaps one may say it is a duplicate. This is a useful gateway question, though.  
> **username_3**: I feel like that question is dated.  
> **username_4**: Same thing would happen if they were hit by a plane! :P  

---

## 2 answers

### Answer by username_1 on 2013-03-20. Score: 8 | Accepted answer

If the entire core development team would be gone, a new team would need to take their place. I assume that the process might get political (some people wanting to push their agenda onto the project), and before the new devs would fully understand the system the innovation in the client might get stifled. It might also be likely that the Bitcoin Foundation would need to hire a few people to work on the project (just as they pay Gavin now). However, as there are already [a lot of people](http://bitcoin.org/about.html) that have contributed to the project, I don't think we couldn't handle the change in the long run.


---

### Answer by username_3 on 2013-03-20. Score: 2

Bitcoin-Qt is just *one* client. Yeah, it's the *reference* client, meaning that all other clients are *expected* to be compatible with it. So, the unity that Bitcoin-Qt espouses may disappear and it'd be up to the alt clients to work together with the community to decide on protocol enhancements ala BIP. I speculate that, in the worst case scenario, there may be a fork of the chain.

If the core development team and its resources (bitcoin.org, its github and sourceforge presence, etc.) disappeared, there are likely enough people who have touched the code and even have it cached locally that *someone* would be able to at least recompile and post a reliable package for the continuance of the reference client.

In its absence, though, it's likely that Bitcoin progress would shift heavily to one of the other clients or implementations, most likely BitcoinJ. This assumes that the C++ implementation -- the reference client -- is abandoned because folks picking it up don't have the expertise necessary to maintain it. This has happened with other open source projects; BitTorrent once had reference client that has since disappeared and its alternatives (Azureus/Vuze, µTorrent, Transmission, etc.) took the forefront. So, there's a precedent.


---

