From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id E8E9EEDA for ; Mon, 5 Oct 2015 15:42:58 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 43357170 for ; Mon, 5 Oct 2015 15:42:58 +0000 (UTC) Received: by wicge5 with SMTP id ge5so126677672wic.0 for ; Mon, 05 Oct 2015 08:42:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=d9zqtoKI5ob3cd0qW0sjDDSD19NHvl8Lj5F2odbAjIk=; b=H9R3nwAyxrCMx29V7DVYE+rY5YukrwnqwyY1ogKNc4KhL9oZXzVXGVRPrQ9vV+nLay Fxxn0ICuvoIq9bIc6nFEXJ5v5mpPAuzIR9CwWYL8M1afT3TfFXv9N76c57RBhnybNpqK /59Bz+1jaVGltlpQApWIINbWDHQJpwYFP7JcvLXY843XPrRP86NYcb6sDZELcVPEyLE6 fvA9uJ73ayFBI8ZC4l1ZiKKBllt7WtqqDbh9o9sngftHpaYnqJTglCG9pDKNUo/IqqL4 TI2ngF7ROat0BKIsMxLL9ku94Y9tW24S41Ffv01kJaj/qQVSwRcaU17Tz9qY0ulP9D8d iNsA== X-Gm-Message-State: ALoCoQlfiILZmWtNRhUb9DT3Z1KY908kM14IpV1D14q0Uhnb19sApR6J1H/jOUwyw8t3Ir9Sg0AW MIME-Version: 1.0 X-Received: by 10.194.246.161 with SMTP id xx1mr30808149wjc.26.1444059777081; Mon, 05 Oct 2015 08:42:57 -0700 (PDT) Received: by 10.194.114.199 with HTTP; Mon, 5 Oct 2015 08:42:56 -0700 (PDT) In-Reply-To: References: Date: Mon, 5 Oct 2015 17:42:56 +0200 Message-ID: From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= To: =?UTF-8?Q?Cl=C3=A9ment_Elbaz?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] Let's deploy BIP65 CHECKLOCKTIMEVERIFY! X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Oct 2015 15:42:59 -0000 On Mon, Oct 5, 2015 at 2:29 PM, Cl=C3=A9ment Elbaz wrot= e: > The problem is that some transactions that are meaningless to you are > actually meaningful to people using an upgraded Bitcoin software. > > Therefore during a softfork, while you can not miss the existence of a > transaction, you can miss its meaning. Why would you care about payments to other people? The scriptPubKey's that you give to your payers certainly have meaning to y= ou. > But as soon as you try to actually use Bitcoin (that is, calculate the > accurate balance of a wallet in a very broad sense), you can be led a wro= ng > result if you did not upgrade, which is a critical problem for financial > software. What is it important that you are able to calculate balances of wallets that aren't yours? > And because nothing prevent people to send you transactions of a new type= , > you have no way to "opt out" of this problem. Why would anyone "pay you" to a scriptPubKey you don't understand? I can "pay" the bill of my internet services by burying cash in a park nearby my house for my provider to pick up later. But if I don't tell my provider, it will never know. If I inform it, I will get an answer: "no, sorry, we won't accept this new 'form of payment' of yours as payment".