OK, any comments about the protocol proposal?
It's missing several things:- A way to know when a job has been started (and on which boards/chips) and completed (and how much of the nonce range was in fact scanned).
- A way to know which specific slave board and chip found the nonce in question.
- Access to temperature sensors.
- Control of any LEDs.
- Commands to get and/or control clock frequencies, voltages, etc.
- Some way to get error checking information/feedback, to make dynamic clocking more accurate.
Additionally, "cancel" is misspelled. IMO there is no real value for asking the device for its current hashrate.
It might be nice if the protocol were prepared to handle non-Bitcoin POW algorithms too, but this could probably be done as an extension.
Finally, if any vendors are actually willing to implement this protocol, KNK should get a BIP number assigned by gmaxwell and post the draft on the Bitcoin wiki for further review.
