Bitcoin ABC aims to scale Bitcoin Cash to handle the payments needs of billions of daily users. We must scale, and there is no time to waste. The competition is not waiting, and we must reach the market first, or risk irrelevance.
Every design choice that Bitcoin ABC makes to support the P2P electronic cash vision is a design choice that takes us away from the Bitcoin Core model and lessens our ability to inexpensively leverage the Bitcoin Core workforce and their backports.
Still Limited by Bitcoin Core
Yes, currently, due to Bitcoin ABC being underfunded, we spend about 90% of developer time just keeping Bitcoin Cash secure, running and updated. As such, we rely on code backports — the copying of open-source code – from Bitcoin Core.
Because of this, Bitcoin Cash even now, 2.5 years after the 2017 fork that created BCH, remains hampered by Bitcoin Core’s digital-gold, anti-scaling technical vision and decisions.
The Cost of Change
For every change made to the Bitcoin ABC codebase, there is a corresponding cost not just for that change, but also for the peer review, revisions prior to commits, future Bitcoin Core backports, testing, and maintenance.
In order to realize the Bitcoin Cash vision and improve BCH as peer-to-peer electronic cash, Bitcoin Cash needs to chart its own path and establish its own technical leadership.
Even when changes are small, they can result in medium- and long-term ongoing expenses. Once assumed, these expenses can not be merely undone. They must be factored into the long-term cost of building and maintaining Bitcoin Cash infrastructure.
Lack of adequate and sustained funding for Bitcoin ABC is a blocking issue on this front. This is an issue our business plan solves, with your support.
Join us in building censorship-resistant P2P electronic cash for billions of daily users and realizing the vision that is Bitcoin Cash!
Visit fund.bitcoinabc.org to find our business plan, budget, delivery timeline, funding options and feedback mechanisms.
We can only do this together.
Are you in?
Got questions? Ask us below.