This project has 3 parts: 1) a command-line program, 2) some written instructions on using the output of the program, and 3) some brief guidelines on the best way to choose input values.
1. The command-line program would ask for the following input values:
item: example value
timestamp: Fin Times 24/Jan/2014 US softens tone on any Snowden deal
time: 1390585860
public signature: 040184710fa689ad5023690c80f3a49c8f13f8d45b8c857fbcbc8bc4a8e4d3eb4b10f4d4604fa08dce601aaf0f470216fe1b51850b4acf21b179c45070ac7b03a9
initial subsidy: 1996
target timespan: 3.5 * 24 * 60 * 60 (3.5 days)
target spacing: 2.5 * 60 (2.5 minutes)
and then generate appropriate output. The output might be values printed to the screen, data files, or both. We expect that the output values would include the nonce and the genesis block hash, possibly among other things.
2. The written instructions would briefly tell us how to take the output of the program and integrate it into our codebase and our deployment process. It is perfectly ok if this integration is to be done manually by us (editing code, copying files, etc). We’re just looking for a couple of sentences here.
3. The guidelines would be any brief general instructions you think are worth knowing when we generate a new genesis block, for example, the advantages/disadvantages of setting the input values to certain numbers. We’re just looking for a couple of sentences here as well.
Hi John, hi Adam,
based on the basecamp discussion, my bid is based on the following
preassumptions:
Parameters for genesis block generation:
* timestamp string
* unix timestamp
* public signature
* initial subsidy
* initial difficulty
The unix timestamp might be slightly changed by the genesis block
mining process if necessary.
Parameters with mere documentation regarding how/where to change the
source (not related to genesis block content:
* target timespan
* target spacing
Please inform me if this would be as expected, or if changes are
needed.
Best regards,
Isidor