# Gavin Andresen
# 2012-02-29 00:40:31
# https://bitcointalk.org/index.php?topic=64777.msg774467#msg774467

This would replace the existing JSON-RPC getmemorypool command? @p{par}


Code:
getmemorypool [data] @p{brk}
If [data] is not specified, returns data needed to construct a block to work on: @p{brk}
  "version" : block version @p{brk}
  "previousblockhash" : hash of current highest block @p{brk}
  "transactions" : contents of non-coinbase transactions that should be included in the next block @p{brk}
  "coinbasevalue" : maximum allowable input to coinbase transaction, including the generation award and transaction fees @p{brk}
  "coinbaseflags" : data that should be included in coinbase so support for new features can be judged @p{brk}
  "time" : timestamp appropriate for next block @p{brk}
  "mintime" : minimum timestamp appropriate for next block @p{brk}
  "curtime" : current timestamp @p{brk}
  "bits" : compressed target of next block @p{brk}
If [data] is specified, tries to solve the block and returns true if it was successful. @p{brk}

 @p{brk}
And a meta-question: are there any other implementations that will be supporting external mining via JSON-RPC soon? There's no reason to go through the whole BIP process to make a change or improvement to one implementation. @p{brk}