Bitcoin Core integration/staging tree (by bitcoin)

Bitcoin Alternatives

Similar projects and alternatives to bitcoin
  • bips

    Bitcoin Improvement Proposals

  • sips

    Community-submitted Stacks Improvement Proposals (SIPs)

  • original-bitcoin

    This is a historical repository of Satoshi Nakamoto's original bitcoin sourcecode

  • 30-seconds-of-code

    Short JavaScript code snippets for all your development needs

  • bitcoinbook

    Mastering Bitcoin 2nd Edition - Programming the Open Blockchain

  • Tasmota

    Alternative firmware for ESP8266 with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at

  • croc

    Easily and securely send things from one computer to another :crocodile: :package:

  • Server


  • jdk

    JDK main-line development

  • ciphey

    ⚡ Automatically decrypt encryptions without knowing the key or cipher, decode encodings, and crack hashes ⚡

  • btcd

    An alternative full node bitcoin implementation written in Go (golang)

  • linuxupskillchallenge

    Learn the skills required to sysadmin a remote Linux server from the commandline.

  • eleventy-high-performance-blog

    A high performance blog template for the 11ty static site generator.

  • a32nx

    The A32NX Project is a community driven open source project to create a free Airbus A320neo in Microsoft Flight Simulator that is as close to reality as possible. It aims to enhance the default A320neo by improving the systems depth and functionality to bring it up to payware-level, all for free.

  • neutrino

    Privacy-Preserving Bitcoin Light Client

  • clifford

    Geometric Algebra for Python

  • Bitcoin-Spec

    Bitcoin Developer Reference

  • P2P-Trading-Exchanges

    Person-to-Person bitcoin Trading Exchanges

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better alternative or higher similarity.


Posts where bitcoin has been mentioned. We have used some of these posts to build our list of alternatives and similar projects.
  • Bitcoin is decentralized. However, I assume there’s developers who have access to code? What if they decide to change it? Quite a responsibility given for a few unknown developers? | 2021-01-17
    Yes, anyone can change the code. One way to do this is to go to, click Clone, and now you can change any row of code you want. Now release your version and lets see how many people run your code.
  • About block size controversy
  • Bitcoin Core 0.21.0 Released: What’s New | 2021-01-16
    The current plan is to stop being able to use a Legacy wallet in 27.0 (~2023). However you will still be able to migrate a Legacy wallet to a descriptor wallet in that and future versions. This migration will work independently of the legacy wallet support so it will remain for a long time. | 2021-01-16
    You can see the review work in action here:
  • What is required to become a Bitcoin core Developer ? | 2021-01-15
    You can start by reviewing pull requests and helping to test them. See Contributing to Bitcoin Core. Code is mainly C++, tests are written in Python. But even without much code skills, you can still help by testing, fixing typos, improving documentation, etc.
  • Fred Wilson: Smart Contracts on Bitcoin | 2021-01-15
    The first comment in the pull request is: "The maximum size for OP_RETURN outputs used to be 80 bytes, then got changed to 40 bytes to be on the safe side. We have now been running with 40 bytes for about 9 months, and nothing catastrophic happened to the Blockchain, so I am proposing to increase it back to 80 bytes."

    The commit that is referenced by this comment is "script: reduce OP_RETURN standard relay bytes to 40" | 2021-01-15
    What do you mean by "originally"? It looks like it was introduced as 80 bytes here, so it had only been 80 bytes for a year or so: | 2021-01-15
    Your Coindesk source is wrong, the limit was never lowered.

    Here is the commit where it was raised from 40 to 80:

    If you believe if was ever lowered, show me the commit.

    The Coindesk articles contains the phrase "OP_RETURN was originally meant to store 80 bytes of extra data in a bitcoin transaction". How do they know what it was originally meant to do? If it meant to do it, why wasn't it in the source?

  • [bitcoin-core-dev] Bitcoin Core 0.21.0 released | 2021-01-14
  • Interesting How The Narrative Changed Over The | 2021-01-13
    Since Bitcoin’s early days, one of the challenges of developing lightweight clients with SPV security has been finding a way for the client to download transactions affecting its wallet without giving the third party server providing the transactions the ability to track the wallet’s receiving and spending history. An initial attempt at this was BIP37-style bloom filters, but the way wallets used them ended up providing only minimal privacy and created denial of service risks for the full nodes that served them. An anonymous developer posted to the Bitcoin-Dev mailing list in May 2016 suggesting an alternative construction of a single bloom filter per block that all wallets could use. The idea was quickly refined, implemented, and specified, becoming the BIP157 and BIP158 specifications of compact block filters. This can significantly improve the privacy of lightweight clients, although it does increase their bandwidth, CPU, and memory requirements compared to current popular methods. For full nodes, it reduces the DoS risk to that of a simple bandwidth exhaustion attack, which nodes can already address with bandwidth throttling options. Although merged on the server side in btcd in 2018 and proposed for Bitcoin Core around the same time, 2020 saw the P2P part of the protocol merged piecewise into Bitcoin Core in May through August, culminating with the ability for a node operator to opt in to creating and serving compact block filters by enabling just two configuration options. | 2021-01-13
    The Bitcoin Core project merged several PRs in May and the following months that improved transaction origin privacy, both for users of the Bitcoin Core wallet and for users of other systems. Bitcoin Core #18038 began tracking whether at least one peer had accepted a locally-generated transaction, allowing the wallet to significantly reduce the frequency Bitcoin Core used to rebroadcast its own transactions and making it harder for surveillance nodes to identify which node originated the transaction. PRs #18861 and #19109 were able to block a type of active scanning by surveillance nodes by only replying to requests for a transaction from peers the node told about the transaction, further reducing the ability of third parties to determine which node first broadcast a transaction. PRs #14582 and #19743 allow the wallet to automatically try to eliminate address reuse links when it wouldn’t cost the user any extra fees (or, alternatively, allowing the user to specify the maximum extra they’re willing to spend in order to eliminate such links).
  • Main Consensus Forks of Bitcoin (January 2021 update) | 2021-01-12
    It was merged into Bitcoin Core in late 2015: | 2021-01-12
    I wouldn't be so hard. Core developers maintained their software, developed PSBT and useful things like that. And there's the Schnorr/Taproot upgrade that should be be activated in the coming year (Mark Lunderberg used their work to implement Schnorr on Bitcoin Cash).
  • Every Wednesday there is a hosted Bitcoin Core Pull Request Review Club on IRC. All welcome to join. Tomorrow's topic: PR19825 - Simpler setban and new ban manipulation commands | 2021-01-12
    What’s the benefit for participants? Reviewing and testing PRs is the best way to start contributing to Bitcoin Core, but it’s difficult to know where to start. There are hundreds of open PRs, many require a lot of contextual knowledge, and contributors and reviewers often use unfamiliar terminology. The review club will give you the tools and knowledge you need in order to take part in the Bitcoin Core review process on GitHub.
  • Node
    You can track releases here:


Basic bitcoin repo stats
6 days ago

bitcoin/bitcoin is an open source project licensed under MIT License which is an OSI approved license.