logo
TradFi
Sign Up to 15,000 USDT in Rewards
Limited-time offer is waiting for you!

Who Is Peter Todd? Bitcoin Developer Behind OpenTimestamps

Key Points

Who is Peter Todd? Meet the Bitcoin developer who built OpenTimestamps and argued for replace-by-fee, and see why he says he is not Satoshi.

Peter Todd is the Bitcoin developer who wrote the time-lock rule in Bitcoin Improvement Proposal (BIP) 65, co-wrote opt-in replace-by-fee and created the OpenTimestamps project. On GitHub he describes himself as an applied cryptography consultant. He has said he is not Satoshi Nakamoto, Bitcoin's creator.

Todd was arguing for full replace-by-fee on Bitcoin's developer mailing list by May 2013, and Bitcoin Core made it the default only in October 2024. His BIP 65 time-lock moved faster, going from its assigned number to enforcement on the Bitcoin network in 439 days. Bitcoin changes slowly, and his record shows how slowly.

Date
What happened
Source
May 2013
Todd argues for full replace-by-fee on the developer list
bitcoin-dev archive
October 2014
BIP 65 assigned, with Todd as sole author
BIP repository
December 2015
BIP 65 enforced on the Bitcoin network
Bitcoin Core code
February 2016
Bitcoin Core 0.12.0 ships opt-in replace-by-fee
bitcoincore.org
September 2016
OpenTimestamps client 0.2.0, the public alpha
OpenTimestamps repository
October 2024
Bitcoin Core 28.0 makes full replace-by-fee the default
bitcoincore.org
October 2026
OpenTimestamps client 0.8.0 released
OpenTimestamps repository
 

How Long Did Replace-by-Fee Take to Become Bitcoin's Default?

More than 11 years, from Todd's May 2013 posts to Bitcoin Core 28.0. Replace-by-fee lets you resend an unconfirmed payment with a higher fee, so a stuck transaction can still get into a block.

The idea predates Todd. BIP 125 records that Bitcoin's original software allowed replacement until Satoshi Nakamoto switched it off in version 0.3.12. In March 2013 Todd proposed a cautious version for adding fees. By May he was defending full replacement, where any unconfirmed transaction can be swapped for one paying more.

Opt-in came first. Bitcoin Core merged Todd's code in November 2015, and he set out the rules in BIP 125 with David A. Harding. Bitcoin Core 0.12.0 shipped it in February 2016, letting senders mark a transaction replaceable.

Full replace-by-fee drops the mark. In August 2023 Todd wrote the commit to make it the default, though his pull request closed unmerged. Another pull request carried that commit into Bitcoin Core in August 2024. The Bitcoin Core 28.0 release notes record the default flipping from off to on.

The argument was over unconfirmed payments, which BIP 125 says some receivers trusted on first sight. Todd's 2013 posts called that a false sense of security, and Bitcoin Core's default has sided with him since version 28.0.

Replace-by-fee fixes a fee set too low, and Bitcoin Core v32's better fee estimates check fees against the queue of waiting transactions.

How Does OpenTimestamps Prove a File Existed?

OpenTimestamps proves a file existed by tying its fingerprint, a cryptographic hash, to a Bitcoin transaction. The OpenTimestamps client calls the Bitcoin blockchain its "timestamp notary," and the proof is a separate file you keep beside the original.

  1. Your computer hashes the file, so a calendar server only ever receives a hash and learns nothing about the contents.

  2. Calendar servers gather many digests and commit them to Bitcoin together, which is why a new proof needs a few hours to confirm.

  3. Anyone holding the file and its proof can check it against Bitcoin's own records, though the OpenTimestamps client needs a Bitcoin Core node of your own to verify.

That design takes Bitcoin back to one of its first ideas. Satoshi Nakamoto's 2008 white paper starts from a timestamp server that proves data existed by publishing its hash, and it cites 1990s timestamping research beside Wei Dai's b-money proposal.

The OpenTimestamps server code starts with Todd's commits of June 2012, and the client's release notes say its first version wasn't widely used. The public alpha came in September 2016 as version 0.2.0.

The client can also timestamp signed Git commits, so a software project can show when a version of its code existed. Version 0.8.0, which Todd released in late October 2026, changed that Git support so it hands the signature check only data the proof covers.

How Peter Todd's Career Shows Up in Bitcoin Core and the BIPs

Todd was posting to Bitcoin's developer mailing list by April 2012, and his name sits on 106 commits in Bitcoin Core's main code, from April 2012 to April 2025. The earliest fixed a confusing error message and landed in May 2012, nearly two years before former Bitcoin Core lead developer Gavin Andresen handed the project's top job to Wladimir van der Laan.

Todd is the only author of BIP 65, assigned in October 2014. It added OP_CHECKLOCKTIMEVERIFY, a script command that keeps coins unspendable until a chosen block height or time. Its motivation section walks through escrow and payment channels among other uses.

BIP 65's own path shows the pace of Bitcoin upgrades. Bitcoin Core merged the opcode's code in June 2015 and the soft-fork logic in October. A soft fork is a backward-compatible change to Bitcoin's rules. Version 0.11.2 shipped both in November 2015. The network enforced the rule from December, once 95% of recent blocks came from upgraded miners.

The notes for Bitcoin Core 0.12.0, the release that shipped opt-in replace-by-fee, credit Todd with 11 changes. One of them set a node that already listens on Tor, the anonymity network, to connect to other Tor nodes by default.

Todd also co-wrote BIP 9, which lets miners signal support for a soft fork through bits in each block's version field. His co-authors there were Bitcoin Core developer Pieter Wuille and two others.

With Matt Corallo he wrote BIP 111, which lets a node advertise if it serves bloom filtering. The proposal calls that service weak on privacy and a denial-of-service risk, so operators needed a way to switch it off. His name is also on BIP 63, about stealth addresses. It has a number but no text.

Bitcoin Core's code also lists a DNS seed that Todd runs, one of the servers a brand-new node asks for the addresses of its first peers. Todd added that seed to the list in February 2017.

Not every proposal landed. In April 2025 Todd opened a pull request to lift Bitcoin Core's limits on OP_RETURN outputs, which let a transaction carry a small piece of data. It closed without a merge. The data-limit change that shipped in Bitcoin Core 30.0 came through another developer's pull request, which carried one of Todd's test commits.

Did Peter Todd Create Bitcoin?

Todd has said no. HBO's October 2024 documentary "Money Electric" named him as Satoshi Nakamoto, and its director pointed to a 2010 Bitcoin forum post of Todd's as evidence. "For the record, I'm not Satoshi," Todd told CNN in a statement. He called the forum post a minor correction to what Satoshi had written.

How to Trade Bitcoin Futures on Phemex

Todd's time-locks and fee rules run inside Bitcoin's own software, and on Phemex you can trade bitcoin's price through BTC/USDT futures without holding any coins. They're perpetual contracts, so they never reach an expiry date. Your margin and any profit or loss are counted in USDT, the dollar-pegged stablecoin. Phemex also lists a BTC/USDC pair if you'd rather post margin in USDC.

Futures use leverage, and a leveraged position is closed automatically if losses push its margin below a set minimum. You can go long if you expect bitcoin to rise or short if you expect it to fall, and a stop-loss order closes the trade at a price you choose in advance.

Frequently Asked Questions

What is Peter Todd known for?

Todd is known for BIP 65, which added Bitcoin's time-lock command, and for co-writing BIP 125's opt-in replace-by-fee. He also created OpenTimestamps, a free system that uses Bitcoin to prove a file existed by a certain time. His name is on BIPs 9 and 111 as well.

Is Peter Todd still working on Bitcoin?

His public work on Bitcoin tools was still going in late 2026. OpenTimestamps client 0.8.0 came out under his name in late October 2026, and his latest post to Bitcoin's developer mailing list had come in September 2026. His GitHub profile calls him an applied cryptography consultant.

What is OP_CHECKLOCKTIMEVERIFY?

It's a Bitcoin script command, added by Todd's BIP 65, that locks coins until a set block height or date has passed. That deadline is what escrow deals and payment channels lean on, and the BIP gives both as examples.

 

Disclaimer: This article is for informational purposes only and is not financial advice. Cryptocurrency trading involves substantial risk. Always do your own research before making investment decisions.

Sign Up and Claim 15000 USDT
Disclaimer
This content provided on this page is for informational purposes only and does not constitute investment advice, without representation or warranty of any kind. It should not be construed as financial, legal or other professional advice, nor is it intended to recommend the purchase of any specific product or service. You should seek your own advice from appropriate professional advisors. Products mentioned in this article may not be available in your region. Digital asset prices can be volatile. The value of your investment may go down or up and you may not get back the amount invested. For further information, please refer to our Terms of Use and Risk Disclosure