Re: [ANN] BitcoinDark (BTCD)--Sha-256/PoW-PoS hybrid/Bounty Opportunities
the order in the .conf file doesnt matter
Good to know, but already found a better way to solve my problem 
.there should be different checksums for each binary download
if people are compiling their own, then the same version wont necessarily mean identical binaries due to differences in system build env
I used the version from the OP, as I haven't got a clue yet how to build it. Checksums were fine when I downloaded to a clean machine. Worked on the clean machine, and when finished created the SHA-256 checksum.if people are compiling their own, then the same version wont necessarily mean identical binaries due to differences in system build env
Uploaded on my main machine.
Downloaded on a 2nd clean machine, and still gave the same checksum. So I fugured all should be ok.
it is a good idea about the general version number. not sure of the best way to have that across all OS and daemon and wallets
I would say that every release should have the same version on all platforms. Usually the first 3 numbers are/should be used for external releases, the forth number for internal builds.
So everytime a version is released, update at least the 3rd number. Current version is 1.0.0.0, so next should be at least 1.0.1.0.
I might (but still need to test that a bit further) even need the 2nd one to go up to keep the updates working as intended. If so, I'll keep using a different version for the installer only, just like I did now.