Back to blog

Parity Bitcoin is now supporting SegWit, SegWit2x and Bitcoin Cash

The Parity Bitcoin client (pbtc), released in April this year, is a full-node implementation of the Bitcoin protocol written in Rust. Our team is thrilled to announce its recent upgrade that includes support for SegWit (https://segwit.org/), SegWit2x (https://segwit2x.github.io/) and Bitcoin Cash (https://www.bitcoincash.org/).

Parity Bitcoin does not favor any scaling approach or any chain fork rule over another; at the same time, users of Parity Bitcoin can decide which version of Bitcoin they wish to run. However, Parity Bitcoin defaults to the Bitcoin (BTC) chain with the majority of hashrate with SegWit enabled (UASF). Users supporting user activated hard-fork (UAHF) can use the --bitcoin-cash flag to synchronize the Bitcoin Cash (BCH) chain. In addition, the client allows support for SegWit2x by passing the --segwit2x parameter.

Parity Bitcoin is published under a GPLv3 open-source license which encourages developers to contribute new features to the rustlang-based software stack. The strict copyleft license does not only allow organizations and companies to use and modify the code, but also enforces code changes to be contributed back to the open source community.

Parity Technologies is excited to support the Bitcoin community and utilize Bitcoin in upcoming projects, we will keep you posted on our blog!

Parity Bitcoin can be downloaded on GitHub: https://github.com/paritytech/parity-bitcoin/

If you have any questions or comments, write us: [email protected] or join our Gitter channel: https://gitter.im/paritytech/parity

Read more

  • On Classes of Stuck Ether and Potential Solutions

    A Brief History

    Since Ethereum went live two and a half years ago, users and developers have often struggled with the usability and building on this new ‘Frontier’ of development.

    The issues began almost immediately as the first users of Ethereum had to grapple with a command line interface that was extremely unforgiving of mistakes.

  • A Postmortem on the Parity Multi-Sig Library Self-Destruct

    On Monday November 6th 2017 02:33:47 PM UTC, a vulnerability in the “library” smart contract code, deployed as a shared component of all Parity multi-sig wallets deployed after July 20th 2017, was found by an anonymous user. The user decided to exploit this vulnerability and made himself the “owner” of the library contract. Subsequently, the user destructed this component.

  • Parity Technologies Multi-Sig Wallet Issue Update

    This week, as has been widely reported, a vulnerability in the Parity Wallet library contract of the standard multi-sig contract was found by an anonymous user. This user managed to gain access to the smart contract, effectively making themselves the owner of the contract.

Back to blog