Skip to content

BITRY/PRUX-Wallet

 
 

Repository files navigation

Prux Core [PRUX]

Prux

PRUX-Coin is a Cryptocurrency (similar to Bitcoin or Litecoin) but with fast transaction time of 27 seconds!!! PRUX is mineable along the Proof of work consensus mechanism, algorithme is scrypt. In addition PRUX is a very rare Altcoin. Fast Blocks, all 27 second, instant tx are possible. For a normal broadcast less than minutes. PRUX was developed because we were / are sorry for the eternal wait in a transaction. In addition, PRUX has only very few coins per new mined block, so it is very very very rare. On 31.??.2??? we have calculated total of 114375 PRUX mined!!!

License

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

Development and contributions – omg developers

Development is ongoing, and the development team, as well as other volunteers, can freely work in their own trees and submit pull requests when features or bug fixes are ready.

Version strategy

Version numbers are following major.minor.patch semantics.

Branches

There are 3 types of branches in this repository:

  • master: Stable, contains the latest version of the latest major.minor release.
  • maintenance: Stable, contains the latest version of previous releases, which are still under active maintenance. Format: <version>-maint
  • development: Unstable, contains new code for planned releases. Format: <version>-dev

Master and maintenance branches are exclusively mutable by release. Planned releases will always have a development branch and pull requests should be submitted against those. Maintenance branches are there for bug fixes only, please submit new features against the development branch with the highest version.

Contributions ✍️

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 of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

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.

YAY plz make pruxd/prux-cli/prux-qt

The following are developer notes on how to build Prux on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.

Such ports

  • RPC 19595
  • P2P 9595

Development tips and tricks

compiling for debugging

Run configure with the --enable-debug option, then make. Or run configure with CXXFLAGS="-g -ggdb -O0" or whatever debug flags you need.

debug.log

If the code is behaving strangely, take a look in the debug.log file in the data directory; error and debugging messages are written there.

The -debug=... command-line option controls debugging; running with just -debug will turn on all categories (and give you a very large debug.log file).

The Qt code routes qDebug() output to debug.log under category "qt": run with -debug=qt to see it.

testnet and regtest modes

Run with the -testnet option to run with "play pruxs" on the test network, if you are testing multi-machine code that needs to operate across the internet.

If you are testing something that can run on one machine, run with the -regtest option. In regression test mode, blocks can be created on-demand; see qa/rpc-tests/ for tests that run in -regtest mode.

DEBUG_LOCKORDER

Prux Core is a multithreaded application, and deadlocks or other multithreading bugs can be very difficult to track down. Compiling with -DDEBUG_LOCKORDER (configure CXXFLAGS="-DDEBUG_LOCKORDER -g") inserts run-time checks to keep track of which locks are held, and adds warnings to the debug.log file if inconsistencies are detected.

Packages

 
 
 

Languages

  • C++ 67.8%
  • Python 15.2%
  • C 10.2%
  • M4 2.6%
  • Makefile 1.5%
  • HTML 0.7%
  • Other 2.0%