Skip to content
No description, website, or topics provided.
C++ C M4 Python Shell HTML Other
Branch: master
Clone or download
Pull request Compare This branch is 60 commits ahead of MiniblockchainProject:master.
Latest commit c573f33 Oct 29, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build-aux/m4
contrib Initial commit Jul 28, 2014
doc Initial commit Jul 28, 2014
qa Initial commit Jul 28, 2014
share
src Seeds update Oct 29, 2018
.gitattributes
.gitignore Initial commit Jul 28, 2014
COPYING Initial commit Jul 28, 2014
INSTALL
Makefile.am Qt5.11 compat and Windows improvements. (#9) Jun 12, 2018
README.md Added line break after MBC copyright Oct 26, 2014
autogen.sh Qt5.11 compat and Windows improvements. (#9) Jun 12, 2018
buildwin32.sh Initial commit Jul 28, 2014
configure.ac Boost 1.54 compat (#12) Jul 5, 2018
foo.cpp Initial commit Jul 28, 2014
pkg.m4 Initial commit Jul 28, 2014

README.md

Cryptonite Core integration/staging tree

http://cryptonite.info

Copyright (c) 2014 The Mini-blockchain Project
Copyright (c) 2009-2014 Bitcoin Core Developers

What is Cryptonite

Cryptonite (also known as Crypton) is the first cryptocurrency to implement the mini-blockchain scheme along with many other innovative features. Cryptonite is a fork of the Bitcoin core but the code has been extensively modified and expanded upon. Innovative new features include withdrawal limits and unmalleable transactions. The mini-blockchain scheme alleviates the blockchain bloat problem and therefore allows superior support for micro-transactions and arbitrary data to be stored in the blockchain.

For more information see http://cryptonite.info

License

Cryptonite Core 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 Cryptonite 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).

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.md) or are controversial.

Testing

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

Every pull request is built for both Windows and Linux on a dedicated server, and unit and sanity tests are automatically run.

Manual Quality Assurance (QA) Testing

Large changes should have a test plan, and should be tested by somebody other than the developer who wrote the code.

You can’t perform that action at this time.