The Rules

Submitting Interest

An interested party should register interest on the registration form for the bounty they are interested in working on. This does not hold a place for submissions but lets the administration staff gauge interest in a project and lets the backers of said project know if there are people working towards it. It also lets you know how many others are potentially competing against you.
This step is in no way required to claim the purse for a given bounty.

Judgment on bounty’s will be based on The Gatalog’s beta testing criteria as well as the win conditions specified on the bounty page.
Contact an admin on The Gatalog’s chat to open a beta testing room.
The package submitted to the admins must contain
- Original CAD in its native format
- STL files
- Step Files
- A readme containing
  - Print settings
  - material requirements
  - a BOM/shopping list
  - additional tooling
  - additional supporting information
There may be a requirement for additional proof of function video to be submitted.
Complete the beta testing process with third party validation.
Release via The Gatalog.
A maximum of 3 bounty submission betas will be open at any given time. You may still open a beta room for your project but it will not be tracked for the bounty unless a previous submitter withdraws and you as a developer make a request.
Transferring of lead developers and projects between rooms is prohibited.
Projects, and conditions will vary based on the bounty at hand and may require slight modifications to the claim conditions. Those based on the bounty itself will be updated to the win condition list as they become apparent. Those stemming from a developers particular implementation of features will be specified to the developer directly.

Entries are timestamped based on the time the completed release package is submitted to the admin review team on the gatalog chat.
Once a package has been submitted it will be reviewed for completeness by the admin.
Only 1 package for a submission will be reviewed at a time.
If an issue is found the package will be rejected and the developer will have 24hrs to respond with the required updates.
If they do not respond, the developer will loose their review slot and the submission time will reset opening an opportunity for other competing developers to submit their packages.
Once the administrative panel has reached a majority consensus that the package is complete and has met the requirements established in the bounty, they will notify the CTRLPew and the Developer.
Upon completion of the beta process and release via The Gatalog the purse will be awarded.

Once the bounty is closed the winner of the purse will be notified via the administrator on the communit y chat.
If the winner does not respond within 15 days the bounty will be forfeited and transferred to the community BTC pool.
The winner will need to provide a BTC wallet for the bounty purse.
Transfer fees will be deducted from the bounty purse at the time of transfer.