Getwork - Bitcoin Wiki

UPDATE: Virus found on my mining rig

Context here
I was able to run a wireshark on the packets and traced down what and where the data was coming from. This is the TCP Stream that lead me to 50btc
Authorization: Basic anJvZHJpZ3VlejQ0MkBvdXRsb29rLmNvbTpwYXNzd29yZA== Host: Accept: */* Accept-Encoding: deflate, gzip Content-type: application/json X-Mining-Extensions: longpoll midstate rollntime submitold Content-Length: 44 User-Agent: cgminer 2.10.4 {"method": "getwork", "params": [], "id":0} HTTP/1.1 200 OK server: 50BTC X-Long-Polling: X-Blocknum: 231342 X-Roll-NTime: expire=120 Content-Length: 607 Content-Type: application/json;charset=ISO-8859-1 { "error": null, "id": 0, "result": { "data": "000000025ecbc41aa5897932445af6485e044d24faedffe58daae1ae00000212000000007655b172b85920f3f03f8290b6abc4e6fb684bc374b3a89d6097a01a518fc45e516b00331a022fbe00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000", "hash1": "00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000", "midstate": "50810233b8406896d763a6a432c16bda68080ecf1740d2e5336d6292af334dad", "target": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffff00000000" } } 
So I emailed the pool and this is the reponse to me telling them they have fraudulent miners.
Hello, *!
Thanks ofr the feedback. Suspicious accounts was blocked, if you'll find any more bots, please let us know.
Your help is much appreciated! Best regards, team
Kudos to for taking care of the issue and if you find that your GPU is being used while your PC is idle start by looking at the task manager as regular virus programs will no detect miners yet. Malware Bytes will tag cgminer and others as PUP (Potentially unwanted programs) but this is only on a full scan. Track down the offending exe and before you delete it run a wireshark and see where it is mining too.
Be safe out there.
submitted by ruffneck123 to BitcoinMining [link] [comments]

Or did calculating the midstate count as the first hash computation? And when the nonce overflows, should I submit another getwork request or wait until I've checked the nonces in the range of [0, original_nonce_value)? (Assuming my analysis that the given nonce is 21474836481 is correct?) Lastly, if our target value from the getwork request is: Getwork ist komplizierter und läuft in ernster endian – /byte-Reihenfolge Durcheinander. Ersten Hinweis, dass die getwork-API ist optimiert, um die Geschwindigkeit der ersten Schritte der Bergbau. Die midstate und hash1 Werte sind für diese performance-Optimierungen und können ignoriert werden. Schauen Sie sich einfach die „Daten“. I'm looking for example getwork input and output of a successful block hash to verify a getwork client I've implemented. I'd also accept suggestions on better ways to verify this. I've looked at Recently I've been trying to implement some Bitcoin-related code, and I've stumbled upon a weird concept, a SHA-256 "midstate". Some explanation is given here.. The general concept is that Bitcoin relies on performing SHA hashing of a 128 byte data chunk many times, but only the second half of that chunk changes. Because getwork provides the data in little endian, and SHA256 works in big endian, for every 32-bit chunk you need to swap the byte order; Chop off the SHA-2 padding; for Bitcoin, you can just take the first 80 bytes, but otherwise you can find the correct length (in bits) as the last 64 bits of the (byteswapped) data

[index] [21184] [31069] [22397] [39729] [47308] [35618] [11533] [6548] [14059] [9150]