qt: askpassphrasedialog: Clear pass fields on accept

[novacoin.git] / README.md

diff --git a/README.md b/README.md
index 92635bb..cc27b34 100644 (file)
--- a/README.md
+++ b/README.md
@@ -1,20 +1,23 @@
 
-Bitcoin integration/staging tree
+NovaCoin official development tree
+
+NovaCoin - a hybrid scrypt PoW + PoS based cryptocurrency.
+
+* 10 minutes stake spacing
+* 30 minutes PoW spacing
+* Balanced PoW blocks and stakes weighting
+* The PoW subsidy halves every x64 multiply of PoW difficulty
+* The PoS interest halves every x64 multiply of PoS difficulty
+* Maximum PoW reward is 100 coins
+* Maximum PoS reward is 10 coins
+* No deterministic limit of the supply, currently ~ 1411259 coins mined
 
 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
-bitcoin 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 (if they haven't already) on the mailing list:
-http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development
-
 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)
@@ -22,9 +25,17 @@ 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
-official, stable release versions of Bitcoin. If you would like to
-help test the Bitcoin core, please contact QA@BitcoinTesting.org.
+official, stable release versions of NovaCoin.
 
 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'.