Skip to content
No description, website, or topics provided.
C++ Python HTML C Roff Shell Other
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

GitHub Logo

Twitcoin integration/staging tree

Copyright (c) 2009-2014 Bitcoin Developers
Copyright (c) 2011-2014 Litecoin Developers
Copyright (c) 2018 Twitcoin Developers

What is Twitcoin?

GitHub Logo
Coin Name: Twitcoin
Ticker: TWIT
Algorithm: Scrypt
Type: PoW

Maximum Coin Supply: 330.000.000
Premine: 33.000.000
Useage: Team, Airdrops, Bounties (Marketing, Design, Etc.)

Block time: 30 seconds
Maturity: 30 Blocks
Difficulty Re-adjustment: 330 Blocks

Block rewards:
Phase 1 - Premine (Block 1) 33.000.000 TWIT
Phase 2 - PoW (Block 2-1337) .50 TWIT
Phase 3 - PoW (Block 1338+) 30 TWIT

For more information, as well as an immediately useable, binary version of the Twitcoin client sofware, see


Twitcoin is released under the terms of the MIT license. See COPYING for more information or see

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 Twitcoin 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 with the devs and community.

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


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
make -f Makefile.test
You can’t perform that action at this time.