Edit: A separate thread has been created: https://bitcointalk.org/index.php?topic=663828Betarigs Dual API Programming Challenge -- 2 BTC Bounty total!Betarigs API Programming Challenge number 1 : Mass rental script -- 1 BTC Bounty!1 BTC will be awarded to the submitted script selected by Betarigs that:
1/ Work on all OSes (Win/Mac/Linux) on the command line.
2/ Use Betarigs and Coinbase API (whose API keys will be stored either in a config file, or in the script itself)
3/ Takes as input:
- An target amount of Mh/s to rent
- A mining algorithm (X11, Scrypt, ...)
- A maximum price in BTC/Mh/day of the rigs to rent
- A given duration in hours (to be taken in the list of available Betarigs durations; so all rigs would be rented for that duration)
- A target pool URL, worker name and worker password
4/ Have the following behavior:
- The script will use the Betarigs API to create rentals up to the target amount of Mh/s to rent (unless the maximum price in BTC/Mh/day is reached)
- The script will then use the Coinbase API to pay for these rentals (use the "idem" parameter on the Coinbase payment API to prevent double payments!!!)
- The script will then, without waiting for the payment to be confirmed by Betarigs, put the pool infos (URL, worker name, password) on the created rentals
5/ As output, the script will have launched and paid mining rentals based on the input parameters.
6/ The script must be sufficiently verbose to inform what it is doing.
7/ The script must have a dry-run mode: It would be an option that, if used, will simulate the rental creation and payment, but not actually do it.
8/ The script will have to handle all the error scenarios (no more rentals under the specified price, rig got rented by someone else, Coinbase API returning an error ("You are sending too fast, wait a bit"), ...)
9/ The submission of participants will be assessed on the forum thread
https://bitcointalk.org/index.php?topic=663828 ; and any feedback by Betarigs about bugs/missing features will be posted on this forum.
10/ The resulting script will have to be open-source, and hosted on Github.
11/ The actual winner will be assessed by the Betarigs team. Code quality, proper output, handling of errors, fullfillment of requirements, will be criterias used to determine a winner. There is no time limit, a winner can be designated as soon as a proper script is created.
Betarigs API Programming Challenge number 2 : Mass rental website -- 1 BTC Bounty!1 BTC will be awarded to the submitted website selected by Betarigs that:
1/ Use PHP as a language. The full project needs to be fully in PHP. A Symfony 2 setup with bundles will be
strongly preferred.
2/ Use Betarigs and Coinbase API (whose API keys will be stored in a config file)
3/ Takes as input, in a form in a web page:
- An target amount of Mh/s to rent
- A mining algorithm (X11, Scrypt, ...)
- A maximum price in BTC/Mh/day of the rigs to rent
- A given duration in hours (to be taken in the list of available Betarigs durations; so all rigs would be rented for that duration)
- A target pool URL, worker name and worker password
4/ Have the following behavior:
- The website will use the Betarigs API to create rentals up to the target amount of Mh/s to rent (unless the maximum price in BTC/Mh/day is reached)
- The website will then use the Coinbase API to pay for these rentals (use the "idem" parameter on the Coinbase payment API to prevent double payments!!!)
- The website will then, without waiting for the payment to be confirmed by Betarigs, put the pool infos (URL, worker name, password) on the created rentals
5/ As output, the web page will have launched and paid mining rentals based on the input parameters.
6/ The web page should display the various actions taken as a result of the form submission (which rigs were rented, etc)
7/ The website must have a dry-run mode: It would be an option that, if used, will simulate the rental creation and payment, but not actually do it.
8/ The web page should then be able to display the status of the currently rented rigs, and to mass update their pool credentials.
9/ The web page will have to handle all the error scenarios (no more rentals under the specified price, rig got rented by someone else, Coinbase API returning an error ("You are sending too fast, wait a bit"), ...)
10/ The submission of participants will be assessed on the forum thread
https://bitcointalk.org/index.php?topic=663828 ; and any feedback by Betarigs about bugs/missing features will be posted on this forum.
11/ The resulting website will have to be open-source, and hosted on Github.
12/ The website code will have to work standalone (i.e. only a database connection, and a composer install will be needed).
13/ The website will NOT need to work for external visitors. The website will primarily need to work for his owner, the admin. (Of course, it's a big bonus if it works for external visitors, but that's a much larger work, so it's not required)
14/ The actual winner will be assessed by the Betarigs team. Website aestetics, reusability, code quality, proper output, handling of errors, fullfillment of requirements, will be criterias used to determine a winner. There is no time limit, a winner can be designated as soon as a proper website is created.
Good luck!REVISIONS : Specs may be slightly modified (mainly adding more details), and the change list will be listed here:
- A separate thread has been created:
https://bitcointalk.org/index.php?topic=663828
