Posts Tagged ‘Rigel

IronFish (IRON) is a new privacy-oriented Layer-1 Proof-of-Work crypto project that is launching its mainnet tomorrow on April 20th 2023 and that is when the actual mining of the IRON coins will start. IronFish has been in development for a while now and has been running an incentivized testnet for quite some time in order to make sure that at launch everything will be operating properly and everyone will be ready to start mining and using IRON. Every single IronFish transaction is encrypted, hiding sensitive user information on who the sender, recipient, or the amount of transaction was with an accompanying zero-knowledge proof (zk-SNARKs).

The IronFish genesis block will include 42M tokens that will be distributed to insiders, foundation, and community members and to incentivise testnet participants. So, do have in mind that there will be high initial number of coins generated even before mining actually starts, though these will be a 1-year lock-up period for most of these coins, meaning that no tokens can be traded or transferred by an insider for 12 months after the mainnet event. The mining will start with 20 IRON coins per block and a 60 second block time with the block reward going down a little by little every year (not halving every year!).

Now, let us get onto mining IronFish (IRON) coins. Due to the incentivized testnet there are already some pools and mining software available that support the Blake3-based IronFish mining algorithm and you can head on and give it a go mining with your existing GPU hardware. Currently you will be mining testnet coins, but the pools and miners should continue to mine with the launch of the mainnet when that happens tomorrow. This simply means that you can be ready ahead of time and start mining right at the launch, though for that you would need to get the CLI (needs to be compiled) or GUI wallet (node is not syncing) and install it and generate a wallet address that you can use to mine (the address should continue to work on the mainnet, though no coins mined from the testnet will be available there). Pools where you can mine IronFish (currently on the testnet) include HeroMiners, Flexpool and Kryptex and others will probably soon follow with support as the mainnet launches tomorrow.

There are currently three miners available for GPU miners to choose from for mining IRON coins – BzMiner v14.2.0 (AMD/Nvidia), Rigel 1.4.1 (Nvidia Only) and SRBMiner-MULTI v2.2.4 (AMD/Nvidia). Our advice will be to opt out for the SRBMiner-Muilti for the moment as it seems to be faster than the other two options, about 3 times faster on Nvidia RTX 3070 in our comparison tests with similar power usage. Another good thing about the IronFish mining algorithm is that it is a GPU-intensive one, being Blake-based, so memory can run at the minimum operating frequency and you can use a GPU offset to further lower the operating voltage and reduce power usage. In fact, if you have mined KASPA (KAS), Radiant (RXD) or any other of the more recent GPU-intensive crypto coins you should have a good idea on what settings to use for the GPU clock, offset and memory clock in order to optimize performance and reduce power usage (the same clocks should be a very good starting point).

Here is an example command line to run SRBMiner-Multi on Nvidia RTX 3070 for mining IronFish:

SRBMiner-MULTI --disable-cpu --algorithm blake3_ironfish --pool de.ironfish.herominers.com:1145 --wallet WALLET-ID.WORKER-ID --gpu-cclock0 1750 --gpu-mclock0 810 --gpu-coffset0 250

Make sure you set the WALLET-ID and WORKER-ID in order for the miner to properly function and mine to your IronFish wallet!
A good idea to work on is adding Zilliqa (ZIL) dual-mining to go along with IronFish mining as it will increase profit without affecting much the IRON mining, another thing to consider is triple-mining by also adding a memory-intensive algorithm as well in the mix.

Update: Rigel 1.4.2 and BzMiner v14.2.2 updates made them perform faster than SRBMiner-Multi 2.2.4, the Rigel 1.4.3 currently seems to be the fastest option for Nvidia. F2Pool has added support for IronFish mining as well as does not require you to have a wallet address to mine (just when you want a payout). The official GUI wallet has been taken down for now as it is apparently having issues.

For more information about the project visit the official website of IronFish…

The latest update of the Rigel miner version 1.3.5 once more brings it to the top spot in terms of mining performance for NEXA mining after it has briefly lost its leading position to the recent release of lolMiner 1.67 that also brought significant hashrate improvements for the nexapow mining algorithm. Besides the performance/efficiency improvements the new version also brings support for explicit locked clocks reset.

Do note however that users are reporting issues with the new release when mining on Nvidia 4xxx series of GPUs, so you might want to try the latest lolMiner 1.67 on these at least until a fix is made available. Also, you might want to try locking your video memory to 5000 MHz as this seems to be providing the optimal performance boost while saving some power, lowering the video memory to the minimum does lead to significant reduction in the hashrate. Even though the nexapow algorithm is more GPU-intensive it still requires the use of some video memory, so setting it too low for power savings is not beneficial.

Below is an example config for running the Rigel miner on Nvidia RTX 3070 for NEXA mining:

rigel.exe -a nexapow -o stratum+tcp://pool.woolypooly.com:3124 -u YOUR_NEXA_WALLET --cclock 250 --lock-cclock 1750 --lock-mclock 5000

In the example above make sure to replace YOUR_NEXA_WALLET with your walled address for NEXA. Here we are setting a GPU clock offset of 250 (you can try the 200-300 range to see what works best for you), the GPU clock is locket at 1750 and the video memory clock at 5000 MHz. Feel free to experiment with the power limit level and the GPU clock as 1750 MHz might be a bit too much for a 120 Watts TDP limit for instance.

To download the latest Rigel 1.3.5 Nvidia GPU miner with NEXA mining support…

The Rigel Nvidia GPU miner is a newcomer among the mining software solutions for GPU miners and more specifically for Nvidia GPU mining rig operators, but it is doing quite well in terms of competing with other older and more established and widely used miners. It does not support that many algorithms, but it is quickly introducing support for ones that are gaining a lot of user attention and the performance is really good. Not to mention that the miner comes with a nice text-based terminal user interface, is quite easy to use and comes with the right number of features including full overclocking set for the GPUs.

The Rigel miner also supports dual mining with Zilliqa (ZIL) as a means to further increase mining profitability as this dual-mining mode supports not only ethash and ethash, but any single or even dual algorithm combination + ZIL. Triple mining is supported for ethash + kheavyhash + zil and etchash + kheavyhash + zil, but that one is not actually that interesting of a mode compared to the dual-mining any algorithm with ZIL. The reason for that is due to the way ZIL is being mined – just a very short period of time every two hours, so essentially you retain the full hashrate of the main algorithm for mining the rest of the time and the extra profit from the mined ZIL is not something to miss.

In the last few versions ZIL mining was broken apparently, though the latest update of Rigel 1.3.4 brings it back working properly, so we are going to do a quick overview on how you can dual-mine Kaspa (KAS) with Zilliqa (ZIL), so that you can maximize your profit and get more than just single mining KAS. Now, Kaspa (KAS) and its kheavyhash algorithm is GPU-intensive, so you can optimize performance with a significant reduction in power usage compared to the normal settings for your video card. On the other end however you have Zilliqa (ZIL) that is a memory-intensive algorithm that just like Ethereum or any other Ethash-based crypto coin like ETC that is still mineable doesn’t need a lot of GPU power, but can benefit from maximum clock of the video memory.

So, how to combine these two seemingly opposite algorithms for dual-mining while getting optimal performance mining both? This is what we are going to take a look at now with the below example for dual-mining KAS + ZIL on an Nvidia GeForce RTX 3070 GPU, followed by explanation what and why is being used like that (the example is for windows, but the same settings should work on Linux as well). Make sure that in the example you set YOUR_KASPA_WALLET, YOUR_ZIL_WALLET and YOUR_WORKER_ID in order for the mining to properly start and you get the mined coins credited. We are using WoolyPooly as KAS mining pool and ShardPool for ZIL, though others should work as well (make sure you have the right settings for them):

rigel.exe -a kheavyhash+zil ^
-o [1]stratum+tcp://pool.woolypooly.com:3112 -u [1]YOUR_KASPA_WALLET ^
-o [2]zmp+tcp://eu1-zil.shardpool.io:3333 -u [2]YOUR_ZIL_WALLET ^
-w YOUR_WORKER_ID --log-file logs/miner.log ^
--cclock 300 ^
--lock-cclock [1]1710 --lock-mclock [1]807 ^
--lock-cclock [2]1200 --mclock [2]1000

Now, the cclock 300 option above sets the GPU clock offset in order for the video cards graphical processor to run at a lower voltage (it is set for all coins mined), do note that the 250-300 setting generally works well on most RTX 3070 GPUs, so test on your mining hardware and find what works stable for you. Since the first coin we are mining is KAS and we have it marked with [1] above then the lock-cclock [1]1710 and lock-mclock [1]807 options refer to the video card settings for Kaspa mining, setting the GPU clock locked at 1710 MHz and the memory clock to the minimum supported 807 MHz in order to reduce the power usage from the memory that we do not need much for the kheavyhash algorithm. The other line lock-cclock [2]1200 and mclock [2]1000 refers to the GPU settings for the second coin we are mining and in this case this is Zilliqa where we don’t need a higher clocked GPU, but could use a +1000 MHz overclock of the video memory over its stock settings in order to get the hashrate up to about 60 MH/s for an RTX 3070 GPU.

You will notice that mining with the settings used in the example above on RTX 3070 GPUs you will be getting around 90-95 Watts of power usage per GPU while mining KAS and when the ZIL switch occurs the different settings that will be applied will bring up the power usage to about 115-120 Watts (these can vary from GPU model to GPU model). So, there will be a slight increase of power usage for a couple of minutes in total on a daily basis and thus there will be not much of a difference in the overall power usage. While mining ZIL you will not be mining KAS, but again the switch is for a short period of time and the earnings for the mined ZIL should be able to compensate for the time you will not be mining KAS.

But why not leave the GPU settings for KAS mining for ZIL mining as well some of you may ask? Well, the answer is pretty simple – the ZIL mining performance will be very low due to the low memory setting we are using to save power when mining KAS. While Kaspa can be mined without performance loss at 807 MHz for the video memory, that operating frequency will result in just around 5 MH/s of hashrate per RTX 3070 GPU compared to round 60 MH/s when the memory is overclocked with 1000 extra MHz over its stock frequency on the same GPU. So, while you might be saving a little bit of power the hashrate will be so low that you might not be able to send even one share during the ZIL mining timeframe and thus you might just be wasting your time, unlike what the GPU can do at 60 MH/s. Just as a reference, in a single ZIL mining period (every two hours) a 6x RTX 3070 GPU mining rig should be able to currently mine 1-2 ZIL (depending on the number of shares you get).

To download the latest Rigel 1.3.4 Nvidia GPU miner with ZIL dual-mining support…


top