skip to Main Content
bitcoin
Bitcoin (BTC) $ 99,203.58 0.73%
ethereum
Ethereum (ETH) $ 3,278.70 2.31%
tether
Tether (USDT) $ 0.999814 0.09%
solana
Solana (SOL) $ 252.86 1.00%
bnb
BNB (BNB) $ 621.23 0.02%
xrp
XRP (XRP) $ 1.42 20.02%
dogecoin
Dogecoin (DOGE) $ 0.397686 3.32%
usd-coin
USDC (USDC) $ 0.999144 0.14%
cardano
Cardano (ADA) $ 0.96469 20.22%
staked-ether
Lido Staked Ether (STETH) $ 3,276.09 2.39%

Bitcoin Core’s CVE-2021-31876 Bug And Potential Complications

In this episode of “The Van Wirdum Sjorsnado,” the hosts discussed CVE-2021-31876, a bug in the Bitcoin Core code affecting replace-by-fee.

Watch This Episode On YouTube

Listen To This Episode:

  • Apple
  • Spotify
  • Google
  • Libsyn
  • Overcast

In this episode of “The Van Wirdum Sjorsnado,” hosts Aaron van Wirdum and Sjors Provoost discussed CVE-2021-31876, a bug in the Bitcoin Core code that affects replace-by-fee (RBF) child transactions.

The CVE (Common Vulnerabilities and Exposures) system offers an overview of publicly known software bugs. A bug in the Bitcoin Core code was recently discovered and disclosed by Antoine Riard, and added to the CVE overview.

Van Wirdum and Provoost explained that the bug affects how RBF logic is handled by the Bitcoin Core software. When one unconfirmed transaction includes an RBF flag (which means it should be considered replaceable if a conflicting transaction with a higher fee is broadcast over the network) any following transaction that spends coins from the original transaction should also be considered replaceable — even if the second transaction doesn’t itself have an RBF flag. Bitcoin Core software would not do this, however, which means the second transaction would in fact not be considered replaceable.

This is a fairly innocent bug; in most cases the second transaction will still confirm eventually, while there are also other solutions to speed confirmation up if the included fee is too low. But in very specific cases, like some fallback security mechanisms on the Lightning Network, the bug could in fact cause complications. Van Wirdum and Provoost tried to explain what such a scenario would look like — badly.

Loading data ...
Comparison
View chart compare
View table compare
Back To Top