Tag: mining

Crypto Miner Softwares

Softwares to be used:

  1. Install windows on the crpto machine.
  2. Install remote monitoring software. Preferrably Team viewer or VNC server/Client.
  3. Create wallet on https://www.myetherwallet.com/ and save the private key.
  4. Create miner config on nanopool. Many pools are available. Nanopool has been my preferred option.
    Nanopool: https://nanopool.org/
  5. Use the config in Claymore’s dual miner.
    Claymore’s dual miner: https://github.com/nanopool/Claymore-Dual-Miner/releases
  6. Happy Mining !!

Unix Distro

Proprotiery OS can also be used for mining.
Ethos is specially designed for mining. It provided advanced tools for managing the rig.

Ethos: http://ethosdistro.com/

 

Crypto Miner Assemblage

Steps to assemble the crypto equipment

  1. Mount the motherboard on the aluminium case.
  2. Fit the processor and the fan provided with it. Take care of the cooling agent (Thermal paste) applied on the processor which connects to the fan.
  3. Connect the ram and ssd to the ram and sata ports.
  4. Connect the power supply to the motherboard and the peripherals.
  5. Connect the gpu’s to the risers and mount the risers on the aluminium case. Connect the risers to the motherboard and the power supply. Depending upon the power supply of the gpu this can vary.
  6. Connect screen, keyboard and mouse (peripherals to the) motherboard.
  7. Connect the power starter cord to the mentioned i/o power sockets on the motherboard. Refer to the circuit diagram of the motherboard for the same.
  8. Mount the fans on the aluminium case adjacent to the gpu’s for cooling.
  9. Start the device. Install windows in the ssd.

Crypto Miner Equipment – Ethereum

Requirements

  1. Aluminium frame
  2. 2″ * 3″ small table
  3. Motherboard: Asus Z270E Strix Gaming – LGA1151 – 7th Generation MotherBoard
  4. Processor: Intel Pentium G4400 Skylake Dual-Core 3.3GHz Desktop Processor
  5. SSD : WD Green 120GB Internal Solid State Drive (WDS120G1G0A)
  6. RAM: HyperX Fury 4GB 2400MHz DDR4 Non-ECC CL15 DIMM 4 DDR4 2400 MT/s (PC4-19200) (HX424C15FB/4)
  7. Graphic Card : Zotac GTX1060 Mini – PCI-Express Graphics Card (6GB GDDR5, CUDA cores 1280, 192-bit, Base: 1506 MHz Boost:1708 MHz, ICE Storm Cooling, VR Ready)
  8. NVIDIA GeForce GTX 1060 GP 106-100 6GB GDDR5 CRYPTOCURRENCY MINING GRAPHICS CARD
  9. Fans: Circle 120MM Silent Cabinet Cooling Fan 15 LED – 7 COLORS – 16X7C
  10. Power Supply: Corsair HX1000 – 1000 Watt 80 PLUS® Platinum Certified Fully Modular PSU
  11. Risers: 4 of Rrimin USB 3.0 PCI-E Express 1x To 16x Extender Riser Card Adapter Power Cable Mining 50CM (107793)
  12. PC Starter: Generic ATX PC Computer Motherboard Power Cable Switch On/Off/Reset w/ HDD LED Light

MultiChain Mining

In MultiChain, block creators must prove their identity by signing blocks

Block signatures

Block signatures are embedded inside the OP_RETURN metadata of the coinbase transaction, using a regular bitcoin-style signature format. The payload signed by the block creator is the full block header, with the following modifications:

  • The merkle_root is recalculated based on the txid of the coinbase transaction with the OP_RETURN removed. This prevents a dependency loop from block signature → coinbase txid → merkle root → block header → block signature.
  • The nonce field is set to 0. This avoids having to recalculate the signature for every attempt at finding a block hash to match the target difficulty. However it does lead to some malleability in that a user without mine permissions could generate a block with the same content as a valid block, but with a different nonce. Seeing as the nonce serves no purpose other than to randomize the block’s content for its hash, this should not be a source of concern.

In the case of a permissioned MultiChain blockchain, consensus is based on block signatures and a customizable round-robin consensus scheme, rather than proof-of-work as in bitcoin.

On the first server, run:

grant 15ZLxwAQU4XFrLVs2hwQz1NXW9DmudRMcyx2ZV mine

(Even though the permission is called mine note that there is no real “mining” taking place, in the sense of proof-of-work.) On the second server, check that two permitted block validators are listed:

listpermissions mine

Run this on both servers to maximize the degree of validator randomness:

setruntimeparam miningturnover 1

Now wait for a couple of minutes, so that a few blocks are added. (This assumes you left the block time on the default of 15 seconds.) On either server, check the creators of the last few blocks:

listblocks -10

The address of the validator of each block is in the miner field of each element of the response.

Snippet:
RR Mining

Node-1 Terminal | Node-2 Terminal

 

Reference: https://www.multichain.com/developers/mining-block-signatures/
https://www.multichain.com/getting-started/