None of these settings can be changed after a BP has been created, although you can add more ether or log additional payer statements. So double-check everything for typos, and make sure there aren't any extra or missing zeros in your ether amounts!
As BPs themselves are new methods of payment, there isn't a lot of experimental data: your mileage may vary. Here, we'll go through each input and talk about what has worked for us in the past.
This is the address that will control the payment. In most cases this will be your address. Note that you can double-click this input to auto-fill with your current Ethereum address.
This will appear at the top of the BP on the interact page, as well as in the list of BPs on the browse page. This is displayed as a single line of no more than 100 characters, so we suggest keeping the title under this limit.
The title, like all of these fields, cannot be edited after creation! So make sure there aren't any typos or spelling errors.
If a worker commits, this is how much you're committed to spending (or burning). If no one commits you can recover this payment and at any time you can add more funds.
For a worker to commit to the BP, they must deposit this amount into the BP. At that point you'll be able to release or burn the total amount in the BP, which will be your initial payment plus the worker's deposit.
As a starting point, we recommend setting this to between 1/3 and 2/3 of the payment amount.
Higher service deposits mean it will take longer to find a worker, but the worker will be more confident and committed. Too high, and no one will commit at all; too low, and you risk getting incompetent, lazy, or dishonest workers.
This is the amount of time, after a worker has committed, that the BP will wait for input from you before the worker can trigger an auto-release. You can delay this timeout as many times as you want, resetting the timer to the full amount you set here. This is essentially to protect workers from "lazy payers" who don't bother to return to the payment regardless of whether the service was rendered effectively.
The shorter this timeout is, the more attractive the BP will be to workers; the longer it is, the less often you'll have to babysit the BP to make sure it doesn't auto-release before the worker has completed the job.
We recommend setting this at least as long as you expect the work to take, or possibly twice or three times as long. For a payer without an established reputation, a short auto-release timeout helps convince prospective workers that they are protected from a lazy payer.
For established payers, this is less essential, and can be set much longer.
You can set this value to decimal amounts, such as 0.1 days.
This is where you give more detail on the work you want done. Good initial statements have the following characteristics: