<p>In KC705_experimental, the readme says the device should return 0E33337A and two other results. It just so happens the bit of test work described in the readme has three different solutions to it.  A mining script should return all three solutions to the server.</p>

<p>fpgaminer, the author of the KC705_experimental code, has written an addon for the Modular Python Bitcoin Miner project (MPBM) to mine using KC705 hardware.  If writing your own mining script you may want to refer to his work.  You can find more information here:  <a href="https://bitcointalk.org/index.php?topic=9047.msg2019538#msg2019538" rel="nofollow">https://bitcointalk.org/index.php?topic=9047.msg2019538#msg2019538</a></p>

CC BY-SA 3.0
2013-05-03T23:31:05.030Z
2013-05-03T23:31:05.030Z
user4790
<p>I make a getwork request and get back data, hash1, midstate, and target. Mining on a KC705 development FPGA board, and following the readme.md file here:<br>
<a href="https://github.com/progranism/Open-Source-FPGA-Bitcoin-Miner/tree/master/projects/KC705_experimental" rel="nofollow">https://github.com/progranism/Open-Source-FPGA-Bitcoin-Miner/tree/master/projects/KC705_experimental</a></p>

<p>I do a uart_write of a section of data plus the midstate, and that would return the golden nonces. Doing that does in fact return the 0E33337A as stated along with two others, 9CCDEF20 and ACBBA77F.</p>

<p>Now I start getting confused. Given the response from the getwork request and 3 nonces, what exactly am I submitting back? From what I gather, I am supposed to do a hash using each nonce, check it if it's smaller than the target, and if it is, submit that hash?</p>

CC BY-SA 3.0
2013-05-02T14:06:09.517Z
If you're working on a mining script for the KC705 I would be interested to see it. I need to do this myself. ox983745 at gmail dot com
user4790
<development><mining-technical-details><getwork><fpga>
Mining: GetWork, Get Nonce, ???, Submit Hash?
SJaguar13
# Mining: GetWork, Get Nonce, ???, Submit Hash?

(Asked by: username_0 on 2013-04-24)

I make a getwork request and get back data, hash1, midstate, and target. Mining on a KC705 development FPGA board, and following the readme.md file here:  
<https://github.com/progranism/Open-Source-FPGA-Bitcoin-Miner/tree/master/projects/KC705_experimental>

I do a uart\_write of a section of data plus the midstate, and that would return the golden nonces. Doing that does in fact return the 0E33337A as stated along with two others, 9CCDEF20 and ACBBA77F.

Now I start getting confused. Given the response from the getwork request and 3 nonces, what exactly am I submitting back? From what I gather, I am supposed to do a hash using each nonce, check it if it's smaller than the target, and if it is, submit that hash?

**Tags:** development, mining-technical-details, getwork, fpga

> **Comments:**
> **username_1**: If you're working on a mining script for the KC705 I would be interested to see it. I need to do this myself. ox983745 at gmail dot com  

---

## 1 answers

### Answer by username_1 on 2013-05-03. Score: 1

In KC705\_experimental, the readme says the device should return 0E33337A and two other results. It just so happens the bit of test work described in the readme has three different solutions to it. A mining script should return all three solutions to the server.

fpgaminer, the author of the KC705\_experimental code, has written an addon for the Modular Python Bitcoin Miner project (MPBM) to mine using KC705 hardware. If writing your own mining script you may want to refer to his work. You can find more information here: <https://bitcointalk.org/index.php?topic=9047.msg2019538#msg2019538>


---

