From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WcyiY-0002Dm-8Q for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 15:04:10 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.49 as permitted sender) client-ip=209.85.216.49; envelope-from=alex.mizrahi@gmail.com; helo=mail-qa0-f49.google.com; Received: from mail-qa0-f49.google.com ([209.85.216.49]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WcyiU-0008Tf-4S for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 15:04:10 +0000 Received: by mail-qa0-f49.google.com with SMTP id j7so952237qaq.36 for ; Wed, 23 Apr 2014 08:04:00 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.224.73.136 with SMTP id q8mr32998584qaj.54.1398265440636; Wed, 23 Apr 2014 08:04:00 -0700 (PDT) Received: by 10.96.77.38 with HTTP; Wed, 23 Apr 2014 08:04:00 -0700 (PDT) In-Reply-To: References: Date: Wed, 23 Apr 2014 18:04:00 +0300 Message-ID: From: Alex Mizrahi To: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a11c3dc48e47cab04f7b70a2b X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (alex.mizrahi[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1WcyiU-0008Tf-4S 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Apr 2014 15:04:10 -0000 --001a11c3dc48e47cab04f7b70a2b Content-Type: text/plain; charset=UTF-8 This is outright ridiculous. Zero-confirmation double-spending is a small problem, and possible solutions are known. (E.g. trusted third party + multi-sig addresses for small-value transactions.) On the other hand, protocol changes like described above might have game-theoretical implications which are non-trivial and hard to understand. The above approach works as long as the majority of hashpower is honest, > defined to mean, working to stop double spending. This is the same security > property as described in the white paper, thus this introduces no new > security assumptions. > No. Bitcoin should work if miners are merely individually rational, i.e. they try to maximize their pay-offs without colluding with others. I guess word "honest" might have different meanings, that can be a source of confusing. 1. Honest -- not trying to destroy bitcoin 2. Honest -- following rules which are not required by the protocol --001a11c3dc48e47cab04f7b70a2b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
This is outright ridiculous.

Zero-confi= rmation double-spending is a small problem, and possible solutions are know= n. (E.g. trusted third party + multi-sig addresses for small-value transact= ions.)

On the other hand, protocol changes like described abov= e might have game-theoretical implications which are non-trivial and hard t= o understand.

The above approach wor= ks as long as the majority of hashpower is honest, defined to mean, working= to stop double spending. This is the same security property as described i= n the white paper, thus this introduces no new security assumptions.

No. Bitcoin should work if miners ar= e merely individually rational, i.e. they try to maximize their pay-offs wi= thout colluding with others.

I guess word "ho= nest" might have different meanings, that can be a source of confusing= .
1. Honest -- not trying to destroy bitcoin
2. Honest -- foll= owing rules which are not required by the protocol


--001a11c3dc48e47cab04f7b70a2b--