Re: New getwork

Quote from: satoshi on November 24, 2010, 17:21:01 – It does not return work when you submit a possible hit, only when called without parameter. It would be immensely useful if you’d return if what I sent to the client actually was an actual hit. It makes it easier to […]

Read more

Version 0.3.17

Version 0.3.17 is now available. Changes: – new getwork, thanks m0mchil – added transaction fee setting in UI options menu – free transaction limits – sendtoaddress returns transaction id instead of “sent” – getaccountaddress <account> The UI transaction fee setting was easy since it was still there from 0.1.5 and […]

Read more

Re: New getwork

Quote from: jgarzik on November 24, 2010, 04:47:42 I suspect something weird going on with ByteReverse (or lack thereof). It’s quite unclear whether or not ‘data’ and ‘nonce’ must be byte-reversed, and in what way. getwork does the byte-reversing.  midstate, data and hash1 are already big-endian, and you pass data […]

Read more

Re: New getwork

I understand the use case for external miners, but I rather like the all-in-one approach. Will I still be able to compile in my own mining code? I really enjoyed the revamped interface you introduced some time ago, and would very much like to keep on using it. It’s not […]

Read more

New getwork

I uploaded a redesign of m0mchil’s getwork to SVN rev 189 (version 31601) m0mchil’s external bitcoin miner idea has solved a lot of problems.  GPU programming is immature and hard to compile, and I didn’t want to add additional dependencies to the build.  getwork allows these problems to be solved […]

Read more
1 2 3 4 5 6 58