Bitcoin Institute

Myckel Habets

BioMike, the Gentoo user Satoshi apologized to for taking a question as an objection

Figures

A dark navy illustration with the name "BioMike" at the upper left. A large gold and orange double-ended wrench lies at an angle above a row of four teal blocks. One more block has left the row and rests on the far end of the wrench, and a large gold question mark stands at the upper right. The words "What's wrong with getting informed?" appear below.

On August 26, 2010, Satoshi Nakamoto apologized to a BitcoinTalk user.

Satoshi Nakamoto (BitcoinTalk post, August 26, 2010, 12:08:12 AM UTC)

My apologies, your post was indeed a question not a statement.

The user was Myckel Habets, who posted as BioMike. Three days earlier Satoshi had announced that he was writing a system for broadcasting alerts across the network. Each alert would be signed with a key that only he held. Five hours later Habets asked a question. If some government arrested Satoshi and made him hand over the key, could it shut down the whole network? Or was that not possible?

Satoshi quoted the question in a reply two days later and wrote that it made him think the people objecting did not know what they were talking about. All the key could do was disable six commands for a while, and the network would keep running. An hour and a half later Habets replied.

BioMike (BitcoinTalk post, August 25, 2010, 6:23:45 PM UTC)

I’ve never objected this change/idea, just asking if this was possible and to what extent. What’s wrong with getting informed? 😉

Satoshi’s apology came less than six hours after that. What happened to the key over the next eight years is covered on the alert key page.

Habets had registered on the forum 41 days before the apology. Habets ran Gentoo Linux and built the Bitcoin software by hand. This site holds 22 of Habets’s posts from the five months before Satoshi left the forum, and 11 of them are about how that software should be built.

2010Registers on BitcoinTalkand asks why the buildis static (Jul 16)Objects to thewxWidgets version(Aug 19)Asks what happens if agovernment takes thealert key (Aug 23)Satoshi apologizes(Aug 26)Lists advice for aGentoo package (Aug27)Says the clock shouldbe left to NTP (Sep 6)Reports sending 10BTC to Tahoe-LAFS(Oct 4)2018Last post in the profile(Sep 14)

Is static linking safe?

Habets’s first post came four minutes after registering. It went into the thread announcing version 0.3.1 and reported that a build on x86 Gentoo, made with Habets’s own makefile, ran more smoothly than 0.3.0. That makefile produced a client that loads its libraries at run time. The standard makefile linked the libraries into the executable. The post ends by asking why.

Nearly ten hours later Satoshi answered. Different systems lack different libraries, so it was easier to link in whatever could be linked, and the size did not grow by much. Four and a half hours later Habets wrote back.

BioMike (BitcoinTalk post, July 16, 2010, 7:46:39 PM UTC)

I think size (static binary is 8x as big in my case) is not the problem, but security.

The post gives three reasons. The libraries in question are fairly common on Unix systems, where many programs depend on them. A static build is not guaranteed to run, and on Habets’s machine it failed to start because the version of another library did not match. The third reason is the real one: when a flaw is found in OpenSSL and the system ships a fixed version, an executable with the old version linked in goes on running the old version.

wxWidgets 2.9

On August 19, in a thread asking whether Bitcoin’s interface should move from wxWidgets to GTK, Habets described a different problem. wxWidgets itself was fine. The trouble was that Bitcoin used version 2.9, which many distributions treated as unstable. Habets agreed with the view that the interface and the daemon should be separated, and was already running a self-made client against the daemon alone.

A little over ten and a half hours later Satoshi quoted the post and replied. Version 2.9 was the first UTF-8 release of wxWidgets, and under 2.8 the differing character-set settings had caused endless build failures.

Satoshi Nakamoto (BitcoinTalk post, August 19, 2010, 6:44:36 PM UTC)

This is a problem that will solve itself. With time, 2.9 will become a more mainline release.

Eleven minutes later Habets responded. The reasons for choosing 2.9 were understandable and reasonable. It was just unfortunate for people who only wanted to install the version their distribution provided.

Build flags, the system clock and NTP

On August 27, Habets gave a user who had written a Gentoo package a numbered list of advice. The interface library is not needed if only the daemon is built. Optimization flags should be left to the user. The code should not be built static. Habets offered to send over a makefile.

The same day Satoshi released version 0.3.11. The announcement said it had been built with a flag aimed at one family of CPUs. Forty-six minutes later Habets asked whether that would break the build on older systems. The next day Habets asked again, this time which CPUs were covered and how many machines were being left out, and thanked another user for the explanation. Later that day Satoshi revised the announcement to say that only part of the code was compiled with the flag.

September 6 was about clocks. The software warns users when their computer’s clock is off, and Satoshi had written that he had considered using NTP to set the time but that the current method was more secure. Habets wrote that there was no reason for a modern system not to run NTP. When Insti said the Bitcoin client should not bloat itself with NTP functions, Habets agreed.

BioMike (BitcoinTalk post, September 06, 2010, 5:25:18 PM UTC)

Hell no, NTP does a good job. Don’t have other services changing the clock (also counts for bitcoin). Right tool for the right job!

DateWhat Habets wroteSatoshi
July 16, 2010Why is the standard build static?Replies nearly ten hours later that static linking is easier
August 19The trouble is wxWidgets version 2.9Replies ten and a half hours later that the problem will solve itself
August 23Could a government with the key shut down the network?Replies two days later that it could not, and apologizes the day after
August 27Will the CPU flag shut out older machines?Revises the announcement the next day: only part of the code uses the flag
September 6Leave the clock to NTPHad written the day before that he had considered NTP

Habets’s interests went beyond Bitcoin. On October 4, Habets wrote of having sent 10 BTC the day before to Tahoe-LAFS, a storage project. Nine days later Habets reported running a storage node as well.

In the alert thread, Satoshi counted Habets among the people objecting. Habets was not objecting. Since July, Habets had only been asking questions. Why is the standard build static? Which CPUs are left out? In November, under the announcement of version 0.3.17, Habets posted a single line asking why there was no 0.3.16. “What’s wrong with getting informed?” sums up Habets in one line. Satoshi apologized because Habets was right.

The real name comes from code he pointed to as his own. On August 11, 2018, Habets wrote in the Auroracoin thread on BitcoinTalk that he had just put in OpenSSL 1.1 support, and linked to the change. Its author is Myckel Habets, and the GitHub account BioMike shows the same name. Habets’s BitcoinTalk profile records 1,658 posts. This site holds 22 of them.

Reference external source

https://bitcointalk.org/index.php?action=profile;u=464
BitcoinTalk profile, checked November 21, 2026: registered July 16, 2010, at 05:20:31, with 1,658 posts, last active November 28, 2019. In the profile's list of posts the first came four minutes after registration and the last is dated September 14, 2018.

Other external sources

Related Entries

23 entries / 7 threads