Author: Luke-Jr 2012-03-04 01:04:29
Published on: 2012-03-04T01:04:29+00:00
Geir Harald Hansen reported a race condition in long polling currently implemented in pools. Double block changes are common with merged mining. He suggested adding "longpollid" in long poll responses and the last seen longpollid should be included by the client in future long poll requests. Another useful value in the getmemorypool response would be "height" so that the miner can include the correct height in the coinbase. Geir also suggested explaining how target vs. fulltarget works. However, this addition of parameters to getmemorypool itself breaks compatibility with bitcoind 0.5 and using HTTP headers makes it HTTP-specific again. It was recommended that some things should be optional for a client to implement but doing this safely needs some way for clients to communicate capabilities to the server. Finally, it was discussed that "noncerange" is of limited use and there's a good chance of getting the endianness wrong.
Updated on: 2023-06-06T03:19:46.943556+00:00