source

COPYING

@@ -0,0 +1,22 @@
+Copyright (c) 2014 BattleStake Developers
+Copyright (c) 2013-2014 NovaCoin Developers
+Copyright (c) 2011-2012 PPCoin Developers
+Copyright (c) 2009-2014 Bitcoin 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.

INSTALL

@@ -0,0 +1,9 @@
+Building BattleStake
+
+See doc/readme-qt.rst for instructions on building BattleStake QT,
+the intended-for-end-users, nice-graphical-interface, reference
+implementation of BattleStake.
+
+See doc/build-*.txt for instructions on building BattleStaked,
+the intended-for-services, no-graphical-interface, reference
+implementation of BattleStake.

README.md

@@ -0,0 +1,44 @@
+BattleStake development tree
+
+BattleStake is a PoS-based cryptocurrency.
+
+Features:
+* Symbol: BSTK
+* 60 second blocktime
+* Variable interest20-60%, based on the percentage of coins staking
+* 50000 ICO Coins
+* 0.0001 BSTK block reward respectively to keep chain moving if needed
+* 10000 PoW block limit
+* X11 PoW/PoS
+* Port: 9542
+* RPC Port: 9543
+* Dedicated Node: seed.battlestake.xyz
+
+
+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 BattleStake.
+
+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'.