Quote from: shads on July 06, 2011, 03:55:32 AM

Quote from: elmigranto on June 29, 2011, 07:13:33 PM

It's header in big-endian hexademical format with additional bytes for SHA256 (see wiki on SHA256 for details).

Can you give a link for this? I've search all over and can't find anywhere that explains how the padding should be done? I'm currently trying to work out how to turn a header in byte array form back into a valid getwork hex string.

FIPS 180-3

You want section 5. Note that the message length is stored in Intel's crazy-endian format.