Authors

RetiredCoder

Solved four keys of the Bitcoin puzzle transaction, then posted seven mini-puzzles on Bitcointalk, four of them paying the Bitcoin Cash left on those addresses.
IDretired-coder25 / 45person · 1 collection · 2024-10-14 → 2026-07-29
Subject

RetiredCoder

bitcoincashbitcoin

Bitcoin puzzle solver and author of RCKangaroo who posted seven mini-puzzles on Bitcointalk: the Bitcoin Cash left on four solved puzzle addresses, and 0.01 BTC three times.

Puzzles
7
Prize recorded
5.1 BCH, 0.03 BTC
Still unsolved
0 · -
closed 7 / 7
Channels
githubgithub.com/RetiredC
bitcointalkbitcointalk.org/index.php

Techniques

  • partial-key3 of 7 puzzles

Log

 

Registered the bitcointalk account on October 5, 2024.

bitcointalk.org/index.php
 

Wrote that the mini-puzzles are meant to be easy, so everyone with minimal skills can solve them, and that #67 and #135 are there for anyone who wants hard ones.

bitcointalk.org/index.php
 

Explained the #130 mini-puzzle in the thread after its winner never showed up there.

bitcointalk.org/index.php
 

Printed the key of puzzle #135 while explaining mini-puzzle #7, whose winner did not write the solution in the thread: It's not polite.

bitcointalk.org/index.php

Who this is

The same RetiredCoder as on the solver page: RCKangaroo, four puzzle transaction 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 mini-puzzles instead, one for each key, October to December 2024, and let the thread fight for it. Then three more with 0.01 BTC on a fresh key, and in July 2026 a seventh, for 135.

The first three 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, and its key came out through mini-puzzle #7.

What the record says

Four facts, all from Bitcointalk. The account registration, the post about what mini-puzzles are for, and the two explanations the author wrote when a winner stayed quiet, for #130 and for #7. The second one printed the key of 135. The author record keeps no addresses. The four big BTC solves have theirs on the solver record, and the funding of #4 to #6 stays on those puzzles.

The record

tssrc/collections/mini.ts
static readonly author = party("RetiredCoder", {
  key: "retired-coder",
  kind: PartyKind.Person,
  about: "Bitcoin puzzle solver and author of RCKangaroo who posted seven mini-puzzles on Bitcointalk: the Bitcoin Cash left on four solved puzzle addresses, and 0.01 BTC three times.",
  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" }),
    fact("Printed the key of puzzle #135 while explaining mini-puzzle #7, whose winner did not write the solution in the thread: It's not polite.", SEVENTH, { date: "2026-07-29" }),
  ],
});