user323: As there are a couple endiannesses used by Bitcoin, what is the proper way to encode the data parameter for a getmemorypool JSON API call?

user659: Do you mean the data response for a getwork call?  Because getmemorypool only returns version, previousblockhash, transactions, coinbasevalue, coinbaseflags, time, mintime, curtime, and bits.
If so, I answered that here.

user942: The "data" is not a number (only numbers have endian issues), but the raw byte data of a valid block. You may wish to read over BIP 22, which is the Draft-status standard detailing the getmemorypool protocol.

323: <p>As there are a couple endiannesses used by Bitcoin, what is the proper way to encode the <code>data</code> parameter for a <code>getmemorypool</code> <a href="https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list" rel="nofollow">JSON API call</a>?</p>
 659: <p>Do you mean the <code>data</code> response for a <code>getwork</code> call?  Because <code>getmemorypool</code> only returns <code>version</code>, <code>previousblockhash</code>, <code>transactions</code>, <code>coinbasevalue</code>, <code>coinbaseflags</code>, <code>time</code>, <code>mintime</code>, <code>curtime</code>, and <code>bits</code>.</p>

<p>If so, I answered that <a href="https://bitcoin.stackexchange.com/a/2907/659">here</a>.</p>
 942: <p>The "data" is not a number (only numbers have endian issues), but the raw byte data of a valid block. You may wish to read over <a href="https://en.bitcoin.it/wiki/BIP_0022" rel="nofollow">BIP 22</a>, which is the Draft-status standard detailing the getmemorypool protocol.</p>
