BIPs that are implemented by Bitcoin Core (up-to-date up to v0.21.1):
BIP 9
: The changes allowing multiple soft-forks to be deployed in parallel have been implemented since v0.12.1 (PR #7575)BIP 11
: Multisig outputs are standard since v0.6.0 (PR #669).BIP 13
: The address format for P2SH addresses has been implemented since v0.6.0 (PR #669).BIP 14
: The subversion string is being used as User Agent since v0.6.0 (PR #669).BIP 16
: The pay-to-script-hash evaluation rules have been implemented since v0.6.0, and took effect on April 1st 2012 (PR #748).BIP 21
: The URI format for Bitcoin payments has been implemented since v0.6.0 (PR #176).BIP 22
: The 'getblocktemplate' (GBT) RPC protocol for mining has been implemented since v0.7.0 (PR #936).BIP 23
: Some extensions to GBT have been implemented since v0.10.0rc1, including longpolling and block proposals (PR #1816).BIP 30
: The evaluation rules to forbid creating new transactions with the same txid as previous not-fully-spent transactions were implemented since v0.6.0, and the rule took effect on March 15th 2012 (PR #915).BIP 31
: The 'pong' protocol message (and the protocol version bump to 60001) has been implemented since v0.6.1 (PR #1081).BIP 32
: Hierarchical Deterministic Wallets has been implemented since v0.13.0 (PR #8035).BIP 34
: The rule that requires blocks to contain their height (number) in the coinbase input, and the introduction of version 2 blocks has been implemented since v0.7.0. The rule took effect for version 2 blocks as of block 224413 (March 5th 2013), and version 1 blocks are no longer allowed since block 227931 (March 25th 2013) (PR #1526).BIP 35
: The 'mempool' protocol message (and the protocol version bump to 60002) has been implemented since v0.7.0 (PR #1641). As of v0.13.0, this is only available forNODE_BLOOM
(BIP 111) peers.BIP 37
: The bloom filtering for transaction relaying, partial Merkle trees for blocks, and the protocol version bump to 70001 (enabling low-bandwidth SPV clients) has been implemented since v0.8.0 (PR #1795). Disabled by default since v0.19.0, can be enabled by the-peerbloomfilters
option.BIP 42
: The bug that would have caused the subsidy schedule to resume after block 13440000 was fixed in v0.9.2 (PR #3842).BIP 61
: The 'reject' protocol message (and the protocol version bump to 70002) was added in v0.9.0 (PR #3185). Starting v0.17.0, whether to send reject messages can be configured with the-enablebip61
option, and support is deprecated (disabled by default) as of v0.18.0. Support was removed in v0.20.0 (PR #15437).BIP 65
: The CHECKLOCKTIMEVERIFY softfork was merged in v0.12.0 (PR #6351), and backported to v0.11.2 and v0.10.4. Mempool-only CLTV was added in PR #6124.BIP 66
: The strict DER rules and associated version 3 blocks have been implemented since v0.10.0 (PR #5713).BIP 68
: Sequence locks have been implemented as of v0.12.1 (PR #7184), and have been buried since v0.19.0 (PR #16060).BIP 70
71
72
: Payment Protocol support has been available in Bitcoin Core GUI since v0.9.0 (PR #5216). Support can be optionally disabled at build time since v0.18.0 (PR 14451), and it is disabled by default at build time since v0.19.0 (PR #15584). It has been removed as of v0.20.0 (PR 17165).BIP 90
: Trigger mechanism for activation of BIPs 34, 65, and 66 has been simplified to block height checks since v0.14.0 (PR #8391).BIP 111
:NODE_BLOOM
service bit added, and enforced for all peer versions as of v0.13.0 (PR #6579 and PR #6641).BIP 112
: The CHECKSEQUENCEVERIFY opcode has been implemented since v0.12.1 (PR #7524), and has been buried since v0.19.0 (PR #16060).BIP 113
: Median time past lock-time calculations have been implemented since v0.12.1 (PR #6566), and has been buried since v0.19.0 (PR #16060).BIP 125
: Opt-in full replace-by-fee signaling honoured in mempool and mining as of v0.12.0 (PR 6871). Enabled by default in the wallet GUI as of v0.18.1 (PR #11605)BIP 130
: direct headers announcement is negotiated with peer versions>=70012
as of v0.12.0 (PR 6494).BIP 133
: feefilter messages are respected and sent for peer versions>=70013
as of v0.13.0 (PR 7542).BIP 141
: Segregated Witness (Consensus Layer) as of v0.13.0 (PR 8149), defined for mainnet as of v0.13.1 (PR 8937), and buried since v0.19.0 (PR #16060).BIP 143
: Transaction Signature Verification for Version 0 Witness Program as of v0.13.0 (PR 8149), defined for mainnet as of v0.13.1 (PR 8937), and buried since v0.19.0 (PR #16060).BIP 144
: Segregated Witness as of 0.13.0 (PR 8149).BIP 145
: getblocktemplate updates for Segregated Witness as of v0.13.0 (PR 8149).BIP 147
: NULLDUMMY softfork as of v0.13.1 (PR 8636 and PR 8937), buried since v0.19.0 (PR #16060).BIP 152
: Compact block transfer and related optimizations are used as of v0.13.0 (PR 8068).BIP 155
: The 'addrv2' and 'sendaddrv2' messages which enable relay of Tor V3 addresses (and other networks) are supported as of v0.21.0 (PR 19954).BIP 158
: Compact Block Filters for Light Clients can be indexed as of v0.19.0 (PR #14121).BIP 159
: TheNODE_NETWORK_LIMITED
service bit is signalled as of v0.16.0 (PR 11740), and such nodes are connected to as of v0.17.0 (PR 10387).BIP 173
: Bech32 addresses for native Segregated Witness outputs are supported as of v0.16.0 (PR 11167). Bech32 addresses are generated by default as of v0.20.0 (PR 16884).BIP 174
: RPCs to operate on Partially Signed Bitcoin Transactions (PSBT) are present as of v0.17.0 (PR 13557).BIP 176
: Bits Denomination [QT only] is supported as of v0.16.0 (PR 12035).BIP 325
: Signet test network is supported as of v0.21.0 (PR 18267).BIP 339
: Relay of transactions by wtxid is supported as of v0.21.0 (PR 18044).BIP 340
341
342
: Validation rules for Taproot (including Schnorr signatures and Tapscript leaves) are implemented as of v0.21.0 (PR 19953), without mainnet activation.BIP 350
: Addresses for native v1+ segregated Witness outputs use Bech32m instead of Bech32 as of v0.21.1 (PR 20861).
LIPs implemented by Litecoin Core (up-to-date up to v0.21.3)
LIP002
: Extension blocks as a mechanism to implement new protocols to Litecoin without relaxing any consensus rules.LIP003
: Opt-in MimbleWimble through Extension Blocks.LIP004
: One sided MimbleWimble transactions without needing to build a transaction interactively with the receiving party.LIP006
: New p2p messages for supporting light-client syncing of MWEB components.