Permalink
Browse files

Initial Update

I just made a github guide.
  • Loading branch information...
HowToCloneAnAltcoin
HowToCloneAnAltcoin committed Nov 4, 2014
0 parents commit 859ce7a362e93f4147c7efc38cc78276ba4c1a3e
Showing 604 changed files with 244,422 additions and 0 deletions.
@@ -0,0 +1 @@
src/version.cpp export-subst
@@ -0,0 +1,34 @@
src/*.exe
src/litecoin
src/litecoind
src/test_litecoin
.*.swp
*.*~*
*.bak
*.rej
*.orig
*.o
*.patch
.litecoin
# Compilation and Qt preprocessor part
*.qm
Makefile
litecoin-qt
Litecoin-Qt.app
# Unit-tests
Makefile.test
litecoin-qt_test
# Resources cpp
qrc_*.cpp
# Qt creator
*.pro.user
# Mac specific
.DS_Store
build
!src/leveldb*/Makefile
20 COPYING
@@ -0,0 +1,20 @@
Copyright (c) 2009-2014 Bitcoin Developers
Copyright (c) 2011-2014 Litecoin Developers
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
@@ -0,0 +1,9 @@
Building Litecoin
See doc/readme-qt.rst for instructions on building Litecoin-Qt,
the intended-for-end-users, nice-graphical-interface, reference
implementation of Litecoin.
See doc/build-*.txt for instructions on building litecoind,
the intended-for-services, no-graphical-interface, reference
implementation of Litecoin.
@@ -0,0 +1,73 @@
Litecoin integration/staging tree
================================
http://www.litecoin.org
Copyright (c) 2009-2014 Bitcoin Developers
Copyright (c) 2011-2014 Litecoin Developers
What is Litecoin?
----------------
Litecoin is a lite version of Bitcoin using scrypt as a proof-of-work algorithm.
- 2.5 minute block targets
- subsidy halves in 840k blocks (~4 years)
- ~84 million total coins
The rest is the same as Bitcoin.
- 50 coins per block
- 2016 blocks to retarget difficulty
For more information, as well as an immediately useable, binary version of
the Litecoin client sofware, see http://www.litecoin.org.
License
-------
Litecoin 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 Litecoin
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](https://github.com/litecoin-project/litecoin/tags) are created
regularly to indicate new official, stable release versions of Litecoin.
Testing
-------
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 bitcoin-qt.pro
make -f Makefile.test
./litecoin-qt_test
Oops, something went wrong.

0 comments on commit 859ce7a

Please sign in to comment.