An historical timeline of The Real Bitcoin (TRB) development, part i.

On October 10, 2014, on the well-intentionedi premise that more relay nodes would mean a healthier, more robust, and more reliable Bitcoin network, I whipped up a little guide for setting up el cheapo AWeSque nodes. How easy, how simple, how innocent, no ?ii

At the time, the Vessenes Phoundation was promoting their version of the Bitcoin reference code, which they called “0.9.x” or “Core,” but which was widely known to be at best a laughingstock and at worst a very marginal improvement on webwallets.iii But while the old Foundation’s jig was up and their puerile pretenders to the throne were literally tripping over themselves to lie to Bitcoin users in an attempt to subvert this world-eating little project, the emerging Republic calling #bitcoin-assets home lacked a reference implementation to call its own. Each individual member carefully guarded their homebrew concoctions with all the shrewdness of poker players in an old Western Saloon, leaving the hows and whys of each stack almost entirely unknown, even if theories swirled.

With this in mind, my $20 node guideiv was never intended to be the final word on the matter, but rather a stop-gap measure that at the time seemed better than nothing, being predicated on the not-overly-ridiculous-sounding-notion that someone, somewhere in my WoT had a decent reference implementation (and that they’d be willing to share) that I could just plug in, press the big red LAUNCH button, watch the thing build in a flurry of lines whizzing across the terminal screen before kickin my feet up on the desk, breathing a sigh of satisfaction, and then deciding if I wanted to spend the next hour shoveling snow or reading poetry or something, all the while smugly content in the knowledge that I was supporting the Bitcoin network.v Oh, the innocence of youth… and how dubious this all seems in hindsight !

Needless to say, this reference codebase thing wasn’t quite so Fast forward to today and we’re still here, still glued to our chairs as the since-established Bitcoin Foundation (the Real one) hacks away at Satoshi’s codebase, getting ever-closer yet paradoxically ever-further from their objective, all the while trying to hygienically remove as much stupidity / FOSS as possible while keeping the important bits ticking.

This is their story :

October 21, 2014 : Bitcoin 0.5.3 selected by Mircea Popescuvii

After Ben Vulpes sifted through the history of Bitcoin’s development from Satoshi to Phoundation, the call was made to select a development branch upon which to base future efforts.viii The balance of considerations saw 0.5.3 selected, with cutting edge features like encrypted wallets (ooh! ahh!) being included and obvious prole-related nonsense like support for “click-to-pay” being eschewed. That the 0.5.3 branch was far from perfect was no mystery, but it was the tallest midget so to speak.

October 22, 2014 : The (Real) Bitcoin Foundation established

In order to guide this process as formally and as professionally as possible, Mircea Popescu selected Shane Kinneyix and Ben Vulpesx as co-chairs and Juraj Varinyxi as treasurer for the newly formed (Real) Bitcoin Foundation, an organisation tasked with taking the 0.5.3 turd and polishing it into something resembling Anish Kapoor’s Cloud Gate in Chicago, except useable and meaningful.

While Mr. Kinney and Mr. Vulpes were tasked with guiding and moderating development of The Real Bitcoin (TRB), patch submissions have always been open to anyone in assbot’s L2 WoT. As you’ll see, this is an important consideration, not the least of which because it’s the opposite of the FOSSxii approach that rendered the reference software so mangled in the first place.

The Real Bitcoin Foundation’s charter is found here.

October 24, 2014 : Qt excised by Stanislav Datskovskiyxiii

With “chicken,” the first scruffy feathers to be plucked from the frankly fetid corpse of 0.5.3 was Qt, which was the basis for the program’s Graphical User Interface (GUI). Qt uses C++ with signals and slotsxiv to provide a cross-platform application framework. for, essentially, illiterate amateurs.xv

As Qt introduced weight and complexity to the code, both mortal enemies of security and “fits in head,” philosophically as much as practically, Qt had to go. Bitcoin, after all, is for professionals and this first excision was telling of this fundamental reality. What remained after the excision of Qt could more properly be called “bitcoind” once again as it was accessible exclusively via the command line interface, as you do.

October 25, 2014 : UPNP excised by Ben Vulpes

With the “rm_rf_upnp” patch, Universal Plug and Play (UPnP) – which allows inter-device networking and communication but in doing so creates a security vulnerability – was plugged. The issue with UPnP centres around the “libupnp” library – that is, the Linux Software Development Kit (SDK) that provides “developers” with an Application Programming Interface (API) and open source code for building control points, devices, and bridges – and in which multiple buffer overflow vulnerabilities were widely recognised, even by the US Department of Homeland Security. (N.B. If something isn’t good enough for the enemy, it’s a pretty damn good bet that it won’t be good enough for the Republic.)

October 28, 2014 : HTTPS/SSL excised by Stanislav Datskovskiy

With the “https-snipsnip” patch, the vulnerability that exposed the Bitcoin network to Heartbleed via Public Key Infrastructure (PKI) was removed.xvi OpenSSL is a cryptographic library that enables Secure Sockets Layer (SSL) or Transport Security Layer (TLS) encryption across the web. In theory, this is both a “cost-effective” and “industry approved” method of encrypted communication. In practice, however, the project was subverted sometime in 2012, if not sooner, and no amount of rubber-stamping could prevent the stench of roadkill from betraying the true state of the library, viz. unknowably large and impossible to trust.

Given that Mr. Datskovskiy is on the record as calling out this turd way back in 2013, it’s little wonder he was the one to pull the trigger here.xvii

October 29, 2014 : Win32 excised by Stanislav Datskovskiy

With the “goodbye-win32” patch, the swiss cheese mousetrap that is Microsoft’s Windows operating system was trimmed from the reference implementation. This should really require no further explanation other than fuck Bill Gates.

October 30, 2015 : Upgrade warning excised by Stanislav Datskovskiy

With the “turdmeister-alert-snip” patch, the old-fashioned, out-dated “upgrade needed” warning message from USGavin et al. was put on the chopping block.xviii The idea being that The Real Bitcoin will eventually be whittled into a weaponised implement of such robustness that it would never need software updates,xix certainly not those “recommended” by Central Command.

December 19 2014 : DBD parameters set by Shane Kinney

With the “db_config” patch, the wedge issue at Block 252450 was overcome. The ram exhaustion wedge was apparently caused by less than ideal Berkeley DB (BDB) configuration settings. BDB is a relatively simple-to-use database management library that’s used to keep track of Bitcoin transactions.

[To be continued]

___ ___ ___

  1. Yes, the road to hell is undeniably paved with good intentions and quadruply so when you have the good intentions of others in mind, with evil squaring further still as a function of distance between you and the intended recipient. So ya, mind your own fucking business ! Ya bunch of fucking wreckers… Oh, you “just wanted to” ? Shut up and get back in the kitchen. What is this, a democracy ? And no, I don’t give a shit if you fancy yourself “a guy who doesn’t do kitchens,” stop being such a sexist tard and find a worthwhile cock to suck already. You’re not getting any younger, you know.
  2. This was itself motivated by an article I’d penned just a few days prior, specifically :

    The biggest challenge ahead isn’t “bringing Bitcoin to the people” or some such nonsense, it’s in maintaining a sufficient number of nodes to relay and verify transactions. This is challenging issue that has yet to be fully addressed.

    But hey, we need something to do in 2015 once all the derps are dead, y’know?

    Which was itself informed by a comment to this effect by Mircea Popescu, which was itself informed by Gavin Andresen’s idiocy, which was itself informed by Gavin’s mother dropping him on the head as a child, etc., etc., ad infinitum.

    Little did I, or anyone else, suspect the magnitude of the task at the time… perhaps Alf notwithstanding.

  3. This open secret was due in no small part to the at-the-time-recent Heartbleed OpenSSL vulnerability that Mike Hearn surreptitiously inserted into version 0.9, only to have his efforts blown apart by Riku, Antti and Matti of Codenomicon (“independent” and “simultaneous” discovery of the bug by Google Security my ass !)

    But what was the big deal with Heartbleed and OpenSSL ? Well, we’re getting to that !

  4. Also at the time, $20 was about 0.05 BTC and would just barely cut the mustard. Today, even with BTC trading for about 30% on the exchanges, you’re looking at about 0.18 BTC to run a node. That being said, Bitcoin’s due for another bounce-and-resettle, so 0.05 BTC per year is likely a reasonable rate going forward, which means that, yes, if you can’t afford that, you can’t afford to be in Bitcoin.
  5. Why did I want to support the Bitcoin network in the first ? Why not just be a free-rider and coast off the accomplishments of others ? Well, my personal reasons were, and still are, two-fold : i) It’s in my rational self-interest to do so, and ii) If you can, you must, and I figured that I could.
  6. See this conversation, which took place shortly after I tried and failed to follow my own recipe :

    mircea_popescu: pete_d you really should know better than taking bitcoin “foundation” shit at face value yo.
    *asciilifeform read the published script, sees nothing to verify installation of particular known-hygienic classical ver. of bitcoind

    pete_d: This i know ! Any suggestions for how to remedy this ??
    mircea_popescu: Nothing good short of running some decent nodes.

    pete_d: And where might I find the scripts for this?
    mircea_popescu: For running a node you mean ?

    pete_d: 0.9.3 is obviously dirt but how would one go about installing 0.6.x on a VPS ?
    mircea_popescu: Well you get the code off the repository and compile it. Or if you trust anyone, you get a binary from them.

    pete_d: The instructions in my “guide” definitely need improvement. Currently point people towards latest bitcoind as per pankkake’s script.*
    mircea_popescu: Generally the people involved in Bitcoin to this level kinda have the history, and a complete file of historical versions and so on. I guess it’s an interesting question, “What’s the new guy to do”. Bunch of playing catchup it seems.

    asciilifeform: n00b, as in any serious business, must apprentice to another. Or make good friends with the nuts and bolts alone, for ages.
    *pete_d now accepting offers for binary of bitcoind 0.6.x for Contravex guide.

    mircea_popescu: But actually his is a legitimate request. I guess I’m adding this to the “wanted maintainer for eulora binaries” thing : wanted maintainer for bitcoin binaries. Anyone want to do a bunch of compiling and sign stuff ?

    And so it began. Of course, since the lathe dog is a more notable player in this saga than I could ever hope to be (as you’ll readily observe from the sheer volume and quality of patches he’s thus far submitted to TRB development) his open order for a printed and bound volume of the 0.6-era source code is commonly regarded as the first cause in The Real Bitcoin’s development, even though it took place some 10 days later, and only after much collective stumbling around in the dark and pawing at the edges of the iceberg that is modern general purpose computing… But hey, we could point to specific causes and their causes and their causes all the way back to infinity and we’d just end up at that Douglas Adams line about the creation of the Universe and how it made a lot of people very angry and was widely regarded as a bad move.

    ___ ___

    *You may recall pankkake as being he of “OMG YOU GUISE R A CULT” fame.

  7. mircea_popescu is identified by PGP Fingerprint : 6160 E1CA C8A3 C529 66FD  7699 8A73 6F0E 2FB7 B452
  8. Update : MP can be credited with his selection of the “no later than 0.6.x branch” as early as February 2014 December 2013 (h/t to Alf!) May 2013 (!).
  9. mod6 is identified by PGP fingerprint : 027A 8D7C 0FB8 A166 4372 0F40 7217 05A8 B71E ADAF
  10. ben_vulpes is identified by PGP fingerprint : 4F79 0794 2CA8 B89B 01E2 5A76 2AFA 1A9F D2D0 31DA
  11. jurov is identified by PGP Fingerprint : BBB0 A999 5003 7551 F533  850A 677A BD62 D0AE E7D7
  12. Free and Open Source Software.
  13. asciilifeform is identified by PGP fingerprint :1721 5D11 8B72 3950 7FAF ED98 B982 28A0 01AB FFC7.
  14. Signals and slots work a bit like a spreadsheet in that certain objects auto-update when other objects that they’re linked to are modified.
  15. A little birdy tells me that Qt isn’t just for illiterates, but is unfortunately, “the ~only~ remaining working cross-platform native-widget graphic lib for cpp.”
  16. The issue with PKI is that it requires “Certificate Authorities”, ie. third-parties who may or may not have your best interests at heart, and whose opinion of you may change over time. For obvious reasons, then, PKI is a political tool rather than a security tool and therefore has no place in sane personal computers any more than your national army does.
  17. From “Don’t Blame the Mice,” September 2013 :

    Let’s go back to your kitchen. It is squeaky-clean, you say, because nowhere in your house do you make use of Microsoft’s miserable imitation of an operating system. Guess what, the mounds of garbage are still there, stinking brazenly; the mice leap, they play without fear, because virtually all of your cryptographic needs are serviced by some variant of OpenSSL. What a monstrous turd of a library! Have you read and understood it – any of it? Do you personally know a single living soul who has done so? Dare to contemplate the very idea of plowing through these megabytes of gnarly crapola.

  18. “WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade” from out of the blue ? Pfff. No thank you.

    That being said, “InvalidChainFound: WARNING: Displayed transactions may not be correct!  You may need to upgrade, or other nodes may need to upgrade.” is still in place as a warning in TRB.

  19. Even if hard drive updates are inevitable as the blockchain grows ever more voluminous.

4 thoughts on “An historical timeline of The Real Bitcoin (TRB) development, part i.

  1. […] of you may be aware of a project called "therealbitcoin" and some of its development history.  Over the last few days I forked the project, dropped in the woodcoin genesis block, […]

  2. […] is a thing, which is probably about the nicest thing you could say about him and the rest of the PRB pretenders. […]

  3. […] competition – that is, in praxis and not in somnis – to the decrees of TMSR~ and its TRB reference […]

Leave a Reply

Your email address will not be published. Required fields are marked *