VDN (vDinar) is a relatively new regional-oriented crypto currency that has been getting more attention lately. It was CPU-mineable up until recently, though it seems that there is a ccMiner fork available (source) supporting the vCrypt algorithm that the coin uses for mining. The vCrypt algorithm is not entirely new mining algorithm, it is more like a variation of the Scrypt-N algorithm, though you are not able to mine vDinar with regular Scrypt-N miners.

Unfortunately there seems to be no binary version of the ccMiner for for Vcrypt, because it seems that the GitHub source of the Veles miner fork of ccMiner is incomplete and many people are having trouble compiling it by themselves. That is why we have compiled a 32-bit Windows binary of the miner with VC2013 and CUDA 8.0, it supports Compute 3.0, 5.0 and 5.2 and should work with pretty much any more recent Nvidia GPU. Do note however that the vCrypt algorithm is pretty heavy on the CPU, so you may have trouble achieving maximum hashrate if you have a slower dual-core CPU like the commonly used Intel Celeron processors for GPU mining rigs.

Performance wise you can expect something like 900-950 KHS from a GTX 1080 Ti, 700-ish from GTX 1070 Ti, 450-500 from GTX 1060, but that is only if you have a high-end CPU. With a slower processor such as Intel Celeron G3930 for example you might be getting just a fraction of the actual hashrate, because of the slow processor performance and the miner maxing out the CPU usage. You can try running multiple instances of the miner for better results and also feel free to play around and experiment with different launch settings to see if this might improve the situation with performance and share your findings, but again, have in mind that to get good performance with vCrypt on a multi-GPU mining rig you will need a really high-end CPU.

To download and try the the Veles miner ccMiner fork for Vdinar (VDN) using vCrypt algorithm for Windows 32-bit…

Innosilicon has announced an upgrade to their 30 GHS A5 DashMaster X11 ASIC miner from last year in the form of a new 65 GHS X11 ASIC named Innosilicon A5+ DashMaster. The new device seems a lot like just two of the older devices joined together and the specifications also suggest something like that as well. Anyway, Innosilicon A5+ DashMaster promises 65 GHS X11 hashrate at 1500 Watts of power usage in a single device that will cost you $4200 USD or the respective value in LTC or BTC (the price does not include a power supply). The X11 ASIC market is pretty crowded already and the profitability for mining DASH especially is not very high anyway, but you could look for altcoins that might give you better results.

Innosilicon A5+ DashMaster Specifications:
– Hash Rate: 65GH/s(+/-8%)
– Power Consumption: 1500W +/-8% (at the wall, with 93% efficiency PSU, 25°C temperature )
– Chip Type: A5+ DashMaster ASIC
– Dimensions: Double tube, 265mm(L) x 250mm(W) x 155mm(H)
– Net Weight: 6.02KG(without PSU)
– Operating Temperature: 0°C—85°C (device junction temperature)
– Network Connection: Ethernet

For more details about the new Innosilicon A5+ DashMaster X11 ASIC miner…

The craze for many forks from the Bitcoin blockchain has resulted in people trying to claim their free coins in various ways, the easiest one is to keep a local wallet and just export your private keys from the Bitcoin wallet and import them to the wallet of the fork. As a security measure it is always advised to first move your Bitcoin (or other coins) to a new address before trying to claim any kind of forked coins, this way you can be safe that your private keys used for the claim cannot be used for stealing your actual BTC. With the recent addition of official support for SegWit addresses it might be a good time to update your Bitcoin Core wallet, generate a new SegWit wallet address and move your coins these and then start claiming some forked coins with the old private keys.

How to export the private keys:
– Start your Bitcoin Core or other QT-walletwallet p
– Click on “Help” in the menu bar of the wallet
– Click on “Debug window” from the menu
– Select the “Console” tab to be able to type commands
– Unlock your wallet (if it is locked) with: walletpassphrase “your wallet password” 600
– Export the private key with: dumpprivkey “your Bitcoin address”
– Copy and keep safe the private key you will get for the respective wallet address you have typed
– Lock the wallet again with: walletlock

How to import the private keys:
– Start your Bitcoin Core or other QT-wallet
– Click on “Help” in the menu bar of the wallet
– Click on “Debug window” from the menu
– Select the “Console” tab to be able to type commands
– Unlock your (if it is locked) wallet with: walletpassphrase “your wallet password” 600
– Import the private key with: importprivkey “your Private key”
– You can check to see that a new receiving address has been added in the wallet
– Lock the wallet again with: walletlock

Make sure you import your private key(s) as soon as you start the local wallet for the fork in order to claim all of the coins properly, otherwise you might have to do a resync of the blockchain. Alternative solution would be to just copy the Bitcoin wallet.dat file, but then you might need to do a zapwallettxes and it can take longer time to claim if you have multiple wallets. Again, make sure you keep your private keys safe and do not share them or use them to try to claim coins unless you have already moved all of the coins to a new address prior to initiating the claiming process, otherwise there is a risk of loosing your BTC or other coins as there are scams out there posing as real forks that are trying to steal your coins. Even with legitimate forks it is always a wise idea to be on the safe side and never share or use a private key for a wallet that still have coins in it, just to avoid possible security risks.