Skip to content

Commit c1d557f

Browse files
committed
Merge pull request #1 from terrytibbs/master
Update readme.md for Litecoin.
2 parents 3a6e468 + 819842d commit c1d557f

File tree

1 file changed

+9
-14
lines changed

1 file changed

+9
-14
lines changed

README.md

Lines changed: 9 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,8 @@
1-
2-
Bitcoin integration/staging tree
1+
Litecoin - a lite version of Bitcoin optimized for CPU mining using scrypt as a proof of work scheme.
2+
- 2.5 minute block targets
3+
- 504 blocks to retarget
4+
- subsidy halves in 840k blocks (~4 years)
5+
- 84 million total coins
36

47
Development process
58
===================
@@ -8,12 +11,7 @@ Developers work in their own trees, then submit pull requests when
811
they think their feature or bug fix is ready.
912

1013
If it is a simple/trivial/non-controversial change, then one of the
11-
bitcoin development team members simply pulls it.
12-
13-
If it is a more complicated or potentially controversial
14-
change, then the patch submitter will be asked to start a
15-
discussion (if they haven't already) on the mailing list:
16-
http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development
14+
litecoin development team members simply pulls it.
1715

1816
The patch will be accepted if there is broad consensus that it is a
1917
good thing. Developers should expect to rework and resubmit patches
@@ -22,8 +20,8 @@ or are controversial.
2220

2321
The master branch is regularly built and tested, but is not guaranteed
2422
to be completely stable. Tags are regularly created to indicate new
25-
official, stable release versions of Bitcoin. If you would like to
26-
help test the Bitcoin core, please contact QA@BitcoinTesting.org.
23+
official, stable release versions of Litecoin. If you would like to
24+
help test the Bitcoin core, please contact one of the OPs at #litecoin on irc.freenode.net.
2725

2826
Feature branches are created when there are major new features being
2927
worked on by several people.
@@ -36,7 +34,4 @@ in this manner will have their corresponding issue labeled 'stagnant'.
3634

3735
Issues with no commits will be given a similar warning, and closed after
3836
15 days from their last activity. Issues closed in this manner will be
39-
labeled 'stale'.
40-
41-
Requests to reopen closed pull requests and/or issues can be submitted to
42-
QA@BitcoinTesting.org.
37+
labeled 'stale'.

0 commit comments

Comments
 (0)