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

Who Is Pieter Wuille? Bitcoin Core Developer and BIP Author

Key Points

Who is Pieter Wuille? The Bitcoin Core developer known as sipa, author of the HD wallet standard and co-author of SegWit and Taproot. His BIPs and career.

Pieter Wuille is a Bitcoin Core developer who does Bitcoin research and development at Chaincode Labs, and on GitHub he goes by sipa. He wrote BIP 32, the proposal that set the standard for HD wallets, and co-wrote the ones behind SegWit and Taproot. He also started libsecp256k1, the signature library inside Bitcoin Core.

In mid-November 2026, the Bitcoin Improvement Proposals archive listed Pieter Wuille as an author on 27 of its 218 proposals, more than any other name in its author lines. Twenty-two of those 27 carried the status Deployed, the archive's label for a proposal in active use, against just over a third of the whole archive.

Pieter Wuille at a Glance

Fact
As of mid-November 2026
Known as
sipa, his GitHub handle
Works at
Chaincode Labs, formerly Blockstream
Earliest Bitcoin Core commit on GitHub
March 2011
BIPs as an author
27 of the archive's 218
Best-known work
HD wallets, SegWit, Schnorr and Taproot, libsecp256k1
Bitcoin Core merge-signing key
Removed in July 2022

Bitcoin itself trades on Phemex as a perpetual future, where funding payments keep its price near the spot market.

 

Who Is Pieter Wuille?

Wuille works on the layers of Bitcoin a typical holder doesn't see, from how a wallet derives its keys to how a node checks a signature. His own site lists code efficiency, applied cryptography and coding theory among his interests, and all three run through the proposals and papers he lists there.

Bitcoin Core is the open-source program that connects to the Bitcoin network and checks every block and transaction for itself. GitHub's record of the project attributed nearly 2,400 commits to Wuille's account, authored between March 2011 and October 2026.

Being a Bitcoin Core developer carries no formal rank. The project's contributing guide says it has no privileged class of developers, though its maintainers merge pull requests and run the release cycle. Each release bundles work from many contributors, and Bitcoin Core v32 brought faster validation and smarter relay for people who run their own nodes.

Outside Bitcoin, his work page lists JiF, an image format that by his account grew into FLIF and later fed into the basis for JPEG XL.

Which BIPs Has Pieter Wuille Written?

A Bitcoin Improvement Proposal is the design document developers write to propose a change, from a new consensus rule to a wallet format. Each file in the archive names its authors and a status. The table groups Wuille's 27 by the year each number was assigned.

Years assigned
BIPs
Status in the files
2012
30 duplicate transactions, 32 HD wallets
Deployed
2014
42 an April Fools' text, 62 malleability
42 Deployed, 62 Closed
2015
9 version bits, 66 strict DER, 103 block size, 141 SegWit
103 Closed, the rest Deployed
2016
143 and 144 SegWit signing and relay, 146 malleability
146 Closed, the rest Deployed
2017
173 Bech32 addresses
Deployed
2019-2020
324 v2 P2P, 330 Erlay, 340-342 Schnorr/Taproot, 350 Bech32m
330 Draft, the rest Deployed
2021-2024
379 Miniscript, 380-387 output script descriptors
379 Draft, 380-387 Deployed

Deployed is a high bar. BIP 3 sets the archive's process rules, and it grants that status on evidence that a proposal is in active use, such as a soft fork's activation on the network.

By that test about four in five of Wuille's proposals made it into use. Most authors in the archive are one-offs. Of the 167 names in its author lines, two in three appear on only one file.

BIP 32, his 2012 HD wallet standard, derives a whole tree of keys from one seed. That's why backing up a single seed can cover every address a wallet makes. It's one of seven BIPs that carry his name alone. He wrote eight more with Ava Chow on descriptors, a simple language for describing the scripts a wallet uses.

Is Pieter Wuille sipa?

Yes, sipa is the handle Pieter Wuille uses on GitHub, and his site and that account point at each other. GitHub's data for the sipa account gives its name as Pieter Wuille, links wuille.net and shows it opened in January 2011. Wuille's own About page links back to the same account.

The handle stands in for his name in Bitcoin Core's own records. Bitcoin Core's 22.0 release notes credit "Basic Taproot signing support for descriptor wallets" to sipa, and Wuille's work page sends you to bitcoin.sipa.be for its Miniscript and Bech32 demos.

If you're searching for him, his name is spelled Pieter in every BIP file that lists him and on his own site, never Peter.

From Bitcoin Core to Chaincode Labs: Pieter Wuille's Career

Wuille's academic research was in programming languages. His work page lists papers on constraint programming from 2007 to 2012 and a PhD dissertation, which KU Leuven's repository dates to December 2011.

Wuille's Bitcoin Core record on GitHub opens in March 2011 with "Spent per txout", a change that let the wallet track each output of a transaction as spent or unspent on its own. In March 2013 he wrote libsecp256k1's opening commit. GitHub attributed about 800 of the library's nearly 3,000 commits to his account.

Wuille wrote BIP 141, the core SegWit proposal, with Eric Lombrozo and Johnson Lau. It moved signatures into a separate structure called the witness. SegWit went live in August 2017. BIP 141's text says unintended malleability, where tweaking a signature changes a transaction's ID, became impossible. It also calls that fix superior to BIP 62, his own 2014 try at the same problem.

Taproot followed in November 2021, built on three proposals Wuille co-wrote. Jonas Nick is on all three, with Tim Ruffing on Schnorr signatures and Anthony Towns on Taproot and Tapscript.

Bitcoin Core's 0.21.1 release notes said it would let multisig scripts and "complex contracts" look the same on chain as single-signature payments. Those contracts are Bitcoin's narrow take on the smart contract.

If your Bitcoin address starts with bc1, its format comes from two of Wuille's proposals. BIP 173, which he wrote with Greg Maxwell in 2017, defined Bech32 for SegWit addresses. His BIP 350 later swapped in an improved variant, Bech32m, for the version 1 outputs Taproot uses.

Bitcoin Core's maintainers are the people who merge code into the project. In October 2014 the project added a script that checks merge commits are signed by keys on a list called trusted-keys.

Wuille's keys sat on that list from its first version until July 2022, when he removed his own key in a commit titled "Remove my key from trusted-keys".

Wuille's GitHub profile calls him a Bitcoin developer at Chaincode Labs and says he was formerly at Blockstream.

In May 2023 Suhas Daftuar opened a GitHub proposal for a new mempool design with the words "@sipa and I gave a presentation to some other developers". The mempool is the waiting room where a node holds unconfirmed transactions. The redesign is joint work, not his alone.

His work page lists a 2026 paper on the same idea, Bitcoin Mempool Linearization, written with Arman Mollakhani and Dongning Guo. Wuille's newest Bitcoin Core commits on GitHub were authored in October 2026. They change how a node picks from the peer addresses it stores, so each candidate in a group gets an equal chance.

How to Trade Bitcoin Futures on Phemex

Wuille's proposals shape how bitcoin is stored and signed. Trading its price is a separate activity. Phemex's BTC/USDT futures let you go long or short on Bitcoin's price with USDT, a dollar-pegged stablecoin, as margin. You never hold the coins or their keys.

Futures use leverage, and a leveraged position is closed automatically if losses push its margin below a set minimum. That forced close is called liquidation in crypto trading, and it can take the whole margin behind the position.

You can set stop-loss and take-profit orders before you enter, so the trade closes at prices you picked in advance. Average True Range can help you set those levels by showing how far Bitcoin's price usually moves in a day.

Frequently Asked Questions

What did Pieter Wuille say about quantum computers?

In a July 2025 mailing-list post, Wuille wrote that Bitcoin's main quantum threat in the medium term "is not the actual materialization" of a key-breaking quantum computer but the belief that one may exist soon. He added that he wasn't "advocating for any specific cause of action."

What is libsecp256k1?

It's the C library Bitcoin Core uses for signatures on secp256k1, the curve behind Bitcoin's keys. Wuille started it in 2013. Bitcoin Core moved its signature checks onto it in February 2016, and the 0.12.0 release notes put the speedup at over five times on x86_64 machines.

Is Pieter Wuille still a Bitcoin Core maintainer?

No. He removed his own key from Bitcoin Core's trusted-keys list, the keys allowed to sign merges, in July 2022. The list's history to mid-November 2026 shows no key of his added back, though he kept writing code for the project into October 2026.

 

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