Introduction

Cryptocurrency mining is an activity that secures a blockchain network. Miners dedicate vast amounts of computing power using CPUs, GPUs and specialized hardware to solve the hash that belongs to the next block of the chain. This is called ‘finding a block’ and miners earn a reward for their effort. Miners compete against each other to find the most blocks. Those who commit more hashing power will find more blocks in a statistically deterministic fashion. For TUBE and most other CryptoNight coins, the difficulty of finding the next block is adjusted continuously so blocks are found roughly every 120 seconds.

Mining secures the network because a malicious actor will require the majority of the network hash rate to attempt to manipulate transactions in a so-called ‘51% attack’. The bigger the network, the more expensive it is to execute such an attack. Additionally, more miners mean that the block reward will be shared among more users, reducing profitability and increasing the production cost and therefore arguably the inherent (thermodynamic) value of the coin.

Furthermore, as more people start mining a certain coin, it becomes increasingly difficult for small miners to compete with the rest of the network. Since actual blocks found by small miners will be far and few between, block reward payouts become very irregular. This is why mining pools exist. Here, a large number of miners bundle their hashing power to find blocks for the pool, while each miner receives regular payouts corresponding to their relative contribution of hashing power. This ensures that small miners will receive regular payouts, whether they find blocks or not.

You can find a list of active TUBE mining pools here. All pools have roughly the same layout. They provide instructions on how to start mining under ‘Get started’ or similar. Each pool allows you to calculate mining profits based on your hash rate and track your payout history and mining statistics by filling in your wallet address.

Mining TUBE is only profitable on GPUs (graphics cards) depending on electricity cost. The proof-of-work is memory-intensive and cards with 4 GB VRAM or more are required for good performance. For the current mining profitability of coins, check out https://www.cryptunit.com.

It is not recommended to mine on laptops or tablet devices. Mining uses considerable power and portable devices like these are not built for 24/7 sustained workloads. They lack proper cooling and you run the risk of overheating resulting in a reduced lifespan.

Download the miner

You can mine TUBE with several software packages:

  1. Official BitTube miner (recommended): https://github.com/ipbc-dev/bittube-miner/releases
    OS support: Windows, Mac, Linux. Based on xmr-stak, the configuration is similar. CUDA support for Nvidia users (2.0.0.2+).
  2. xmr-stak by fireicehttps://github.com/fireice-uk/xmr-stak/releases
    OS support: Windows. 2% developer fee. CUDA support for Nvidia users (2.4.6+).
  3. Other third-party miners: CastXMR, SRB Miner, xmrigCC,… Find the download links on https://mining.bit.tube

Setup the miner

This guide will focus on the official BitTube miner. The installation and configuration are largely identical to the xmr-stak miner by fireice. However, the latter does not feature a beginner-friendly non-expert option to start mining directly to the web wallet.

  1. Unpack the contents of the archive to your desired location.
  2. Run bittube-miner.exe
  3. Select setup mode:

Non-expert mode: start mining to your web wallet directly

  1. “Are you an expert?” No.
  2. This option will directly start mining to your bit.tube web wallet on the default mining.bit.tube pool.
    *Make sure you are registered on bit.tube.
    *Confirm that the wallet address (located in pools.txt) matches with your web wallet.
  3. Click on Start Mining at the left menu on bit.tube to check statistics when mining to your web wallet.

Expert mode: setting everything up yourself

  1. “Are you an expert?” Yes.
  2. Do you want to use HTTP interface?  0.
  3. Enter the pool address, e.g. “mining.bit.tube:13333”.
    Choose alternative pool from https://miningpoolstats.stream/bittube.
    Choose a port number (e.g. 13333, 15555, 17777)) best suited for your hardware.
  4. Enter your wallet address Optional: add a desired static difficulty in the form “walletaddress.difficulty”. This can greatly improve the efficiency and increase the accepted shares by the pool. Optimally use 40x your hash rate, e.g. 500 H/s x 40 = 20000.
  5. Enter Password: x
  6. Rig identifier: only applicable if you run multiple rigs on the same pool, e.g. “rig1”, “rig2”.
  7. TLS/SSL support? n
  8. Use Nicehash? n
  9. Use multiple pools? Optional (Yes: step 10 / No: step 11)
  10. Choose yes, if you would like to add a fallback pool in case you lose connection to your main pool. For this option, the next step is setting the pool weight for the one that you just entered and subsequently repeating all the steps for your second or third pool. For example, if we choose mining.bit.tube:15555 as the main pool and tube.ingest.cryptoknight.cc:5632 as a fallback, the former needs to have weight 2 and the latter weight 1.
  11. All done. If everything checks out, it will now start mining.

Tutorial video done by BitTube community.
How-To Mine BitTube on XMR STAK 2.4.7 Thanks
NorthEastTexasTechnologies .

Inside the installation folder, you will now find additional text files storing your configuration: config.txt, cpu.txt, pools.txt and amd.txt/nvidia.txt, expert.json.

  1. In pools.txt, you can change your wallet address and pools configuration.
  2. The other files are meant for tweaking the behavior and performance of your miner.
    *Each text file has explanations on each setting.
    *We recommend keeping the default settings for mining TUBE, as they are already optimized.

If something went wrong with the setup process and you need to start over, you can simply delete all these configuration text files and run bittube-miner.exe again.

Setting startup parameters (optional)

Mining TUBE is only efficient on GPUs. To make sure your CPU cores are not mining too, you can disable CPU support using a batch file with startup parameter –noCPU (two dashes).

  1. Create a new file named start_nocpu.bat using notepad.
  2. Save As → All types.
    Containing:

start /b bittube-miner –noCPU

If you are an AMD user, it is recommended to include additional driver-related parameters to the batch file to improve performance, like so:

setx GPU_FORCE_64BIT_PTR 1 setx GPU_MAX_HEAP_SIZE 100 setx GPU_MAX_USE_SYNC_OBJECTS 1 setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_MAX_SINGLE_ALLOC_PERCENT 100

start /b bittube-miner –noCPU

  1. Run this batch file instead of bittube-miner.exe directly.
    For xmr-stak, the advice is the same and you should just change “bittube-miner” to “xmr-stak” inside the batch file.

When the miner is running, pressing h will display your current hash rate. To check your pending balance and payout history of the pool, navigate to the pool web page and enter your wallet address under Your Stats & Payment History.

The pending balance will be paid when the pool-specific payout threshold is reached. Under Last Share Submitted, it should indicate whether your shares are being accepted successfully.

Since the release of the GUI wallet 2.0, it is possible to start mining from within the wallet. The user interface provides most of the necessary options to set it up.

Some flexibility from the classic method is sacrificed for ease-of-use with this implementation. The miner executable and its configuration files are located inside the walletdir\miner\ folder. Settings that are not yet available in the UI, such as backup pools, can be edited there.

When clicking Start mining, the bittube-miner.exe process is started in the background and the hash rate stats are shown under Show statistics.

For troubleshooting and tweaking, we refer to the solutions presented for the classic method, as they will apply here.

The following errors are quite common:

  • MEMORY ALLOC FAILED: VirtualAlloc failed.
  • Error CL_OUT_OF_RESOURCES when calling clEnqueueNDRangeKernel for kernel 0.

Make sure your OS’s virtual memory (page file) is at least the total amount of VRAM of all graphics cards combined. For example, 4x 8GB RX 580s will require a 32GB page file to avoid this error.

For Windows machines:

→ Control Panel → System and Security → System → Advanced system settings → Advanced tab → Performance → Settings → Advanced tab → Virtual memory → Change → Custom size → Set → OK → Reboot (mandatory)

Pin It on Pinterest