From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WwdZn-0000JC-6k for bitcoin-development@lists.sourceforge.net; Mon, 16 Jun 2014 20:32:23 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.174 as permitted sender) client-ip=209.85.214.174; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f174.google.com; Received: from mail-ob0-f174.google.com ([209.85.214.174]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WwdZk-0002ab-Sk for bitcoin-development@lists.sourceforge.net; Mon, 16 Jun 2014 20:32:22 +0000 Received: by mail-ob0-f174.google.com with SMTP id va2so6321723obc.5 for ; Mon, 16 Jun 2014 13:32:15 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.24.230 with SMTP id x6mr4714151obf.81.1402950735260; Mon, 16 Jun 2014 13:32:15 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.71.162 with HTTP; Mon, 16 Jun 2014 13:32:15 -0700 (PDT) In-Reply-To: References: Date: Mon, 16 Jun 2014 22:32:15 +0200 X-Google-Sender-Auth: 3fvzfOxUrG3lssDmvnpzeSHh6S8 Message-ID: From: Mike Hearn To: Daniel Rice Content-Type: multipart/alternative; boundary=001a11c2dbce3674a904fbf9ecd1 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: 1WwdZk-0002ab-Sk Cc: Bitcoin Dev , Lawrence Nahum Subject: Re: [Bitcoin-development] instant confirmation via payment protocol backwards compatible proto buffer extension 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: Mon, 16 Jun 2014 20:32:23 -0000 --001a11c2dbce3674a904fbf9ecd1 Content-Type: text/plain; charset=UTF-8 On Mon, Jun 16, 2014 at 10:29 PM, Daniel Rice wrote: > I'm trying to think through how to encourage the maximum number of instant > signature providers and avoid the VISA monopoly. Ideal case would be that > people can even be their own instant provider. > A provider does not have to be an interactive third party. One reason I suggested using X.509 is so secure hardware devices like the TREZOR could also be instant providers. The hardware would be tamperproof and assert using a secret key embedded in it that the tx came from a genuine, unflashed TREZOR. The the server can know the device won't double spend. In this way you have decentralised anti-double spending. Of course, it's an old solution. MintChip sort of worked a bit like this. --001a11c2dbce3674a904fbf9ecd1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On M= on, Jun 16, 2014 at 10:29 PM, Daniel Rice <drice@greenmangosyste= ms.com> wrote:
I'm trying to thin= k through how to encourage the maximum number of instant signature provider= s and avoid the VISA monopoly. Ideal case would be that people can even be = their own instant provider.

A provider does not have to be an in= teractive third party. One reason I suggested using X.509 is so secure hard= ware devices like the TREZOR could also be instant providers. The hardware = would be tamperproof and assert using a secret key embedded in it that the = tx came from a genuine, unflashed TREZOR. The the server can know the devic= e won't double spend.

In this way you have decentralised anti-double spending= . Of course, it's an old solution. MintChip sort of worked a bit like t= his.
--001a11c2dbce3674a904fbf9ecd1--