X13 - CK - Cryptocurrency - Encrypted Messaging - Long PoW
TypeScript C C++ Assembly Objective-C++ Python
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
share
src
.gitattributes
.gitignore
COPYING
INSTALL
README
README.md
ckcoin-qt.pro

README.md

CKcoin an X13 PoW and PoS Hybrid Cryptocurrency with Encrypted Messaging RPC Port: 41996 P2P Port: 40995 Algorithm: X13 POW/POS starts on block 1500000 Ticker: CK Max PoW Coins: Approx. ~30,000,248 CK 7% PoS Annual Interest

X13 Hashing Algorithm:(blake, bmw, groestl, jh, keccak, skein, luffa, cubehash, shavite, simd, echo, hamsi, fugue)

ckcoin-qt Features: Block Explorer Statistics AES 256-bit Encrypted Messaging X13 Algorithm

Block Reward Schedule: Block 1 is 2% (600,000 CK) Bittrex Swap Block Block 2-250 are 1 CK #low reward to prevent an instamine Block 251-1500000 are 20 CK PoW Ends on Block 1500000 (approx. ~2.8 years)

MinStakeAge: 24 hours, MaxStakeAge: Unlimited, 7% Annual Interest

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

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