Migration from ProjectRadium

.gitattributes

@@ -0,0 +1 @@
+src/version.cpp export-subst

.gitignore

@@ -0,0 +1,26 @@
+src/*.exe
+src/radium
+src/radiumd
+src/test_radium
+src/build.h
+.*.swp
+*.*~*
+*.bak
+*.rej
+*.orig
+*.o
+*.patch
+.radium
+#compilation and Qt preprocessor part
+*.qm
+Makefile
+radium-qt
+#resources cpp
+qrc_*.cpp
+#qt creator
+*.pro.user
+#mac specific
+.DS_Store
+build
+
+!src/leveldb/Makefile

COPYING

@@ -0,0 +1,22 @@
+Copyright (c) 2014-2015 radium Developers
+Copyright (c) 2013-2014 NovaCoin Developers
+Copyright (c) 2011-2012 PPCoin Developers
+Copyright (c) 2009-2015 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 radium
+
+See doc/readme-qt.rst for instructions on building radium QT,
+the intended-for-end-users, nice-graphical-interface, reference
+implementation of radium.
+
+See doc/build-*.txt for instructions on building radiumd,
+the intended-for-services, no-graphical-interface, reference
+implementation of radium.

README

@@ -0,0 +1 @@
+README.md

README.md

@@ -0,0 +1,69 @@
+# Radium
+Radium is a proof of stake cryptocurrency, forming the backbone of Radium SmartChain services.
+
+Development Schedule
+===========================
+Development is primarily focused on Radium SmartChain services. Periodic maintence updates will be made to this repository.
+
+Version History
+===========================
+Latest MANDATORY for MAINNET is 1.4.5
+
+Latest MANDATORY for TESTNET is 1.4.5
+
+1.4.5.0 MANDATORY Hard fork at block 682240 to implement fixed Average Fee code
+
+1.4.4.5 TESTNET   Testing Canidate for MAINNET 1.4.5 code
+
+1.4.4.4 TESTNET   Soft Update to test optimised Average Fee code..
+
+1.4.4.3 TESTNET   Hardforks TESTNET to Average Fee V2 code at block 164750.
+
+1.4.4.2 TESTNET   Hardforks TESTNET back to old code to test stablility at block 160250. 
+
+1.4.4.1 TESTNET   Fixes issue that caused failure of Average Fee Fork. Has no effect on main net. 
+
+1.4.4.0 MANDATORY Reverts the Average Fee Fork at block 626550
+
+1.4.3.0 MANDATORY Implementts Average Fee Fork at block 619480
+
+
+Resources
+===========================
+Website: http://radiumcore.org
+
+Block Explorer 1: https://chainz.cryptoid.info/rads/
+
+Block Explorer 2: http://chain.blockpioneers.info/radium/index.php
+
+Radium ANN: https://bitcointalk.org/index.php?topic=1333026.0
+
+See our releases for Windows, Mac, and Linux client downloads.
+
+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 Radium.
+
+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'.