# Merge conflict

Source URL: https://help.blockstream.com/education/glossary/merge-conflict
Updated: 2026-05-26T17:23:05.000Z
Letter: M

---

A merge conflict in the context of Bitcoin occurs when two branches have made conflicting changes to the same code, and the version control system cannot automatically determine which change is correct.

For example, if one developer modifies a certain function in Bitcoin Core while another modifies the same function in a Bitcoin sidechain platform like Elements (which [Liquid](https://help.blockstream.com/education/glossary/liquid-network) is an implementation of). This requires manual review to ensure that the final Elements codebase is consistent, functional, and compatible with its Bitcoin Core counterpart.  
  
Merge conflicts are common in open-source projects like Bitcoin (and it's second-layer protocols) that have an independent, distributed network of developers. Good communication is key.

Navigation: Blockstream Help Center > Education > Glossary > Merge conflict

## Related Terms in This Letter
- [Mempool](https://help.blockstream.com/education/glossary/mempool)
- [Merge conflict](https://help.blockstream.com/education/glossary/merge-conflict) (current)
- [Merkle tree](https://help.blockstream.com/education/glossary/merkle-tree)
- [Mining](https://help.blockstream.com/education/glossary/mining)
- [Miniscript](https://help.blockstream.com/education/glossary/miniscript)
- [Mnemonic](https://help.blockstream.com/education/glossary/mnemonic)
- [Multi-part payments (MPP)](https://help.blockstream.com/education/glossary/multi-part-payments-mpp)
- [MuSig2](https://help.blockstream.com/education/glossary/musig2)