Skip to content
XPChain Core integration/staging tree
Branch: master
Clone or download
Pull request Compare This branch is 489 commits ahead, 2147 commits behind bitcoin:master.
Latest commit b289960 Apr 2, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Rewrite for XPChain Feb 19, 2019
.tx tx: Update transifex slug 016x→017x Aug 2, 2018
build-aux/m4 rename from bitcoin-qt to xpchain-qt Aug 29, 2018
contrib Replace bitcoin with xpchain Feb 3, 2019
depends Update dependencies docs for XPChain Dec 23, 2018
share Add build number to filename of installer Apr 1, 2019
src Fix IsDestinationSame Apr 1, 2019
test Merge pull request #81 from mban259/hotfix/fix_for_dup_txin Mar 31, 2019
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore Added Dockerfile and compose sample file. Jan 15, 2019
.travis.yml change flake8 version Oct 28, 2018 Update contribution documents for XPChain Dec 23, 2018
COPYING Update copyright year in COPYING Mar 31, 2019
Dockerfile Remove bench_bitcoin and test_bitcoin from Dockerfile Feb 2, 2019 Merge #3: Preparing for release (0.17.0-3) Mar 31, 2019
docker-compose.yml.sample Tweak publish port settings. Jan 18, 2019 rename libbitcoinconsensus to xpchain Aug 29, 2018

XPChain Core integration/staging tree

Build Status

What is XPChain?

XPChain, which is usually abbreviated XPC, is a cryptocurrency based on Bitcoin 0.17.0.

XPChain introduces new proof-of-stake consensus as a security model, which solves “nothing at stake” issue in a way proposed by Peercoin community, and enables you to distribute your staking rewards to anyone in the world.

XPChain Core is the name of open source software which enables the use of this currency.

For more information, read the original whitepaper.

For Exchanges

  • The amounts of XPChain in any transaction must be decimals to at most 4 places, while those of Bitcoin are ones to up to 8 places. If you try to generate a transaction, which contains the amount that is a decimal to more than 4 places, an error will occur.
  • Make sure you put no restrictions on the length of withdrawal addresses. Addresses of XPChain can be around 75 characters. Nothing would probably go wrong if you support the latest Bitcoin's address generation.
  • Use native Segwit (bech32) addresses instead of legacy addresses, which enables you to send XPC to either legacy, native Segwit, P2SH-Segwit, or P2WSH addresses.
  • You can be sent XPC that cannot be spent in next 100 blocks, because XPChain wallet has the function of sending proof-of-stake reward to arbitrary addresses and its users can easily transfer their reward to an exchange's deposit address.
  • Make sure your wallet is running with -minting=0 to disable minting. When you mint a block with your customer's funds, you receive a transaction of ‘payment to yourself’ (called ‘coinstake’ or ‘age-burn’ transaction) as well as a coinbase transaction. This would cause incorrect double depositing if your deposit system were to monitor only payments to the customer's deposit addresses.


XPChain Core is released under the terms of the MIT license. See COPYING for more information or see

Development Process

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of XPChain Core.

The contribution workflow is described in


Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/

The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.


While Bitcoin has their Transifex page, XPChain doesn't have such pages of external translation web service (e.g. Transifex or Crowdin). If you want to make some change as well as add new translations, just create a new GitHub pull request to whose title is prefixed “Translation:”. Read for details.

You can’t perform that action at this time.