diff options
| author | Peter Todd <pete@petertodd.org> | 2014-04-23 11:55:31 -0400 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2014-04-23 15:55:45 +0000 |
| commit | 25f9e2063e8e284685fdadf4aa2be52fc29dcec9 (patch) | |
| tree | 41639fed9bf0912a8e3a2b157fa07770c38b161f | |
| parent | f43dab0015ace9da89706196bed085a282ea620a (diff) | |
| download | pi-bitcoindev-25f9e2063e8e284685fdadf4aa2be52fc29dcec9.tar.gz pi-bitcoindev-25f9e2063e8e284685fdadf4aa2be52fc29dcec9.zip | |
Re: [Bitcoin-development] Coinbase reallocation to discourage Finney attacks
| -rw-r--r-- | 99/763520cab7c50c4dd8bf288ffb2c1e143bd548 | 130 |
1 files changed, 130 insertions, 0 deletions
diff --git a/99/763520cab7c50c4dd8bf288ffb2c1e143bd548 b/99/763520cab7c50c4dd8bf288ffb2c1e143bd548 new file mode 100644 index 000000000..5a2f84e91 --- /dev/null +++ b/99/763520cab7c50c4dd8bf288ffb2c1e143bd548 @@ -0,0 +1,130 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <pete@petertodd.org>) id 1WczWS-0005uo-W6 + for bitcoin-development@lists.sourceforge.net; + Wed, 23 Apr 2014 15:55:45 +0000 +Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org + designates 62.13.148.107 as permitted sender) + client-ip=62.13.148.107; envelope-from=pete@petertodd.org; + helo=outmail148107.authsmtp.com; +Received: from outmail148107.authsmtp.com ([62.13.148.107]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) + id 1WczWR-0000ar-U5 for bitcoin-development@lists.sourceforge.net; + Wed, 23 Apr 2014 15:55:44 +0000 +Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) + by punt18.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s3NFtaUr085166; + Wed, 23 Apr 2014 16:55:36 +0100 (BST) +Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109]) + (authenticated bits=128) + by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s3NFtXWq069166 + (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); + Wed, 23 Apr 2014 16:55:35 +0100 (BST) +Date: Wed, 23 Apr 2014 11:55:31 -0400 +From: Peter Todd <pete@petertodd.org> +To: Pieter Wuille <pieter.wuille@gmail.com> +Message-ID: <20140423155531.GA32545@savin> +References: <CANEZrP0szimdFSk23aMfO8p2Xtgfbm6kZ=x3rmdPDFUD73xHMg@mail.gmail.com> + <5357DD8F.6050308@gmail.com> + <CAPg+sBjY4fTTQqkn6=NyU5Fm-54-CnFRHLdEL=3KsUeXBofTqA@mail.gmail.com> +MIME-Version: 1.0 +Content-Type: multipart/signed; micalg=pgp-sha256; + protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" +Content-Disposition: inline +In-Reply-To: <CAPg+sBjY4fTTQqkn6=NyU5Fm-54-CnFRHLdEL=3KsUeXBofTqA@mail.gmail.com> +User-Agent: Mutt/1.5.21 (2010-09-15) +X-Server-Quench: b5aeb4d8-caff-11e3-b802-002590a15da7 +X-AuthReport-Spam: If SPAM / abuse - report it at: + http://www.authsmtp.com/abuse +X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR + aQdMdAEUGUUGAgsB AmIbWlJeVVh7WmU7 bAxPbAVDY01GQQRq + WVdMSlVNFUsrAmJ3 QnZ5Exl0fgRAfjBx Z0VrXD4JWRUvJ0Ip + SlMHRDtQeGZhPWMC AkhYdR5UcAFPdx8U a1UrBXRDAzANdhES + HhM4ODE3eDlSNilR RRkIIFQOdA4gGT86 TRkZEH01EEQBQyI4 + JgAnLVhUAEFZPkQp Olw8Q1sXPlc8CwtY ElAvSCZFO1AKRDFD +X-Authentic-SMTP: 61633532353630.1023:706 +X-AuthFastPath: 0 (Was 255) +X-AuthSMTP-Origin: 76.10.178.109/587 +X-AuthVirus-Status: No virus detected - but ensure you scan with your own + anti-virus system. +X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record +X-Headers-End: 1WczWR-0000ar-U5 +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: Wed, 23 Apr 2014 15:55:45 -0000 + + +--vtzGhvizbBRQ85DL +Content-Type: text/plain; charset=us-ascii +Content-Disposition: inline +Content-Transfer-Encoding: quoted-printable + +On Wed, Apr 23, 2014 at 05:41:26PM +0200, Pieter Wuille wrote: +> On Wed, Apr 23, 2014 at 5:34 PM, Kevin <kevinsisco61784@gmail.com> wrote: +> > I have some questions: +> > 1. How can we work towards solving the double-spending problem? +>=20 +> We have this awesome technology that solves the double-spending +> problem. It's called a blockchain. Of course, it only works when +> transactions are actually in a block. +>=20 +> This issue is about double-spending preventing before they're +> confirmed. This is (and has always been) just a best-effort mechanism +> in the network. +>=20 +> > 2. Is it possible to "scan" for double-spending and correct it? +>=20 +> That is what is being proposed here, by introducing a mechanism where +> miners can vote to penalize other miners if they seem to allow (too +> many?) double spends. + +Worse, it's a mechanism where miners can vote to penalize other miners +for any reason at all. Nothing in the mechanism requires any proof that +a double-spend happened, nor can it. Even if you require the simple +"two signatures for same output" mechanism, that just proves the +existance of a second signature, and says nothing at all about whether +or not that signature was ever broadcast on any network. + +--=20 +'peter'[:-1]@petertodd.org +0000000000000000278031f86c71265f6eaf1fe9ce6cc831dc4f956676a7a7f7 + +--vtzGhvizbBRQ85DL +Content-Type: application/pgp-signature; name="signature.asc" +Content-Description: Digital signature + +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.14 (GNU/Linux) + +iQGrBAEBCACVBQJTV+JvXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw +MDAwMDAwMDAwMDAwMDAyNzgwMzFmODZjNzEyNjVmNmVhZjFmZTljZTZjYzgzMWRj +NGY5NTY2NzZhN2E3ZjcvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0 +ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfvEkAgAvPK1RNoAD/x5W9QuIaH2vZSx +mWdY5Nq4vDGjH36aFOsKaXUOO2jXF7LXmRmLcc/edNY2+GsNrfEYOU8u+CtiFZ/K +h7A2NwZI85VxUHZ87YPBVRtlKDXQVpAngrhG8r3yk7e9E5RpoNWgDWI9lirK9EW5 +Pcmsfz8/uL1621KqudLqEHZK2+R6Fb9CY+9sem4FKb9mijYgHWGjM7ze5Q5YcEl5 +/MNmjd7RI1zTtJP7mxj6GdvvLRQWOuaYYOi+NBDcxQ1Mp2zlWjgwIS9o+I1p6g3Q +VgVGd3N7agNmwerH++k8mGQ9ltTE6CnWMeDXojXrBaEIU0Gpq0vIku1rOUqGPg== +=EtaT +-----END PGP SIGNATURE----- + +--vtzGhvizbBRQ85DL-- + + |