From Mynt

Get started:

Quick start

  1. Download the latest wallet from Mynt github, install and get a receiving address, be sure to Backup your wallet. Remember to check Best Practices page for the best way to keep your coins safe. Note: do not use special chars for our passphrase when encrypting the wallet.
  2. Select a pool from the Pools page - or find one on the BitCoinTalk ANN. Help the network by spreading the hashrate to other pools.
  3. Download the GPU miner from the Mynt github
  4. Unzip, and edit config to include the pool you want to mine on and your wallet address to begin mining

Additional info:

  1. Ccminer(and forks) do not like too many cards in each instance, split up the cards with -d 0,1,2,3 in first bat file and -d 4,5,6,7 in next, and so on. Some are successful with running 6 cards in each instance, but 4 cards seems to be stable in almost every scenario.
  2. Sgminer (and forks) does not like 13 threads or more so if you are using -g 2 keep this in mind.
  3. Once stability is reached try raising core in +10 or +25 steps and recheck for stability. Memory OC does little on x16r and is commonly set to default or -500 for a bit more headroom. Keep in mind that ie +175core on pl 65% will not boost as high as +125core on pl 90% since Boost 3,0 will adjust according to available power and temp.
  4. To get miner to auto start on reboot press ' win + r ' and type in ' shell:startup ' then copy shortcut of your bat file into startup folder.

Please DO NOT MINE with your payout address set to an exchange or mobile wallet.

Best Practices

  • Only run software from known reputable developers, preferably peer revived and audited code.
  • Download only from the links provided by the developer, preferably from the developers own site.
  • The inherent danger of a malicious miner app is that by design it has already all the tools needed to be very harmful, these include upload and download capabilities, there will not necessarily be anything we can detect immediately, as a malicious miner app can be triggered by something as simple as a specific network block number being reached or other delayed mechanisms.
  • There is no way to know if your wallet.dat/private keys are compromised, unless you always keep them safe guarded.
  • The above holds true for any software we download and use.