CFBCFBDB Search the archive
All evidence Thread 04 / 16
Leans toward Satoshi1 min read

He knew how Satoshi hid changes in code

CFB described a specific, verifiable habit in Satoshi's earliest commits — shipping a feature dormant, then quietly switching it on inside an unrelated commit.

The thread. In 2015 Come-from-Beyond wrote: “Read early Bitcoin commits, Satoshi set this tradition by himself” — describing how Satoshi would create something “kinda disabled,” then later enable it, hidden inside a commit whose message mentioned something else.

Points toward Satoshi

This checks out. In Bitcoin’s real commit history (e.g. the Oct 29 2009 commit titled about “addr relaying… proxy… privacy patches”), Satoshi quietly shipped time-based nLockTime with the comment: “do not use time based until most 0.1.5 nodes have upgraded,” then scheduled it to activate at a future block height.

That’s not headline trivia — it’s source-level, process-level familiarity with how Satoshi personally worked. Few people on earth study a repo that closely. The author would.

Points against

The commits are public; a dedicated researcher could discover and describe the pattern. CFB also has a documented habit of stating things confidently to seem like an insider. And “Satoshi did sneaky commits” is a known piece of Bitcoin folklore.

Weight

One of the stronger threads. Most “CFB knew X” facts are learnable headlines; this is intimate craft knowledge, and he reached for it naturally. Suggestive, not conclusive.

Every quote here comes from the archive. Search it yourself, read posts in their original thread, or compare accounts.

Open the database