Topic: Little endian values in Block-header (Read 168 times)
I have gone through your post and seen the information that you have shared here. But I got only minimal information from your article. Since I am interested to know more, share additional data ta the earliest. who provides cable service in my area
The Merkle root is also little-endian...
As to why, it's because the fields are read/written directly between memory and the socket, and that's how the data is ordered in memory. Integers are little-endian in memory because that's how the supported architectures do things. It's a little weird that hashes are stored little-endian, but Satoshi put most hashes in a uint256 type which behaved how you'd expect a 256-bit integer to behave on eg. x86, including little-endianness.
As to why, it's because the fields are read/written directly between memory and the socket, and that's how the data is ordered in memory. Integers are little-endian in memory because that's how the supported architectures do things. It's a little weird that hashes are stored little-endian, but Satoshi put most hashes in a uint256 type which behaved how you'd expect a 256-bit integer to behave on eg. x86, including little-endianness.
Does anyone have any idea why Satoshi made all values in the block-header stored as little endian in byte code except for the Merkle root? It is a frustrating thing when working with code and I can't figure out why it would have been done this way? Any guesses or thoughts or reasonings for this?
Jump to: