Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1R0OoV-0002vt-Sp for bitcoin-development@lists.sourceforge.net; Mon, 05 Sep 2011 02:21:31 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=voights@gmail.com; helo=mail-wy0-f175.google.com; Received: from mail-wy0-f175.google.com ([74.125.82.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1R0OoU-0000IZ-R2 for bitcoin-development@lists.sourceforge.net; Mon, 05 Sep 2011 02:21:31 +0000 Received: by wyf19 with SMTP id 19so4857211wyf.34 for ; Sun, 04 Sep 2011 19:21:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.188.194 with SMTP id a44mr675770wen.4.1315189284397; Sun, 04 Sep 2011 19:21:24 -0700 (PDT) Received: by 10.216.168.73 with HTTP; Sun, 4 Sep 2011 19:21:24 -0700 (PDT) Date: Sun, 4 Sep 2011 22:21:24 -0400 Message-ID: From: Forrest Voight To: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (voights[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service X-Headers-End: 1R0OoU-0000IZ-R2 Subject: [Bitcoin-development] Pull request for "getmemorypool" RPC call X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 02:21:32 -0000 (Moving here because forum thread at https://bitcointalk.org/index.php?topic=39088 didn't yield much discussion) Pull request: https://github.com/bitcoin/bitcoin/pull/476 Diff: https://github.com/bitcoin/bitcoin/pull/476/files This was originally a patch that returned bitcoin's memory pool as list of transaction hashes and the amount of total fees, but evolved into a full alternative to the "getwork" RPC call for clients that create their own generation transactions. Like getwork, this call calls CreateBlock and returns parts of it for mining, but instead of generating its own merkle tree, it returns all the information needed to create a generation transaction in addition to the full contents of other transactions that should be included. It, as is, has had some testing done with p2pool - it resulted the first p2pool generated block with transactions: http://blockexplorer.com/block/00000000000002436bd2ae60d67d6fc0dce44deba2ad739619a3d364f6283e64 Help text: getmemorypool [data] If [data] is not specified, returns data needed to construct a block to work on: "version" : block version "previousblockhash" : hash of current highest block "transactions" : contents of non-coinbase transactions that should be included in the next block "coinbasevalue" : maximum allowable input to coinbase transaction, including the generation award and transaction fees "time" : timestamp appropriate for next block "bits" : compressed target of next block If [data] is specified, tries to solve the block and returns true if it was successful. Thank you, Forrest Voight