HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
trottier
original-bitcoin
C++2018–2022
trottier / original-bitcoin · Archived

original-bitcoin

This is a historical repository of Satoshi Nakamoto's original bitcoin sourcecode

11Distinct people
13Mentions
0Explicit recommenders
1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

This is a historical repository of Satoshi Nakamoto's original bitcoin sourcecode

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year13 dated mentions

Observed mentions: 2018-01-09 23:41:50 UTC to 2022-06-30 19:51:53 UTC.

02462018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC303
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC615
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101

What Hacker News says

13 sources
Specifically just GUI code. Seems the code was just copy-pasted from the wxWidgets GUI code for a Poker Lobby Dialog: CPokerLobbyDialogBase::CPokerLobbyDialogBase(wxWindow* parent, wxWindowID id, const wxString& title, const wxPoint& pos, const wxSize& size, long style) : wxFrame(parent, id, title, pos, size, style) All the Poker references are in lines 1573 to 1731 (https://github.com/trottier/original-bitcoin/blob/master/src...).
In The original Bitcoin code included functions related to playing Poker
I have located the first commit in the bitcoin/bitcoin repo on GitHub [1]. However, there is no single occurrence of "Poker". In the original-bitcoin repo I've found CPokerLobbyDialogBase class [2]. So I can partially confirm your theory. According to bitcoin.com in the early stages of the project there was an idea for implementing on-chain poker game [3]. > Bitcoin was simply designed to be an in game currency for a poker game Could you back this theory with some evidence? [1]: https://github.com/bitcoin/bitcoin/commit/4405b78d6059e536c3... [2]: https://github.com/trottier/original-bitcoin/blob/92ee8d9a99... [3]: https://news.bitcoin.com/satoshis-pre-release-bitcoin-code-c...
In Bitcoin is failing at becoming the future of money
Wow that's super-confused! The original Bitcoin software supported transaction replacement. You could mark a transaction as non-final and then it could be replaced until it got confirmed (potentially gated by its locktime) or until a replacement was made that was marked final. As is necessary in a distributed system, the replacement and non-replacement was best-effort and an older version could be confirmed (or a version made later than a final version). Replacement was intended for use with payment channels, like incrementally updating an open account paying someone. Unfortunately, the functionality had a flaw: It enabled a DOS attack. You could make a transaction then replace it 2^32 times and only pay one fee. So we disabled it. Without the explicit functionality you could still replace transactions by spamming nodes (and esp mi
Read the rest
ners) with the new transaction and hoping they accepted it, but it wasn't very reliable but also no longer DOS-attackable. Later, people pointed out that the DOS attack could be avoided if it was also required that each replacement increase the tx fee by at least the minimum transaction fee that would have been accepted. And the functionality was re-enabled: you could again mark transactions as non-final. When BCH was created they ripped out the functionality and falsely claimed that this made 'instant payments with 0 confirmations for small values' possible. This makes literally zero sense: First, in BCH you can still replace unconfirmed transactions, it's just less reliable. Secondly, replacement is functionality intended to enable faster transactions! Thirdly, you can disable it in Bitcoin (or replace a non-final one with a final version) and get the same behaviour as BCH if that's what your use case requires. Finally, its alleged that this was some dastardly move by Bitcoin devs to "break" "0-conf" transactions, fuled by people who can't understand that Bitcoin devs saying 0-conf transactions are not very secure doesn't mean that they don't like your ability to make them if you want to, and it ignores the fact that the basic replacement functionality was there in the very first version ( https://github.com/trottier/original-bitcoin/blob/92ee8d9a99... ) and had been disabled by the self-same people being attacked for adding it. It's basically 5G CAUSES COVID level of inanity, and it breaks my heart to see people duped by telephone-game polished versions of it.
In Coinbase to Suspend Trading in XRP
> I researched this and found that Bitcoin had no initial capacity limit That is simply untrue. From the very first version it had two capacity limits, an explicit one (https://github.com/trottier/original-bitcoin/blob/master/src...), and a smaller implicit and unintentional one (of about 500k) owing to the maximum locks that could be grabbed in a single BDB transaction. Satoshi later reduced the explicit limit further and provided no explanation for doing so ( https://github.com/bitcoin/bitcoin/commit/a30b56ebe76ffff9f9... ). However, there was no issue with spam at the time or previously, nor mention of spam, and the network already had a separate and highly functional spam limiting mechanism. Had he intended to make the limit simply temporary he could have trivially programmed it that way-- e.g. as we did when we discovered the ~500
Read the rest
kb limit, we wrote a rule that limited blocks to 500kb and then expired a few months later. The claim that it was a "temporary anti-spam limit" is a novel construction that I don't believe I saw ever claimed until many years after that change. At least by the time Satoshi went inactive he was well aware of the trade-offs: "Bitcoin users might get increasingly tyrannical about limiting the size of the chain so it's easy for lots of users and small devices." ( https://bitcointalk.org/index.php?topic=1790.msg28917#msg289... ) Perhaps you should consider conducting "research" by having an open discussion with an actual expert rather than just reading manipulative tracts designed to sucker people into buying alternatives? :) I'm happy to direct you to primary reference material even though you continue to treat me rudely and disrespectfully.
In Coinbase to Suspend Trading in XRP
It would definitely be hard to do. And my personal suspicion is that Satoshi is a group of individuals, making such an analysis almost impossible. However there is the possibility that there is some sort of "linguistic fingerprint" capable of uniquely identifying Satoshi, despite what I believe to be their efforts to create a highly specific and unique style of writing for the purposes of evading identification. The way the Unabomber used a certain phrase in the manifesto and a letter to a family member was what got him caught. https://en.wikipedia.org/wiki/You_can%27t_have_your_cake_and... Another interesting analysis would be to compare the structure of code between the early bitcoin code and code written by likely suspects. Perhaps variable naming convention will identify Satoshi. https://github.com/trottier/original-bitcoin
In The Federalist Papers: Author Identification Through K-Means Clustering
Actually, according to the original definition - https://github.com/trottier/original-bitcoin/blob/92ee8d9a99... - it does, since blockchain is bitcoin (and vice-versa), and as far as anyone can tell, currently it is indeed trustless and censorship resistant. The problem is that some people adopted blockchain as some kind of weird gimmick to wrap extraordinary claims such as the ones in the original post and promote scams (altcoins, appcoins, whatever).
In Building for the Blockchain

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.