when can we get the cpuminer?
Exactly! Why can't we have the miner yet?
I would like a full tutorial on how to mine this coin before it is launched.
I just found this information about mining.
http://heavycoin.github.io/mining.htmlIt looks pretty good.
If you are mining on a pc with and using the gui that is...
The source won't be released until launch. We are trying to providing binaries (for pool mining software) ahead of the launch, so pool operators can make sure everything is up and running.
In addition to mining (and voting) with the GUI wallets, you can use an external miner. For that, we've created a Heavycoin fork of cpuminer.
Usage: minerd [OPTIONS]
Options:
-a, --algo=ALGO specify the algorithm to use
scrypt scrypt(1024, 1, 1) (default)
sha256d SHA-256d
heavy Heavycoin hash
-v, --vote=VOTE block reward vote
-m, --trust-pool trust the max block reward vote (maxvote) sent by the pool
The external miner gets to write his/her block reward vote into the block. The block reward vote is specified with the -v parameter.
Your vote cannot exceed the maximum allowed block reward vote of 1024. Also, if your vote exceeds the current maximum block reward vote, then you will generate invalid blocks. This is not really a problem because the maxvote only changes in the final (Sustain) phase of decentralized voting. At that distant future you will simply relaunch your external miners with at vote between 0 and 8.
For those unsatisfied with this, the -m option allows the external miner to automatically cap his vote to the maximum permitted vote of the current voting phase. For example if you had -v 1024 and the maxvote reported by the pool was 8, then your block reward vote would be capped to 8. However, we do not recommend using this option unless you really trust the pool (ie. you own it). A dishonest pool operator could try to cheat by sending out an artificially lower maxvote, which would cause all the votes from external miners with the -m flag to be capped at a false maxvote. So really don't use this flag unless you are the pool operator.
NoteFor pool mining, the block's vote could be set by the pool software or the external miners. However, we decided to make vote casting part of the external miner, rather than part of the pool software. If the vote for a given block were calculated and set by the pool software, then there would be scope for malicious pool operators to cheat and skew votes in a way that favors them. By allowing the external miners to write their votes directly into the block, we put the voting power in the hands of the individual miners, rather than the pool operators.
A malicious pool operator could still reject blocks from external miners whose votes they do not like; however, this condition would be easily (and publicly) detectable because of the discrepancy between the hashing power of the external miner and the number of his blocks accepted by the pool. It would be the same as stealing blocks or assigning a false shares. In practice it should be very hard for a pool to cheat like this without being found out and becoming very unpopular!
