FAQ

How to mine xxx coin?

Below, we list a few examples to get you mining Gemlink (GLINK) with miniZ

You should check each pool page since the pool may define more than one server or port number.

Normally, you do not need to write --pers sngemPoW or --par=144,5. However, this depends on the pool, and miniZ version.

For more information about miniZ command line arguments, please refer to Usage page.
Happy GLINK mining!

Below, we list a few examples to get you mining Firo (FIRO) with miniZ

You should check each pool page since the pool may define more than one server or port number.

Normally, you do not need to write --par=progpow --pers=firo. However, this may depend on the pool.

For more information about miniZ command line arguments, please refer to Usage page.
Happy FIRO mining!

Below, we list a few examples to get you mining Ethereum Classic (ETC) with miniZ

NOTE: It is possible that a few pools are not yet supported.
             We’ll work to increase the number of supported pools in the next release.

You should check each pool page since the pool may define more than one server or port number.

Normally, you do not need to write --par=etchash and/or --pers=etchash. However, this depends on the pool. We’ll keep improving the miner in order to support more pools.

For more information about miniZ command line arguments, please refer to Usage page.
Happy ETC mining!

Below, we list a few examples to get you mining Ethereum (ETH) with miniZ

NOTE: It is possible that a few pools are not yet supported.
             We’ll work to increase the number of supported pools in the next release.

You should check each pool page since the pool may define more than one server or port number.

Normally, you do not need to write --par=ethash. However, this depends on the pool.

For more information about miniZ command line arguments, please refer to Usage page.
Happy ETH mining!

Below, we list a few examples to get you mining Ravencoin (RVN) with miniZ

You should check each pool page since the pool may define more than one server or port number.

Normally, you do not need to write --par=kawpow or --pers=rAVENCOINKAWPOW. However, this depends on the pool.

For more information about miniZ command line arguments, please refer to Usage page.
Happy RVN mining!

Below, we list a few examples to get you mining VeriBlock (VBK) with miniZ

You should check each pool page since the pool may define more than one server or port number.

Normally, you do not need to write --par=vProgPow or --pers=VeriBlock. However, this depends on the pool.

For more information about miniZ command line arguments, please refer to Usage page.
Happy VBK mining!

Below, we have an example to get you mining Veil (VEIL) with miniZ

You should check each pool page since the pool may define more than one server or port number.

Normally, you do not need to write --par=ProgPow or --pers=veil. However, this depends on the pool.

For more information about miniZ command line arguments, please refer to Usage page.
Happy VEIL mining!

Below, we list a few examples to get you mining Zano (ZANO) with miniZ

You should check each pool page since the pool may define more than one server or port number.

Normally, you do not need to write --par=ProgPowZ or --pers=zano. However, this depends on the pool.

For more information about miniZ command line arguments, please refer to Usage page.
Happy ZANO mining!

Below, we list a few examples to get you mining Super Zero (SERO) with miniZ

You should check each pool page since the pool may define more than one server or port number.

Normally, you do not need to write --par=progpow--pers=sero. However, this depends on the pool.

For more information about miniZ command line arguments, please refer to Usage page.
Happy SERO mining!

Below, we list a few examples to get you mining Zclassic with miniZ.

You should check each pool page since the pool may define more than one server and port number.

Normally, you do not need to write --pers ZcashPoW or --par=192,7. However, this depends on the pool, and miniZ version.

For more information about miniZ command line arguments, please refer to Usage page.
Happy ZCL mining!

Below, we list a few examples to get you mining Grimm with miniZ.

Check each pool page since the pool may define more than one server and port number.

From v1.5p it should not be necessary to add --par=150,5 and --pers=GrimmPOW  to your command line. However, this may depend on the pool.

For more information about miniZ command line arguments, please refer to Usage page.

Happy GRIMM mining!

Below, we list a few examples to get you mining Arrow with miniZ.

You should check each pool page since the pool may define more than one server and port number.

From v1.5p it should not be necessary to add --par=192,7 and --pers=ArrowPoW to your command line. However, this may depend on the pool. 

Also, be aware that some pools do not support --pers=auto, in this case it is better to not specify --pers at all or use --smart-pers

For more information about miniZ command line arguments, please refer to Usage page.

Happy ARW mining!

Below, we list a few examples to get you mining Ycash with miniZ.

You should check each pool page since the pool may define more than one server and port number.

From v1.5p it should not be necessary to add --par=192,7 and --pers=ZcashPoW to your command line. However, this may depend on the pool.

Also, be aware that some pools do not support --pers=auto, in this case it is better to not specify --pers at all or use --smart-pers.

For more information about miniZ command line arguments, please refer to Usage page.

Happy YEC mining!

 

Below, we list a few examples to get you mining Aion with miniZ.

You should check each pool page since the pool may define more than one server and port number.

Normally, you do not need to write --pers AION0PoW. However, this depends on the pool.

For more information about miniZ command line arguments, please refer to Usage page.

Happy AION mining!

From version miniZ v1.6v you can mine the new Beam algorithm – BeamHash III (144,5-siphash) – a new algorithm introduced for Beam mining in the Beam hard fork at block height 777777, on 28 June 2020.

Below, we list a few examples to get you mining Beam with miniZ.

You should check each pool page since the pool may define more than one server and port number.

Normally, you do not need to write --pers Beam-PoW, --par=beam3, or  --par=144,5s  in the command line. However, this depends on the pool.

For more information about miniZ command line arguments, please refer to Usage page.

Happy BEAM mining!

Below, we list a few examples to get you mining BitcoinZ (BTCZ) with miniZ.

You should also check each pool page, since the pool may define more than one server or port number. 

Normally, you do not need to add --pers=BitcoinZ to your command line. However, this may depend on the pool.

Also, be aware that some pools do not support --pers=auto, in this case it is better to not specify --pers at all or use --smart-pers.

For more information about the various command line arguments, please refer to Usage page.

Happy BTCZ mining!

Below, we list a few examples to get you mining Flux with miniZ.

 You should check each pool page since the pool may define more than one server and port number.

Normally, you do not need to write --pers ZelProof. However, this depends on the pool.

For more information about miniZ command line arguments, please refer to Usage page.

Happy FLUX mining!

*ANON changed algorithm to Equihash 192,7. You need to specify the algorithm in the command line. Use --par=192,7. *

For more information about the various command line arguments, please refer to Usage page.

Happy ANON mining!

BTG mining on Windows: step-by-step

Below, we list a few examples to get you mining Bitcoin Gold with miniZ.

You should check each pool page, since the pool may define more than one server or port number.

Normally, you do not need to write --pers=BgoldPoW because this is the default personalisation string. However, this may depend on the pool.

Also, be aware that some pools do not support --pers=auto, in this case it is better to not specify --pers at all or use --smart-pers.

For more information about miniZ command line arguments, please refer to Usage page.

Happy BTG mining!

Below, we list a few examples to get you mining Zero with miniZ.

You should check each pool page since the pool may define more than one server and port number.

Normally, you do not need to write --pers ZERO_PoW or --par=192,7. However, this feature may not be implemented in all versions, especially older ones.

For more information about miniZ command line arguments, please refer to Usage page.

Happy ZER mining!

Below, an example to help you get off to a smooth start with miniZ.

Normally, you do not need to write --pers ZcashPoW or --par=96,5. However, this depends on the pool.

For more information about the various command line arguments, please refer to Usage page.

Happy MNX mining!

Optimisation

With version v1.8y4rc2 we modified --tune option.  Now you will be able to adjust two parameters for your GPU (not compatible with the previous v1.8y4rc1 version, see below).

The default values are not yet optimal for everyone. We suggest you to play around with i and d starting with small variations around the defaults.

--tune=iN1dN2 where i stands for intensity and d stands for drag. N1and N2 are numerical values.

  • Intensity is similar to the value that you were using to tune with v1.8y4rc1. However, values are no longer compatible. N1 is an integer and can take values in the interval 0-64.
    i default values are: 15 (3060), 15 (3070 Ti), and 10 (3080 Ti), on Linux. And 19 (3060), 15 (3070 Ti), 10 (3080 Ti), on Windows.
    Default value with driver 460.39/461.40 for RTX 3060 is 43.
  • Drag will balance intensity. N2 is a decimal number and values can vary in the interval 0-100.
    d default values are: 55 (3060), 60 (3070 Ti), 59 (3080 Ti), on Linux. And 54 (3060), 57 (3070 Ti), 55.5 (3080 Ti), on Windows.
    Default value with driver 460.39/461.40 for RTX 3060 is 64.

Note: If you increase PL, usually you’ll need to decrease i value.

Usage is as follows:

  • To apply tune to all GPUs in your rig, with i=17 and d=57:
    miniZ.exe [email protected]:3096 --tune i17d57

    or

    miniZ.exe [email protected]:3096 --tune=i17d57
  • To apply tune with i=17 and d=57 to GPU 3:
    miniZ.exe [email protected]:3096 --tune3 i17d57
    
  • You can also tune only one of the parameters, i or d, and apply the values to all or just one GPU. Similarly to the previous examples:
    miniZ.exe [email protected]:3096 --tune i17

    or

    miniZ.exe [email protected]:3096 --tune3 d57

* Tune with v1.8y4rc1 version *

The following is only valid for the v1.8y4rc1 version. Read above for usage for other versions (from v1.8y4rc2 on).

With v1.8y4rc1 version --tune was working with one parameter. Only the RTX 3060 supported this option.

Default value with recent drivers such as 470.63/472.12 is 6. Default value with driver 460.39/461.40 for RTX 3060 is 38.

We were advising you to lower this value when the miner is not able to get rid of the anti-mining lock.

Usage is as follows:

  • To apply tune with value 5 to all GPUs in your rig:
    miniZ.exe [email protected]:3096 --tune 5

    or

    miniZ.exe [email protected]:3096 --tune=5
  • To apply tune with value 5 to GPU 3:
    Note that in this case you cannot write with ‘=’ sign

    miniZ.exe [email protected]:3096 --tune3 5

 

From miniZ version v1.8y3, there are a few available options that will have impact on performance on some GPUs.

*** The --mt options will only apply settings to Pascal devices. ***

These improvements are usually applied to ethash/progpow algos, however equihash algos may also profit from them.

This option is known to work well with GTX 1080, GTX 1080Ti, and other devices with Hynix memory. Other GPUs may profit from this adjustments but to a much smaller extent.

The --mt options will require super user permissions.

  • --mt-auto: use automatic memory timings (sudo required)

If you are unsure about the timing values, use the --mt-dump option first to get a hint. Lower values usually will give a better performance.

  • --mt-dump: dump memory timings in use (sudo required).

To apply list of memory timings per GPU use --mt. Remember when using the --mt option to always specify the timing pair, with the values separated by ‘.’ such as ‘16.5’ .

  • --mt=[timings] [16-32].[3-9]: Ex. --mt=16.5. Always specify the timing pair. (sudo required)
    If you have multiple devices you can specify multiple values like this --mt 16.5,0,21.4. The 0 means no timings should be applied.

Warning: some values will be invalid for your GPU and may cause the driver/GPU to crash. In this case you will need to restart your rig/system/computer. Use with caution.

 

Option inspired on the work by Tiago Shibata.
https://github.com/tiagoshibata/meth-pills
donate: stratum1+tcp://[email protected]:3333

 

In some cases you may want to select a specific mode/kernel for miniZ to run in your GPU. This can happen for example after using --ocX1 to tune miniZ for a specific algo+GPU+OC, or just want to test it in another similar GPU.

At the moment, you will be able to run a mode for your rig, or a specific GPU, by using --mode option. This is still a work in progress. We may find a better way to achieve the same task 🙂

  • To select mode 8 for GPU 3:
    Note that in this case you cannot write with ‘=’ sign.

    miniZ.exe --url [email protected]:50053 --log --mode3 8
  • To select mode 5 for GPU 0, and mode 3 for all other GPUs. The order matters. Ex:
    miniZ.exe --url [email protected]:50053 --log --mode 3 --mode0 5
  • To select mode 8 for GPU 3, and mode 1 for GPU 4:
    miniZ.exe --url [email protected]:50053 --log --mode3 8 --mode4 1
  • To select mode 5 for GPU 3 and for GPU 4:
    miniZ.exe --url [email protected]:50053 --log --mode3 5 --mode4 5

Keep in mind that when you apply OCs to a GPU it is possible that some kernels do become unstable and others do not. But, if a mode is dramatically unstable also after you try it with stock settings, we appreciate that you contact us 🙂 Reporting GPU model, miniZ version, mode in question, and algorithm is very useful in this case. Thanks!

1: Do not use/apply oc1/oc2/ocX (or --mode)at the same time on the same GPU. This could cause confusion in understanding miniZ behavior. One of the options will prevail though, usually the last one appearing in the command line.

For other command line arguments check Usage page.

Happy mining!

 

*** Do not use --ocX when mining with RTX 30XX with anti-mining lock. ***

From v1.5t3 version you can use --ocX for miniZ to automatically choose the best kernel for your GPU.
Available for 125,4 and 150,5,3 algorithms in v1.5t3. Available in all algorithms from v1.5u version.

--ocX  is a new option that runs a few available miniZ kernels and chooses the one that performs best.1 It starts with the one set by default, the one we chose to be the best in stock settings. For a few GPUs the defaults are not optimised because we did not have access to that GPU model for testing. Generally, from each algo table performance you can infer which GPUs we tested.

    • To run ocX you only have to add it to your command line. Ex.:
miniZ.exe --url [email protected]:50053 --log --ocX

If you have more that one GPU, it will start optimisation for all GPUs, asynchronously. It starts mining with default kernels, we called it mode in the messages:

After stabilizing a bit (temperature, performance..) miniZ will start switching modes:

After testing all available modes for that GPU it will stop switching.

Some GPUs may finish later. This will be OK, since the ones that tested everything first will start mining with the mode(s) that performed best. There is no need to stop and restart miniZ.

After the tune is finished, take note of the mode in case you want to use it later (we may improve this in future versions). You can run a mode for your rig, or a specific GPU, by using --mode. This is still a work in progress but we have a separate FAQ for it here.

  • To run ocX on a specific GPU. Ex. apply ocX to GPU 3:
miniZ.exe --url [email protected]:50053 --log --ocX=3

In this case, optimisation will only start for GPU 3, similarly to what is shown above. The other GPUs will just start mining as usual.

  • To run ocX on specific GPUs. Ex. apply ocX to GPU 0 and GPU 3:
miniZ.exe --url [email protected]:50053 --log --ocX=0,3

In this case, optimisation will only start for GPU 0 and GPU 3. The other GPUs will just start mining as usual.

Keep in mind that when you apply OCs to a GPU it is possible that some kernels do become unstable and others do not. But, if a mode is dramatically unstable also after you try it with stock settings, we appreciate that you contact us 🙂 Reporting GPU model, miniZ version, mode in question, and algorithm is very useful in this case. Thanks!

1 --ocX is different from --oc1/--oc2.
--oc1 or --oc2 will set a specific kernel mode for the GPUs. --ocX will select and run a few kernels and let you know which performed best. Do not use/apply oc1/oc2/ocX (or --mode)at the same time on the same GPU. This could cause confusion in understanding miniZ behavior. One of the options will prevail though, usually the last one appearing in the command line.

For other command line arguments check Usage page.

Happy mining!

miniZ includes a command line argument for improving performance at distinct overclock (OC) values.

When you’re adjusting your power limit (PL) and OC setting values, you can use --oc1 or --oc2 to change the default kernel mode for your GPU. The following table (Table 1.) shows oc1 and oc2 support for each combination of GPU and algorithm. --oc0 is default mining mode that each GPU.

--oc1 or --oc2 will set a specific kernel mode for the GPUs. These refer to kernels we noticed that performed best in some OC settings, and for some GPUs. This is why not all GPUs have oc1 or oc2. Sometimes the default (optimised for stock settings) was the best we found.

Recently, from v1.5t31,2 version, you can use --ocX for miniZ to automatically choose the best kernel for your GPU. For more information check ocX related FAQ here.

Algorithms
GPU 96,5 144,5 125,4 150,5 192,7 210,9 150,5,3 144,5s
BeamHashIII
GTX 1050 2GB - - - - oc1 - - -
GTX 1050 Ti 4GB - oc1/oc2 - oc1 oc1 - - -
GTX 1060 3GB/6GB oc1 oc1/oc2 oc1/oc2 oc1 - oc1 oc1 -
GTX 16XX series - oc1 - - - oc1 - -
P106-100 oc1 oc1/oc2 - oc1 - oc1 oc1 -
GTX 1070 - oc1/oc2 oc2 oc1 oc1 oc1 oc1 -
GTX 1070 Ti - oc1/oc2 oc1/oc2 oc1 oc1/oc2 oc1 oc1/oc2 oc1
GTX 1080 8GB oc1 oc1/oc2 oc1/oc2 oc1 oc1 - oc1/oc2 -
GTX 1080 Ti 11GB - oc1 oc1/oc2 oc1 oc1 oc1 oc1/oc2 oc1
P104-100 oc1 oc1/oc2 oc1 oc1 oc1 - oc1/oc2 -
RTX 2060/2070 - - - - - - oc1 -
RTX 2080/2080 Ti - - - - - - oc1 -
TITAN - oc1 oc1/oc2 oc1 oc1 oc1 oc1/oc2 oc1
Table 1. v1.6v --oc1/--oc2 support for all algorithms and GPUs.

Usually, at lower PL/OC values --oc1 produces better performance. When you push your GPU to higher PL/OCvalues, --oc2 is likely to be produce higher hashrate. It all depends on your OC settings. 

The best is to try both and check which performs best for your settings and GPUs. For stock settings it should not be necessary to use this option.

When you add --oc1 or --oc2 to your command line this setting is applied to all GPUs. You can also apply the setting to a specific GPU.

Examples for a rig with 6 GPUs, mining Zel on equipool:

1. To apply --oc1 to all GPUs

miniZ.exe --url [email protected]:50053 --log --oc1

2. To apply --oc1 only to GPU#2 and GPU#3

miniZ.exe --url [email protected]:50053 --log --oc1=2,3

3. To apply --oc2 to all GPUs except for GPU#1 and GPU#4. Note that order matters (try it out!).

miniZ.exe --url [email protected]:50053 --log --oc2 --oc0=1,4

4. To apply --oc1 to most GPUs, --oc2 to GPU#0, and default mode to GPU#3 and GPU#4.

miniZ.exe --url [email protected]:50053 --log --oc1 --oc2=0 --oc0=3,4

 

1 Available for 125,4 and 150,5,3 algorithms in v1.5t3. Available in all algorithms from v1.5u version.

2: Do not use/apply oc1/oc2/ocX (or --mode) at the same time on the same GPU. This could cause confusion in understanding miniZ behavior. One of the options will prevail though, usually the last one appearing in the command line.

 

* NOTE: Adding --oc1/2 to the command line does not apply OCs to the GPU, it just makes the GPU run with different kernel functions. When you adjust the OCs in Afterburner (or other program) and run miniZ without --oc1/2 the miner will run with the default kernels (usually optimized for stock settings). The --oc command line option just change the way miniZ runs not the OC settings of the GPU. *

For other command line arguments check Usage page.

Happy mining!

Operating Systems

  • We made available a few Windows .bat files on Download page for you to launch miniZ. These are just a few examples to help you get started. Feel free to customize them to your own needs, and do not forget to add your wallet addresses and worker names.
  • You can also create your own .bat file. For this you need to create a new text file, and when giving it a name do not forget to set the .bat extension. Then you can paste there a command line with other miner options (ex. add --show-pers to show personalisation string). Or add extra functionalities (ex. auto restart the miner).
  • Alternatively, you can use the miniZ GUI launcher, given with the miniZ Windows packages. The following link will guide you through it.

miniZ GUI Launcher

Happy mining!

When you run miniZ, you have various arguments available that enable you to customize your console output and get the information about what is going on with your mining.

The use of colors makes it easier for the user to check the information (check here to see how it looks like). However, if you are not using Windows 10, it is likely that the console output gets all cluttered and unreadable.

The easiest solution is to use the --nocolor argument when running miniZ. This will help clean up the console. The downside is that you get rid of colors too.

If you like to have a more colorful output, you should know that you can install another console on Windows. We tried ConEmu terminal emulator and it worked fine. (Helper videos can be found on Youtube, example) There are others available, which should also work OK. 

Happy mining!

We realized that some of you struggle with some issues when starting mining using Windows.

We hope this will help you get started.

Windows mining step-by-step: how to start miniZ on Windows?

** Hive OS already includes miniZ out of the box 🙂 **

To use miniZ with Hive OS, you only have to create a new Flight Sheet.

We keep instructions updated @ our Blog.

See the latest here https://miniz.ch/2019/04/26/hive-os-support-6/

Happy mining!

Additional Features

Sometimes one wants to define multiple failover pools, and some of these may require a password.

However, when writing the (long) command line in the shell the password will be set equal for both. If the password cannot be the same in all pools then, the only way to define more than one password is by creating a configuration file. This is also very handy when the line is long.

You can read the FAQ about creating a configuration file. Yet, we repeat here a little with focus on how to define two passwords.

1. Add --write-config to your command line, and run. (add your information):

miniz.exe --par=192,7 --pers=auto [email protected]:2144 --pass x1 [email protected]:2144 --pass x2 --write-config

miniZ will create miniZ.conf file…with both pass equal. You’ll need to edit the file and correct it.

Note that if you want to give it a different name, then add filename.conf to command line, right after the --write-config:

miniz.exe --par=192,7 --pers=auto [email protected]:2144 --pass x1 [email protected]:2144 --pass x2 --write-config filename.conf

2. Open your config file with a text editor. Go to “Servers”, and edit/correct the “pass” as you need, and save.

3. Then you’ll only need to run miniZ with --read-config.

If you want to read from the default file name:

miniZ.exe --read-config

or if you want to read from another file:

miniZ.exe --read-config filename.conf

Happy mining!

Setting up a configuration file can be quite useful. This is particularly true when the command line is very long and you want to modify it often, then it is easier to create and edit a simple file where the information can be more organised.

To create a configuration file with miniZ, you can write it from scratch, however you can also write the long command line once , adding --write-config  to it, and run. Ex:

 miniz.exe --algo=150,5,3 --url=ssl://[email protected]:3333 --pass x1 --url=ssl://[email protected]:3333 --pass x2 --write-config

miniZ will create miniZ.conf file. If you want to give it a different name add filename.conf to command line, right after the --write-config:

miniz.exe --algo=150,5,3 --url=ssl://[email protected]:3333 --pass x1 --url=ssl://[email protected]:3333 --pass x2 --write-config filename.conf

You can open the file with a text editor to see how it looks like. You can also edit the file as needed.

Finally, you’ll only need to run miniZ with --read-config. 🙂

If you want to read from the default file name:

miniZ.exe --read-config

or if you want to read configurations from another file:

miniZ.exe --read-config filename.conf

 

Saving ocX best mode to configuration file.

In case you want to save the result of running ocX to the configuration file, you’ll need to proceed as above and write the command line with --write-config at the end (do not forget you can add a filename, read above):

miniz.exe --algo=150,5,3 --url=ssl://[email protected]:3333 --pass x1 --url=ssl://[email protected]:3333 --pass x2 --ocX --write-config

However, now you will see the program run and start ocX. When ocX ends, miniZ will save the best mode to the configuration file. (It will also keep running with the best mode.)

If you run miniZ with that config file, it will start applying the saved mode to the GPU.

 

For other command line arguments check Usage page.

Happy mining!

From v1.5q you can save statistics to an csv format.

Define the desired csv filename by adding --csv [filename] to your command line. This will create a file with data separated by commas.

The data you’ll find in the csv file:

* Run time information: run_time,unix_time,human_time,

* Mining pool: mining_pool,

* Personalisation string: pers_string,

* Shares information (total, for rig): sum_shares_ok,sum_shares_stale,sum_shares_invalid,

* Ping information: ping,

* User pool and fee servers share: pool.server,fee.server,

* I/s, Sol/s, Sol ratio information (total, for rig):  sum_Is,sum_Is_avg,sum_Sols,sum_Sols_avg,sum_solratio,

* Power information (total, for rig): sum_power,sum_power_avg,

* Information per GPU (#GPU number 1,2,3…): pcibus_1,gpuname_1,shares_ok_1,shares_stale_1,shares_invalid_1,temperature_1,fan_speed_1,clock_1,mem_clock_1,iterations_1,iterations_avg_1,sols_1,sols_avg_1,solratio_1,power_1,power_avg_1,sol_watt_1

Happy mining!

Mining Pools

NiceHash did an upgrade to its platform. For more information read here https://blog.nicehash.com/post/new-nicehash-platform-now-live-updates

Here you can find instructions on how to use miniZ on NiceHash:

  1. Here https://www.nicehash.com/algorithm you can find the algorithms and respective information to set the stratum+tcp address, username (your Bitcoin address) and password (x).
  2. Example usage for 144,5 algorithm – Zhash , european server:  
    miniZ.exe [email protected]:3369 --pass x --pers=auto


    Example usage for 144,5s algorithm – BeamHash III
    , european server:

    miniZ.exe [email protected]:3387 --pass x

    You can also write --pers=Beam-PoW  but is not necessary.

  3. Follow your miner by entering your BTC address @ https://www.nicehash.com/miner

Happy mining!

We will strive to help you with any doubt you may have and provide a solution to any problem you may encounter. In case you need to reach us, please check the Support page.

Follow us
On Twitter
Our thread on bitcointalk.org