PlexHive is a POW project supporting SHA256 PoW, Minotaurx CPU/POW and Hive Mining. For full details, as well as prebuilt binaries for Windows, Mac and Linux, please visit our website at https://plexhive.com.

PlexHive Core is the full node software that makes up the backbone of the PLHV network.

840 million total supply

2.5 minute block time

SHA256, MinotaurX (CPU), Hive mining options

No premine

Slow mining start (2000 blocks)

DarkGravity V3 difficulty adjustment

52658/52657 - RPC/P2P ports

Website www.plexhive.com

Block Explorer explorer.plexhive.com

Pool pool.plexhive.com

Discord https://discord.gg/GrvXQGtn

X @PlexHive_PLHV

Forum https://bitcointalk.org/

PlexHive Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

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

The contribution workflow is described in CONTRIBUTING.md.

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.

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/README.md.

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/test_runner.py

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

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.

Any translation corrections or expansions are welcomed as GitHub pull requests.