digital currency
Switch branches/tags
Nothing to show
Clone or download
rubexmoney18 coin
coin
Latest commit 87cfdde May 25, 2018
Permalink
Failed to load latest commit information.
contrib coin Feb 26, 2018
doc coin Feb 26, 2018
share coin Feb 26, 2018
src coin May 25, 2018
COPYING coin Feb 26, 2018
INSTALL coin Feb 26, 2018
README.md coin May 25, 2018
rubex-qt.pro coin Feb 26, 2018

README.md

Rubex integration/staging tree

https://rubexmoney.com/

Copyright (c) 2009-2013 Bitcoin Developers Copyright (c) 2011-2013 Litecoin Developers

What is Rubex?

rpcport=9443 p2pport=9444

node1 =45.118.133.58 node2 =178.79.132.25 node3 =172.105.196.97

Rubex is a lite version of Bitcoin using scrypt as a proof-of-work algorithm.

  • 2.5 minute block targets
  • subsidy halves in 10000
  • 8cror total coins

The rest is the same as Bitcoin.

  • conditional coins per block
  • 2016 blocks to retarget difficulty

For more information, as well as an immediately useable, binary version of the Rubex client sofware, see https://rubexmoney.com/

License

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

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

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

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/coding.txt) or are controversial.

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

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test. Please be patient and help out, 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 for the core code are in src/test/. To compile and run them:

cd src; make -f makefile.unix test

Unit tests for the GUI code are in src/qt/test/. To compile and run them:

qmake BITCOIN_QT_TEST=1 -o Makefile.test bitcoin-qt.pro
make -f Makefile.test
./rubex-qt_test