<p>BIPs are just proposals. Whether any particular piece of software supports/adopts it is up to the developers of that software.</p>
<p>To find out which BIPs are supported by Bitcoin Core specifically, look at its  <a href="https://github.com/bitcoin/bitcoin/blob/master/doc/bips.md" rel="noreferrer">doc/bips.md</a> file.</p>

CC BY-SA 4.0
2022-01-24T23:37:42.290Z
Thanks for your answer Pieter - however, per my question the doc/bips.md file is unclear on when the BIP was adopted/merged by Bitcoin Core.
Ben
CC BY-SA 4.0
2022-01-24T23:50:45.093Z
Ah, you can look at the version numbers. 0.21.0, 0.21.1, and 22.0 were released in 2021. Note that the descriptor BIPs (380 and up) were mostly implemented in earlier versions, but only later turned into BIPs.
Pieter Wuille
CC BY-SA 4.0
2022-01-18T18:26:43.923Z
2022-01-18T18:26:43.923Z
Pieter Wuille
<blockquote>
<p>With taproot, a number of longstanding BIPs were merged into the Bitcoin standard client/consensus protocol - BIP341, BIP340, and BIP342.</p>
</blockquote>
<p>Bitcoin Core is an implementation of the Bitcoin protocol. It is considered by many as the reference implementation and is certainly the dominant implementation on the network at the time of writing.</p>
<p>According to <a href="https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki#specification-1" rel="nofollow noreferrer">BIP 2</a> a BIP can be in a FINAL/ACTIVE state. But this does not necessarily mean that a BIP is adopted in Bitcoin Core. Some BIPs (e.g. <a href="https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki" rel="nofollow noreferrer">BIP 39</a>) are proposed standards documents that have been implemented in the wider ecosystem but have not been implemented in Bitcoin Core.</p>
<p>There are three types of BIPs (Process, Informational, Standard) and even within say Standard BIPs they can vary from Consensus (soft fork) to Applications that may not be applicable to Bitcoin Core. BIP 340-342 were examples of Consensus (soft fork). Obviously Bitcoin Core needed to implement these features for these consensus changes to be activated on the network.</p>
<p>However, the state of each BIP isn't always up to date. For example Signet has been implemented in Bitcoin Core but is still in a Proposed state. So any count of BIPs in a FINAL/ACTIVE state wouldn't be an accurate representation of what has been &quot;adopted&quot; or &quot;merged into the standard client&quot;.</p>

CC BY-SA 4.0
2022-01-24T23:39:37.673Z
Thank you for the context around the state of the BIPs and their relation to the implementation.
Ben
CC BY-SA 4.0
2022-01-18T18:28:04.737Z
2022-01-18T18:28:04.737Z
Michael Folkson
<p>With taproot, a number of longstanding BIPs were merged into the Bitcoin standard client/consensus protocol - BIP341, BIP340, and BIP342. However, the <a href="https://github.com/bitcoin/bips" rel="nofollow noreferrer">Bitcoin repository BIPS index</a> is unclear on when a BIP has actually been 'adopted' and merged into the standard client.</p>
<p>Does anyone have suggestions on identifying which BIPs were implemented in bitcoin-core, and when?</p>

<bitcoin-core><bitcoin-core-development><bip>
How many BIPs were adopted in the standard client in 2021?
Ben
# How many BIPs were adopted in the standard client in 2021?

(Asked by: username_0 on 2022-01-18)

With taproot, a number of longstanding BIPs were merged into the Bitcoin standard client/consensus protocol - BIP341, BIP340, and BIP342. However, the [Bitcoin repository BIPS index](https://github.com/bitcoin/bips) is unclear on when a BIP has actually been 'adopted' and merged into the standard client.

Does anyone have suggestions on identifying which BIPs were implemented in bitcoin-core, and when?

**Tags:** bitcoin-core, bitcoin-core-development, bip


---

## 2 answers

### Answer by username_1 on 2022-01-18. Score: 6

BIPs are just proposals. Whether any particular piece of software supports/adopts it is up to the developers of that software.

To find out which BIPs are supported by Bitcoin Core specifically, look at its [doc/bips.md](https://github.com/bitcoin/bitcoin/blob/master/doc/bips.md) file.

> **Comments:**
> **username_0**: Thanks for your answer username_1 - however, per my question the doc/bips.md file is unclear on when the BIP was adopted/merged by Bitcoin Core.  
> **username_1**: Ah, you can look at the version numbers. 0.21.0, 0.21.1, and 22.0 were released in 2021. Note that the descriptor BIPs (380 and up) were mostly implemented in earlier versions, but only later turned into BIPs.  

---

### Answer by username_2 on 2022-01-18. Score: 0

> With taproot, a number of longstanding BIPs were merged into the Bitcoin standard client/consensus protocol - BIP341, BIP340, and BIP342.

Bitcoin Core is an implementation of the Bitcoin protocol. It is considered by many as the reference implementation and is certainly the dominant implementation on the network at the time of writing.

According to [BIP 2](https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki#specification-1) a BIP can be in a FINAL/ACTIVE state. But this does not necessarily mean that a BIP is adopted in Bitcoin Core. Some BIPs (e.g. [BIP 39](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki)) are proposed standards documents that have been implemented in the wider ecosystem but have not been implemented in Bitcoin Core.

There are three types of BIPs (Process, Informational, Standard) and even within say Standard BIPs they can vary from Consensus (soft fork) to Applications that may not be applicable to Bitcoin Core. BIP 340-342 were examples of Consensus (soft fork). Obviously Bitcoin Core needed to implement these features for these consensus changes to be activated on the network.

However, the state of each BIP isn't always up to date. For example Signet has been implemented in Bitcoin Core but is still in a Proposed state. So any count of BIPs in a FINAL/ACTIVE state wouldn't be an accurate representation of what has been "adopted" or "merged into the standard client".

> **Comments:**
> **username_0**: Thank you for the context around the state of the BIPs and their relation to the implementation.  

---

