Radium Core/FAQs

A list of Frequently Asked Questions about the Radium SmartChain

Who are the developers for Radium?
Timothy Mesker: Founder and developer, MGR Project Radium, LLC

Justin J.: Founder and SmartChain developer, SmartChain Software Solutions, LLC

Alaniz: Radium Core Developer and Community Manager

Lamptoast: Assistant SmartChain Developer

Goblynn: Social Media and Beta Testing

BanzaiBTC: 3rd Party Support

Is the SmartChain Open Source?
No, for now it is a closed source project. Perhaps sometime in the future, the source will be published, but there are no current plans to release the source.

What platforms are supported?
The Radium Coin wallet is supported for Windows, Linux, and Mac.

The Radium SmartChain is supported for Windows. A version compatible with Mono is being planned, but is not currently a priority.

When will Radium be added to XYZ Exchange?
Nearly every respectable exchange does not comment on new coin additions. The development team does not know in advance of any exchange additions.

Is Radium Proof of Stake?
Yes.

Can Radium run on a Raspberry Pi?
Radium is an open source Proof Of Stake coin, and should compile and run on a Raspberry Pi.

Was there a Premine/Instamine for the Radium Coin?
No. The coin was launched in May 2015. There was an approximately 2 week Scrypt Proof of Work period, followed by decreasing PoS rewards. The PoS reward has recently declined to 0.75 coins per block plus Spread Fees.

Will it become too expensive to use the Radium SmartChain if the price of Radium goes up?
No. If/When this becomes an issue, there is code in place to adjust the cost per operation, if need be.

Do you use OP_RETURN to encode the data?
No. The current protocol encodes the data into fake public keys.

How many connections should I have?
Wallet connections is a question that comes up pretty frequently, so lets here is a brief explanation!

TL:DR: More than 3 is good. You can not have more than 16 outgoing connections, but you may get more if other nodes connect to you.

In order for the wallet to work correctly, it needs to have a MINIMUM of one connection. A wallet can work perfectly fine, using only one high quality connection to the network. It is desired that a wallet have more than one connection in case your one connection is of low quality. A total of three to five connections is more than enough for the wallet to work correctly.

But arnt more connections better?

Well, it CAN be, in terms of the health of the entire network, however after 3-5 connections there really is little improvement in wallet function. Each connection requires resources to maintain, and the more connections you have the harder your computer will need to work in order to communicate with all the other nodes. Once your wallet has a stable connection to the network, more connections will not increase the speed or improve staking.

I have 16, BUT I WANT MORRRR!

Well, then, be patient. First, connections require more CPU power for the connected wallets. There are two types of connections used by the wallet, outgoing and incoming. An outgoing is established when your wallet reaches out and initiates a connection to another node. An incoming connection occurs when someone else connects to you. There is a hard coded limit of 16 outgoing connections, so that your wallet does not create more work for more nodes than necessary. To help new wallets gain connections even if your already have 16, the incoming connection default limit is set at 125. This means your wallet can not ask for more than 16 connections, but it can accept more connections from other nodes with low connection counts. In summary, only way to get more than 16 connections is to have your wallet open for a long period of time and allow other new nodes to connect to you.