1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
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 <jgarzik@bitpay.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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>
<CAJHLa0P2qARDGk45Cs0jThp14J+YVvxRGE=wZMhO1XMemP-cWA@mail.gmail.com>
<CAPaL=UUJ+Qu2ejXO6YYOzzDW0jPUpCPAmcw4j30niaT2e7+=Nw@mail.gmail.com>
<CAJHLa0PRNxS7K3YeCx_eXkZQdO8vOCefuGyXMXD7ESq0QEhr+g@mail.gmail.com>
<20130604183652.GI45035@giles.gnomon.org.uk>
Date: Tue, 4 Jun 2013 14:49:54 -0400
Message-ID: <CAJHLa0PjAU-MWfUNRtK9zysQdLsCnNx3EiUjdbqQcCcco=g1=A@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Roy Badami <roy@gnomon.org.uk>
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 <bitcoin-development@lists.sourceforge.net>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2013 18:50:01 -0000
On Tue, Jun 4, 2013 at 2:36 PM, Roy Badami <roy@gnomon.org.uk> 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/
|
