Radium tree for Radium Core https://radiumcore.org
Switch branches/tags
Nothing to show
Clone or download
alaniz3 Merge pull request #3 from JJ12880/master
Improve speed of getblockbynumber RPC call
Latest commit 78d9fe1 Sep 6, 2017



Radium is a proof of stake cryptocurrency, forming the backbone of Radium SmartChain services.

To view the old Radium GitHub repository please click here.

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 MANDATORY Hard fork at block 682240 to implement fixed Average Fee code TESTNET Testing Canidate for MAINNET 1.4.5 code TESTNET Soft Update to test optimised Average Fee code.. TESTNET Hardforks TESTNET to Average Fee V2 code at block 164750. TESTNET Hardforks TESTNET back to old code to test stablility at block 160250. TESTNET Fixes issue that caused failure of Average Fee Fork. Has no effect on main net. MANDATORY Reverts the Average Fee Fork at block 626550 MANDATORY Implementts Average Fee Fork at block 619480


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'.