diff options
| author | Mike Hearn <mike@plan99.net> | 2014-04-24 16:09:31 +0200 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2014-04-24 14:09:37 +0000 |
| commit | e5d2b80fe7f03a0040c725c313bb038937a2c5e1 (patch) | |
| tree | e58c4ccfa5dce2e3e7b3972d4ad5b325f0126f2c | |
| parent | da9a592b9ae5976c03d07cf08a972c7446714433 (diff) | |
| download | pi-bitcoindev-e5d2b80fe7f03a0040c725c313bb038937a2c5e1.tar.gz pi-bitcoindev-e5d2b80fe7f03a0040c725c313bb038937a2c5e1.zip | |
Re: [Bitcoin-development] Coinbase reallocation to discourage Finney attacks
| -rw-r--r-- | 85/49f7a13ce4ae8e3dd90005c4459d6c2963d643 | 113 |
1 files changed, 113 insertions, 0 deletions
diff --git a/85/49f7a13ce4ae8e3dd90005c4459d6c2963d643 b/85/49f7a13ce4ae8e3dd90005c4459d6c2963d643 new file mode 100644 index 000000000..6cbf37983 --- /dev/null +++ b/85/49f7a13ce4ae8e3dd90005c4459d6c2963d643 @@ -0,0 +1,113 @@ +Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] + helo=mx.sourceforge.net) + by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <mh.in.england@gmail.com>) id 1WdKLJ-0002Pd-L6 + for bitcoin-development@lists.sourceforge.net; + Thu, 24 Apr 2014 14:09:37 +0000 +Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.214.177 as permitted sender) + client-ip=209.85.214.177; envelope-from=mh.in.england@gmail.com; + helo=mail-ob0-f177.google.com; +Received: from mail-ob0-f177.google.com ([209.85.214.177]) + by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1WdKLI-0007iU-UB + for bitcoin-development@lists.sourceforge.net; + Thu, 24 Apr 2014 14:09:37 +0000 +Received: by mail-ob0-f177.google.com with SMTP id wp18so2631315obc.36 + for <bitcoin-development@lists.sourceforge.net>; + Thu, 24 Apr 2014 07:09:31 -0700 (PDT) +MIME-Version: 1.0 +X-Received: by 10.182.236.162 with SMTP id uv2mr1748419obc.40.1398348571602; + Thu, 24 Apr 2014 07:09:31 -0700 (PDT) +Sender: mh.in.england@gmail.com +Received: by 10.76.96.180 with HTTP; Thu, 24 Apr 2014 07:09:31 -0700 (PDT) +In-Reply-To: <20140424134441.GE16884@savin> +References: <CANEZrP0szimdFSk23aMfO8p2Xtgfbm6kZ=x3rmdPDFUD73xHMg@mail.gmail.com> + <CAAS2fgTS65b0mfJakEA5s3xJHuWU2BDW8MbEVgMFMNz8YAmEiA@mail.gmail.com> + <CANEZrP15DDdfT+o5jVKMO=tGTvHYx53yzhXfaVyzq7imfwJsZQ@mail.gmail.com> + <CAE28kUSLXG0y350gMiwnv0CoOHUorMgLup9TG77Mjj+BJcuowA@mail.gmail.com> + <CANEZrP0j0KoLUB+SE+W3fL8vTKay0niqoeQ38RKnU9cyGgvvYw@mail.gmail.com> + <CAAS2fgQV0=QfCWhwVh6-mw=eg9MDd1E21P_7rFAnGp0P43c1Fw@mail.gmail.com> + <CANEZrP3vT6Q72X6PrcDQ8_fDeF90WmV4-M045Ac=kJY+PhuAdg@mail.gmail.com> + <CAAS2fgQFx7-0vZ2AR3RnLORZZCqjBFHyUBqj688Jrz8OuMYPKA@mail.gmail.com> + <CANEZrP18=Y5EBcfR-sHumVvU3-yqYr1tuhr_J4ieG817HOpE=g@mail.gmail.com> + <20140424134441.GE16884@savin> +Date: Thu, 24 Apr 2014 16:09:31 +0200 +X-Google-Sender-Auth: 55aWfC4JDmhugYuMTDJ0DUoFYa4 +Message-ID: <CANEZrP0Qmmrs5dzQ8N6FGL1K3W0A0XWBqtkPTFOgU_rXDvc+sQ@mail.gmail.com> +From: Mike Hearn <mike@plan99.net> +To: Peter Todd <pete@petertodd.org> +Content-Type: multipart/alternative; boundary=001a11c2eb52e1fa3604f7ca65a7 +X-Spam-Score: -0.5 (/) +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 + (mh.in.england[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + 1.0 HTML_MESSAGE BODY: HTML included in message + 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: 1WdKLI-0007iU-UB +Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] Coinbase reallocation to discourage + Finney attacks +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: Thu, 24 Apr 2014 14:09:37 -0000 + +--001a11c2eb52e1fa3604f7ca65a7 +Content-Type: text/plain; charset=UTF-8 + +> +> Like I said before, that leads to the obvious next step of +> deleting/stealing their coinbases if they don't identify themselves. +> + +And as I said before, that's a huge leap. A majority of miners deciding +double spending needs tougher enforcement doesn't imply they also think all +miners should identify themselves. Those are unrelated things. + +This kind of totally unsupported "obvious next step" argument can be +applied to any proposal in any walk of life. We developed SPV clients? The +obvious next step is that miners have to stop being anonymous. We developed +floating fees? The obvious next step is that miners have to stop being +anonymous. The prior arguments sound absurd exactly because they're not +obvious or even logical - same as this. + +--001a11c2eb52e1fa3604f7ca65a7 +Content-Type: text/html; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo= +ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c= +cc solid;padding-left:1ex"><div class=3D"">Like I said before, that leads t= +o the obvious next step of<br> +</div> +deleting/stealing their coinbases if they don't identify themselves.<br= +></blockquote><div><br></div><div>And as I said before, that's a huge l= +eap. A majority of miners deciding double spending needs tougher enforcemen= +t doesn't imply they also think all miners should identify themselves. = +Those are unrelated things.</div> +<div><br></div><div>This kind of totally unsupported "obvious next ste= +p" argument can be applied to any proposal in any walk of life. We dev= +eloped SPV clients? The obvious next step is that miners have to stop being= + anonymous. We developed floating fees? The obvious next step is that miner= +s have to stop being anonymous. The prior arguments sound absurd exactly be= +cause they're not obvious or even logical - same as this.</div> +<div><br></div><div><br></div></div></div></div> + +--001a11c2eb52e1fa3604f7ca65a7-- + + |