Skip to content
Version 1.0.0.6
C++ Makefile Python Assembly HTML C Other
Branch: master
Clone or download
tiranad Merge pull request #15 from btcdraft/draftcoin-1.0.0.6
Checkpoint update to block 700000
Latest commit f0137a8 Feb 24, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Build-Windows-Compile-Environment added How to build the Windows Compile Environment Dec 8, 2018
build Checkpoint update t0 block 700000 Feb 24, 2019
contrib Update installer.sh Apr 7, 2018
doc Branding updates Jan 9, 2018
share first commit May 26, 2015
src Checkpoint update t0 block 700000 Feb 24, 2019
COPYING Branding updates Jan 9, 2018
Dockerfile Added docker Jul 21, 2017
DraftCoin-qt Checkpoint update t0 block 700000 Feb 24, 2019
DraftCoin-qt.bak added Multisend / Stake4Charity Dec 8, 2018
DraftCoin-qt.pro Update DraftCoin-qt.pro Dec 12, 2018
DraftCoin.conf
INSTALL first commit May 26, 2015
Makefile Checkpoint update t0 block 700000 Feb 24, 2019
README first commit May 26, 2015
README.md first commit May 26, 2015
compile.sh Main 1.0.0.5 release Mar 28, 2018
docker-compose.yml Added docker Jul 21, 2017
qrc_bitcoin.cpp Checkpoint update t0 block 700000 Feb 24, 2019

README.md

DraftCoin development tree

DraftCoin is a PoS-based cryptocurrency.

Development process

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

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 they don't match the project's coding conventions (see coding.txt) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new stable release versions of DraftCoin.

Feature branches are created when there are major new features being worked on by several people.

From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.

Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled 'stale'.

You can’t perform that action at this time.