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 1RKCHL-0003xT-ED for bitcoin-development@lists.sourceforge.net; Sat, 29 Oct 2011 17:01:07 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.161.47 as permitted sender) client-ip=209.85.161.47; envelope-from=gavinandresen@gmail.com; helo=mail-fx0-f47.google.com; Received: from mail-fx0-f47.google.com ([209.85.161.47]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1RKCHK-00050q-L6 for bitcoin-development@lists.sourceforge.net; Sat, 29 Oct 2011 17:01:07 +0000 Received: by faas16 with SMTP id s16so7118607faa.34 for ; Sat, 29 Oct 2011 10:01:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.92.135 with SMTP id r7mr15477033fam.35.1319907660381; Sat, 29 Oct 2011 10:01:00 -0700 (PDT) Received: by 10.152.2.231 with HTTP; Sat, 29 Oct 2011 10:01:00 -0700 (PDT) In-Reply-To: <564C59F8-8077-4603-8EAC-389C30509F02@ceptacle.com> References: <7A50EE90-0FFC-45FB-A27F-786AEB23A8CA@ceptacle.com> <1089B122-1274-454C-9097-700D392BF0FA@ceptacle.com> <564C59F8-8077-4603-8EAC-389C30509F02@ceptacle.com> Date: Sat, 29 Oct 2011 13:01:00 -0400 Message-ID: From: Gavin Andresen To: =?ISO-8859-1?Q?Michael_Gr=F8nager?= Content-Type: text/plain; charset=ISO-8859-1 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -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 0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RKCHK-00050q-L6 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Detecting OP_EVAL scriptPubKeys that are to you 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: Sat, 29 Oct 2011 17:01:07 -0000 RE: buying me and Gregory a shared beer: > I would make a "both of two" btc-addresses script transaction using OP_EVAL. And post it. > You would then not be able to know that you actually got a beer unless I told you so in a mail. But that transaction won't show up in my bitcoin wallet as bitcoins I can spend. And even if my wallet DID show me "transactions that involve your keys but that you can't spend," all I would know is there are N bitcoins that I can only spend if I can somehow figure out that Gregory has public key XYZ. How would I know that unless you told me? I think the right long-term solution is moving away from bitcoin addresses as 'pay-to entity' and create an infrastructure where we're paying people or organizations. But in the short term, I think there are lots of benefits to creating a new type of bitcoin address built on top of OP_EVAL that will be very easy for all of our existing infrastructure to support. -- -- Gavin Andresen