RetiredCoder

Who this is

The same RetiredCoder as on the solver page: RCKangaroo, four b1000 keys, then a public retirement. This page is the other side. Keys like 120, 125 and 130 open more than the BTC. Their addresses were funded before the 2017 fork, so a copy of the old coins waited on Bitcoin Cash. Selling it quietly would be the boring option. RetiredCoder posted three mini-puzzles instead, October to December 2024, and let the thread fight for it.

They get harder in order. Three swapped hex characters, then twelve shuffled pieces, then a signature whose nonce sat 80 bits from another one. The author's own line on the difficulty: easy "so everyone with minimal skills can solve it", and for hard ones "you already have #67 and #135". A year and a half later, 135 was theirs too.

What the record says

Three facts, all from Bitcointalk. The account registration, the post about what mini-puzzles are for, and the explanation of #130 the author wrote when its winner never turned up. The addresses of the four big BTC solves stay on the solver record. This collection is on Bitcoin Cash, and the author record only keeps addresses on its own chain.

The record

static readonly author = party("RetiredCoder", {
  key: "retired-coder",
  kind: PartyKind.Person,
  about: "Bitcoin puzzle solver and author of RCKangaroo who gave away the Bitcoin Cash left on three solved puzzle addresses as mini-puzzles on Bitcointalk.",
  profiles: [
    profile("github", "https://github.com/RetiredC"),
    profile("bitcointalk", "https://bitcointalk.org/index.php?action=profile;u=3657819"),
  ],
  facts: [
    fact("Registered the bitcointalk account on October 5, 2024.", PROFILE, { date: "2024-10-05" }),
    fact("Wrote that the mini-puzzles are meant to be easy, so everyone with minimal skills can solve them, …", WRAP_UP, { date: "2024-11-15" }),
    fact("Explained the #130 mini-puzzle in the thread after its winner never showed up there.", EXPLANATION, { date: "2024-12-15" }),
  ],
});