No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Latest commit db06f8e May 9, 2018
Failed to load latest commit information.
contrib Initial Commit Mar 7, 2018
depends Initial Commit Mar 7, 2018
doc Initial Commit Mar 7, 2018
share Initial Commit Mar 7, 2018
src Initial Commit Mar 7, 2018
.gitignore Initial Commit Mar 7, 2018
.travis.yml Initial Commit Mar 7, 2018
COPYING Initial Commit Mar 7, 2018
README Rewording readme Mar 7, 2018 Update May 8, 2018 Initial Commit Mar 7, 2018


What is eBoost?

eBoost is an experimental in game digital currency created for users. eBoost allows for instant payments to anyone, anywhere in the world. eBoost was built on Litcoin core with modifications. eBoost uses peer-to-peer technology to operate with no central authority. Managing transactions and issuing money are carried out collectively by the network. eBoost Core is the name of the source software which enables the use of this currency. Originally forked from Litecoin

For more information about eBoost, visit


PoW Scrypt Cryptocurrency with ACP

100,000,000 Premined Coins

0 Block Reward

3 Minute Blocks (On Average)

60 Block Retarget Rate

RPC Port 5883

P2P Port 5884


eBoost Core is released under the terms of the MIT license. See for more information.

Development process

Future development work is managed by Jim Blasko ( and the eBoost Team.

If it is a simple/trivial/non-controversial change, then one of the eBoost development team members simply pulls it.

The master branch is regularly built and tested, but is not guaranteed to be completely stable.


Testing and code review is handled by Blaskoshi and eBoost Team.


Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translations may be converted to eBoost periodically.

Development tips, tricks, and FAQs

Official Nodes

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


eBoost 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.

Are there any changes to the serialization of blocks or transactions?

No. eBoost maintains the serialization of LTC to ensure easy compatibility with existing projects. There are also no changes to all of the following: the proof of work hash function (scrypt), block id hash function, transaction id hash function, cryptographic signature algorithm, the script language.