Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
autom4te.cache first commit May 29, 2016
contrib first commit May 29, 2016
dist first commit May 29, 2016
doc first commit May 29, 2016
share first commit May 29, 2016
COPYING first commit May 29, 2016
Makefile first commit May 29, 2016
aclocal.m4 first commit May 29, 2016
configure first commit May 29, 2016
pkg.m4 first commit May 29, 2016

Vaperscoin Core [VPRC]



Build Status tip for next commit

What is Vaperscoin?

Vaperscoin is a cryptocurrency like Bitcoin, although it does not use SHA256 as its proof of work (POW). Taking development cues from Tenebrix and Litecoin, Vaperscoin currently employs a simplified variant of scrypt.

  • Total coins: 42 750 000 000
  • Initial subsidy: 7500
  • Block target: 60 seconds
  • Port: 4444
  • RPC port: 4455
  • Testnet port: 14444
  • RPC testnet port: 14455


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

Development and contributions

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.


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.


Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.

Periodically the translations are pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

If the changes are Vaperscoin specific, they can be submitted as pull request against this repository. If it is a general translation, consider submitting it through upstream, as we will pull these changes later on.

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.


If the code is behaving strangely, take a look in the debug.log file in the data directory; error and debugging message 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 vaperscoins" 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 -regest mode.


Vaperscoin 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 what locks are held, and adds warning to the debug.log file if inconsistencies are detected.

You can’t perform that action at this time.