Peter Todd

IDpeter-todd10 / 18person · 1 collection · 2013-09-13

Subject

Peter Todd

bitcoin

Bitcoin Core contributor and applied cryptography consultant, creator of OpenTimestamps, who paid for hash collisions with Bitcoin script in 2013.

Puzzles: 6
Prize recorded: 3.07465 BTC
Still unsolved: 4 · 0.59365 BTC

closed 2 / 6

Channels: websitepetertodd.org; githubgithub.com/petertodd; twitterx.com/peterktodd; keybasekeybase.io/petertodd; bitcointalkbitcointalk.org/index.php

Addresses: 1FCYd7j4CThTMzts78rh6iQJLBRGPW9fWv; 3MeoP8VzBURphKjrpkyY2GoW52z32ZmfK7

Log

2013-09-13

Posted the bounties on bitcointalk in September 2013: P2SH scripts that pay anyone who presents two different inputs with the same hash.

bitcointalk.org/index.php

undated

Created OpenTimestamps, a standard for timestamping data on Bitcoin with free calendar servers.

opentimestamps.org

undated

Writes at petertodd.org since 2013: replace by fee, timestamping, consensus and code review of Segwit and V3 transactions.

petertodd.org

undated

The Keybase account proves one key over petertodd.org, GitHub petertodd, Reddit petertodd and X peterktodd.

keybase.io/petertodd

Who this is

Peter Todd has been around Bitcoin since 2010 and has argued most of its arguments in public: replace by fee, soft forks over hard forks, the Segwit code review, V3 transactions. He created OpenTimestamps, which is still the standard way to timestamp a file on Bitcoin. The hash collision bounties are from September 2013. Each one is a P2SH script that runs two inputs through a hash and pays if the inputs differ and the hashes don't. The SHA-1 one was collected. The rest are still there and still worth something if you have a collision to sell.

What the record says

The bitcointalk thread, because it's where the bounties were posted. OpenTimestamps and petertodd.org, because they're his projects and his writing, first party. And the Keybase account, which is the interesting one: it's a cryptographic proof that one key controls the domain, the GitHub account, the Reddit account and the X account. That's the strongest kind of link an author record can carry, so it's a profile and a fact both.

He's a public figure with a long public record, and the page could be three times as long. It carries what the puzzles need: who he is, what he built, and that his accounts are provably his.

The record

src/collections/hash_collision.ts

static readonly author = party("Peter Todd", {
  key: "peter-todd",
  kind: PartyKind.Person,
  about: "Bitcoin Core contributor and applied cryptography consultant, creator of OpenTimestamps, who paid for hash collisions with Bitcoin script in 2013.",
  addresses: ["1FCYd7j4CThTMzts78rh6iQJLBRGPW9fWv", "3MeoP8VzBURphKjrpkyY2GoW52z32ZmfK7"],
  profiles: [
    profile("website", "https://petertodd.org/"),
    profile("github", "https://github.com/petertodd"),
    profile("twitter", "https://x.com/peterktodd"),
    profile("keybase", "https://keybase.io/petertodd"),
    profile("bitcointalk", "https://bitcointalk.org/index.php?topic=293382.0"),
  ],
  facts: [
    fact("Posted the bounties on bitcointalk in September 2013: …", "https://bitcointalk.org/index.php?topic=293382.0", { date: "2013-09-13" }),
    fact("Created OpenTimestamps, a standard for timestamping data on Bitcoin with free calendar servers.", "https://opentimestamps.org/"),
    fact("Writes at petertodd.org since 2013: …", "https://petertodd.org/"),
    fact("The Keybase account proves one key over petertodd.org, GitHub petertodd, Reddit petertodd and X peterktodd.", "https://keybase.io/petertodd"),
  ],
});