I have finally got around to revising the BIP 22 draft, and would appreciate further review: https://en.bitcoin.it/wiki/BIP_0022
I believe this revision addresses Geir's last email in March, as well as some practical problems some pools recently came across. To summarize the changes from the last revision in March: - The submitblock(<data>, <params>) method is renamed to getmemorypool - Requesting a job now uses getmemorypool(<params>) to provide client capabilities and other information to the server - Longpolls use a parameter in the getmemorypool request, not necessarily a separate URI - The client can inform the server of its own size and sigop requirements in advance - The client can request detailed transaction data from the server, necessary to sanely manipulate the transactions included in the final block without discarding fees or making the block invalid due to not having enough - With both client and server support, blocks can be proposed before wasting time mining them, to ensure they are otherwise valid - Servers can be arranged into single logical services, with failover and load balancing (similar to the getwork X-Host-List and X-Switch-To extensions). You can see the full diff here: https://en.bitcoin.it/w/?title=BIP_0022&action=historysubmit&diff=26408&oldid=25544 Luke ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Bitcoin-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bitcoin-development
