Skip to content
Particl Core integration/staging tree
Branch: master
Clone or download
Pull request Compare This branch is 1200 commits ahead of bitcoin:master.
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Merge branch 'bitcoin' into particl_dev Jan 3, 2019
.travis Merge branch 'bitcoin' into particl_dev Apr 9, 2019
.tx qt: Pre-0.18 split-off translations update Feb 4, 2019
build-aux/m4 Merge branch 'bitcoin' into particl_dev Feb 15, 2019
build_msvc bench: Add wallet_balance benchmarks Apr 15, 2019
contrib Merge branch 'bitcoin' into particl_dev Apr 20, 2019
depends Merge branch 'bitcoin' into particl_dev Apr 9, 2019
share Merge branch 'bitcoin' into particl_dev Mar 12, 2019
src Merge branch 'bitcoin' into particl_dev Apr 20, 2019
test Merge branch 'bitcoin' into particl_dev Apr 20, 2019
.appveyor.yml appveyor: Don't build debug libraries instead of "build and delete" Feb 28, 2019
.cirrus.yml cirrus ci: Inital config Feb 3, 2019
.editorconfig unpassing categories Oct 25, 2017
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.python-version .python-version: Specify full version 3.5.6 Mar 2, 2019
.style.yapf test: .style.yapf: Set column_limit=160 Mar 4, 2019
.travis.yml Merge branch 'bitcoin' into particl_dev Apr 16, 2019 Merge branch 'bitcoin' into particl_dev Mar 21, 2019
COPYING Merge branch 'bitcoin' into particl_dev Jan 1, 2019 Update INSTALL landing redirection notice for build instructions. Oct 5, 2016 Merge branch 'bitcoin' into particl_dev Feb 15, 2019 Add "export LC_ALL=C" to all shell scripts Jun 14, 2018 Merge branch 'bitcoin' into particl_dev Mar 5, 2019

Particl Core integration/staging tree

Build Status

What is Particl?

An open source, decentralized privacy platform built for global person to person eCommerce.

For more information, as well as an immediately useable, binary version of the Particl Core software, see

Getting Started

A new Particl wallet will need an HD master key loaded and an initial account derived before it will be functional.

The GUI programs will guide you through the initial setup.

It is recommended to use a mnemonic passphrase. To generate a new passphrase see the mnemonic rpc command. Loading the new mnemonic with the extkeyimportmaster command will setup the master HD key and first account.

To create an initial new HD master key and account from random data, start particld or particl-qt with the parameter: -createdefaultmasterkey.

Remember to backup your passphrase and/or wallet.dat file!


Particl 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 Particl Core.

The contribution workflow is described in and useful hints for developers can be found in doc/


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.

You can’t perform that action at this time.