From mboxrd@z Thu Jan 1 00:00:00 1970 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 1UjwIz-0001Ao-LH for bitcoin-development@lists.sourceforge.net; Tue, 04 Jun 2013 18:50:01 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.128.41 as permitted sender) client-ip=209.85.128.41; envelope-from=jgarzik@bitpay.com; helo=mail-qe0-f41.google.com; Received: from mail-qe0-f41.google.com ([209.85.128.41]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UjwIx-0004Xi-VY for bitcoin-development@lists.sourceforge.net; Tue, 04 Jun 2013 18:50:01 +0000 Received: by mail-qe0-f41.google.com with SMTP id b4so452464qen.0 for ; Tue, 04 Jun 2013 11:49:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=O/3CjdM01qphRE2KoM9t0gH1GutqbpmR+bxzaGp8juI=; b=HW/gwtclWIeGZcFFvWuqrxLWl2PWj1Iy0b4F4YEei/vJPsN0MRDi/A59Y+JyJHGAr5 t5R9RhsFj4PL5b218GujQ6GIQzDfjHPOCOW3XXi75PtUHavqngZbIPcFoVZkRF6bF5E5 FDwUqSGLlvzPc4xsu35gybEDRTW/0ljoJ76evIZoY4Ch0m2lAoAbhrm06B3aZbHB6tnY C2DOA4xHrLkFZejVYABm0/tgFquT9KZxb6kVZ1aW0bH9qH9sI2KKihPy1P4dEgBvoTSb 8yKWLC1pt9we6JdiQTVC8/OFmYW4Mn/67Ay3OMiYm9+H3wAGY6xJlY3MvYbikNB/wKag rnQQ== MIME-Version: 1.0 X-Received: by 10.229.178.69 with SMTP id bl5mr1880893qcb.40.1370371794432; Tue, 04 Jun 2013 11:49:54 -0700 (PDT) Received: by 10.49.2.102 with HTTP; Tue, 4 Jun 2013 11:49:54 -0700 (PDT) In-Reply-To: <20130604183652.GI45035@giles.gnomon.org.uk> References: <20130601193036.GA13873@savin> <20130602214553.GA11528@netbook.cypherspace.org> <20130604183652.GI45035@giles.gnomon.org.uk> Date: Tue, 4 Jun 2013 14:49:54 -0400 Message-ID: From: Jeff Garzik To: Roy Badami Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmwUkC7LvJhL80Ye11R0qyW7UVxRJgVU/euA+a8Q3AcEAfKG8xhUU3UZtodjUDDuCTVKksp 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: 1UjwIx-0004Xi-VY Cc: Bitcoin-Dev Subject: Re: [Bitcoin-development] Proposal: soft-fork to make anyone-can-spend outputs unspendable for 100 blocks 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: Tue, 04 Jun 2013 18:50:01 -0000 On Tue, Jun 4, 2013 at 2:36 PM, Roy Badami wrote: >> Sure they are paying themselves, but given bitcoin network >> difficulty is uso high, simply obtaining payments-go-myself-as-miner >> transactions is itself difficult. > > Not for pool operators it isn't. Nor for people buying hashing power > from a GPUMAX-type service, if such services still exist (or should > they exist again in future). Re-read what I wrote. That's perfectly OK. It is analogous to a pool operator receiving merged mined coins, each time they mine a bitcoin block. If you achieve the very high difficulty needed to create a valid bitcoin block, you have achieved a very high bar. -- Jeff Garzik Senior Software Engineer and open source evangelist BitPay, Inc. https://bitpay.com/