Skip to content
Branch: master
Clone or download
Latest commit c2e23c2 Mar 6, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx
build-aux/m4 Initial Release Mar 6, 2018
contrib Initial Release Mar 6, 2018
corez-docs
depends
doc
qa
share Initial Release Mar 6, 2018
src Initial Release Mar 6, 2018
.gitignore
.travis.yml
CONTRIBUTING.md
COPYING Initial Release Mar 6, 2018
INSTALL Initial Release Mar 6, 2018
LICENSE
Makefile.am
README.md
autogen.sh Initial Release Mar 6, 2018
configure.ac Initial Release Mar 6, 2018
libbitcoinconsensus.pc.in

README.md

CoreZ Core staging tree 0.12.1

https://www.corez.site

What is CoreZ?

CoreZ (CRZ) is an innovative cryptocurrency. A form of digital currency secured by cryptography and issued through a decentralized and advanced mining market. Based on Dash, it's an enhanced and further developed version, featuring the masternode technology with 50% Reward, near-instant and secure payments as well as anonymous transactions. CoreZ has great potential for rapid growth and expansion. Based on a total Proof of Work and Masternode system, it is accesible to everyone, it ensures a fair and stable return of investment for the Graphics Processing Units (GPUs) miners and the Masternode holders.

Additional information, wallets, specifications & roadmap: https://bitcointalk.org/index.php?topic=3064429.0

License

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

Development Process

The master branch is meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of CoreZ Core.

The contribution workflow is described in CONTRIBUTING.md.

Testing

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.

Automated Testing

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

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

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

Manual Quality Assurance (QA) Testing

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.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.