Proper getmemorypool data endianness?

Question

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?

score 2 · Answer 1 · answered Mar 05 '12 at 22:15

2

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.

answered Mar 05 '12 at 22:15

Luke-Jr

1,160
5
10

score 1 · Answer 2 · edited Apr 13 '17 at 12:47

1

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.

edited Apr 13 '17 at 12:47

Community

1

answered Feb 26 '12 at 05:05

Chris Moore

14,745
6
65
87

No, I'm specifically referring to getmemorypool call's `data` field, as in a whole, solved block, rather than just a block header. Maybe I shouldn't have called it "response", but a "parameter". – ThePiachu Feb 26 '12 at 05:37
2

In that case: it's a byte-per-byte encoding in hex of the serialized block, the same way it would be serialized on disk in blk0001.dat or on the network. – Pieter Wuille Mar 06 '12 at 00:58

Proper getmemorypool data endianness?

2 Answers2