Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VCUmS-0005je-8l for bitcoin-development@lists.sourceforge.net; Thu, 22 Aug 2013 13:18:28 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com designates 74.125.82.179 as permitted sender) client-ip=74.125.82.179; envelope-from=jgarzik@bitpay.com; helo=mail-we0-f179.google.com; Received: from mail-we0-f179.google.com ([74.125.82.179]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VCUmQ-0007PZ-4G for bitcoin-development@lists.sourceforge.net; Thu, 22 Aug 2013 13:18:28 +0000 Received: by mail-we0-f179.google.com with SMTP id t58so1679318wes.10 for ; Thu, 22 Aug 2013 06:18:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=GXyjnZi8PXEValWaZLVUGV9JU63PBZ//TOVlQOwZdwY=; b=LBq8KhUSp8r8R1YVhJi/ekbmGIEGUIkHmP5ke4ZR/7fqzpsaCx0ss0gtUjfWQTF9fR RC9IHJxyjtVYVCIDUKdEAtHKJQPySG3+hy00kmxtxXRLfa9C694yUsOmwv5pBVlmTpcD dKNxMME9g8dRz4x+v/c6Rlz4fRef1nu76FnxfCOuvtMBgeDUgdz4mFY1o0SaFs764ymc gUfHu6eNNM/b5uuRIYwPZMcR7FdQ1nWOOXPcmtEHjTUS8rGe1UpYvprcWUtkr5ZZpwyZ 2uWjCQisWgjxYDl5e/GusDHpniOfalU6Vy9f8MRNN/bpgx3o5RSdHM1vclvG6+bHskr0 0xOg== X-Gm-Message-State: ALoCoQnm9Ja9YGHSPiQy33KyCfk0jJOs2g6oyOOhzS7tbgTc9fkxQLH/uenkRLEA+i1ll16xjMaE MIME-Version: 1.0 X-Received: by 10.194.219.38 with SMTP id pl6mr1954781wjc.47.1377177499942; Thu, 22 Aug 2013 06:18:19 -0700 (PDT) Received: by 10.194.23.1 with HTTP; Thu, 22 Aug 2013 06:18:19 -0700 (PDT) In-Reply-To: References: <1377120278.34996.YahooMailNeo@web124501.mail.ne1.yahoo.com> <6e1e64615be421f47a74bcc427a13485@astutium.com> Date: Thu, 22 Aug 2013 09:18:19 -0400 Message-ID: From: Jeff Garzik To: Maciej Trebacz 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 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 X-Headers-End: 1VCUmQ-0007PZ-4G Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Proposal: remove "getwork" RPC from bitcoind 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: Thu, 22 Aug 2013 13:18:28 -0000 On Thu, Aug 22, 2013 at 5:36 AM, Maciej Trebacz wrote: > Will removing "getwork" from the client impact the "setgenerate" RPC call? > I.e. would you still be able to generate coins on testnet-in-a-box this way, > or would you need a dedicated miner for that? testnet-in-a-box is very > useful for testing and easy to setup, it would be great if it stays that way Yes, that is currently being discussed in a separate pull request. My pull request does not impact setgenerate, but an added proposal does remove the internal miner completely. -- Jeff Garzik Senior Software Engineer and open source evangelist BitPay, Inc. https://bitpay.com/