<p>The source code for old versions is available in the <a href="https://github.com/bitcoin/bitcoin" rel="nofollow">Bitcoin-Qt Git repository</a>. Click on the "branch: master" button and then select "Tags", and you can go all the way back to v0.1.5.</p>

CC BY-SA 3.0
2014-05-12T03:49:26.703Z
Thank you, didn't realize it was under tags.  Still wondering what made them "insecure".
Mine
CC BY-SA 3.0
2017-03-02T00:47:33.527Z
@Mine For one thing, you can create transactions that create billions of Bitcoins, and that client will accept them without complaint.
Nick ODell
CC BY-SA 3.0
2014-05-11T20:27:26.390Z
2014-05-11T20:27:26.390Z
Greg Hewgill
<p>According to the downloads for the Bitcoin client, versions older than ~0.3.0 were "insecure".  Since they are not available for download (and the lack of security is the given reason) no one can learn from them or verify the reason.  </p>

<p>The question I have is, 1, does anyone have a copy of the original wallets and or their source code for download and, 2, does anyone know what made them insecure?</p>

<wallet>
What made the old versions of the bitcoin wallet insecure?
Mine
# What made the old versions of the bitcoin wallet insecure?

(Asked by: username_0 on 2014-05-11)

According to the downloads for the Bitcoin client, versions older than ~0.3.0 were "insecure". Since they are not available for download (and the lack of security is the given reason) no one can learn from them or verify the reason.

The question I have is, 1, does anyone have a copy of the original wallets and or their source code for download and, 2, does anyone know what made them insecure?

**Tags:** wallet


---

## 1 answers

### Answer by username_1 on 2014-05-11. Score: 2

The source code for old versions is available in the [Bitcoin-Qt Git repository](https://github.com/bitcoin/bitcoin). Click on the "branch: master" button and then select "Tags", and you can go all the way back to v0.1.5.

> **Comments:**
> **username_0**: Thank you, didn't realize it was under tags.  Still wondering what made them "insecure".  
> **username_2**: @username_0 For one thing, you can create transactions that create billions of Bitcoins, and that client will accept them without complaint.  

---

