Difference between revisions of "Upgrade to RandomX"

From BiblePay Wiki
Jump to: navigation, search
(Created page with "''' Upgrading to 1.5.0.7 - RandomX ''' On March 24th, 2020, BiblePay will be transitioning to the RandomX algorithm. This upgrade is a major release therefore we need to exp...")
 
Line 2: Line 2:
  
 
On March 24th, 2020, BiblePay will be transitioning to the RandomX algorithm.  This upgrade is a major release therefore we need to explain some finer technical details that may not be apparent so we can help you upgrade.
 
On March 24th, 2020, BiblePay will be transitioning to the RandomX algorithm.  This upgrade is a major release therefore we need to explain some finer technical details that may not be apparent so we can help you upgrade.
 +
  
  
Line 10: Line 11:
 
Note the part about compiling RandomX.  This is an easy step, and is only required once.  In general, a person compiling BiblePay will cd to the "depends" directory, compile depends as usual, then back out, cd to RandomX, compile randomX, then back out and compile the coin.   
 
Note the part about compiling RandomX.  This is an easy step, and is only required once.  In general, a person compiling BiblePay will cd to the "depends" directory, compile depends as usual, then back out, cd to RandomX, compile randomX, then back out and compile the coin.   
 
Additionally, our github URL has changed to:  https://github.com/biblepay/biblepay    (however, we have integrated an automatic redirect in our old URL so as to not break any old scripts).
 
Additionally, our github URL has changed to:  https://github.com/biblepay/biblepay    (however, we have integrated an automatic redirect in our old URL so as to not break any old scripts).
 +
  
  
Line 15: Line 17:
  
 
For exchanges, and block explorers:  You will not be affected because our memory tuning selector is set to only use 256meg for full nodes by default if they are not miners.  However, for miners and those running sanctuaries, Since RandomX uses up 256Meg of memory per mining thread (or block checking thread), be wary about starting the solo miner.  Each solo mining thread will consume more RAM.  Therefore we advise you to start very small, for example:  setgenerate true 1, check the stability of your system, then move to setgenerate 2.  Know that it is never profitable to solo mine with the core wallet, due to the memory tuning constraint.  See Mining with XMRig below to mine bbp with randomx.
 
For exchanges, and block explorers:  You will not be affected because our memory tuning selector is set to only use 256meg for full nodes by default if they are not miners.  However, for miners and those running sanctuaries, Since RandomX uses up 256Meg of memory per mining thread (or block checking thread), be wary about starting the solo miner.  Each solo mining thread will consume more RAM.  Therefore we advise you to start very small, for example:  setgenerate true 1, check the stability of your system, then move to setgenerate 2.  Know that it is never profitable to solo mine with the core wallet, due to the memory tuning constraint.  See Mining with XMRig below to mine bbp with randomx.
 +
 +
 +
  
 
''' Mining BiblePay with RandomX '''
 
''' Mining BiblePay with RandomX '''

Revision as of 17:15, 13 March 2020

Upgrading to 1.5.0.7 - RandomX

On March 24th, 2020, BiblePay will be transitioning to the RandomX algorithm. This upgrade is a major release therefore we need to explain some finer technical details that may not be apparent so we can help you upgrade.


Exchanges, Block Explorers and Self Compiling Full Nodes

The compilation instructions have slightly changed, due to integrating RandomX into our core crypto library. Please refer to this document first: https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt Note the part about compiling RandomX. This is an easy step, and is only required once. In general, a person compiling BiblePay will cd to the "depends" directory, compile depends as usual, then back out, cd to RandomX, compile randomX, then back out and compile the coin. Additionally, our github URL has changed to: https://github.com/biblepay/biblepay (however, we have integrated an automatic redirect in our old URL so as to not break any old scripts).


Memory

For exchanges, and block explorers: You will not be affected because our memory tuning selector is set to only use 256meg for full nodes by default if they are not miners. However, for miners and those running sanctuaries, Since RandomX uses up 256Meg of memory per mining thread (or block checking thread), be wary about starting the solo miner. Each solo mining thread will consume more RAM. Therefore we advise you to start very small, for example: setgenerate true 1, check the stability of your system, then move to setgenerate 2. Know that it is never profitable to solo mine with the core wallet, due to the memory tuning constraint. See Mining with XMRig below to mine bbp with randomx.



Mining BiblePay with RandomX

Download XMRig-BBP:

... (Coming Soon)


Pool Configuration:

... (Coming Soon)