From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XF52l-0007Er-Ls for bitcoin-development@lists.sourceforge.net; Wed, 06 Aug 2014 17:30:31 +0000 Received: from mail-pa0-f52.google.com ([209.85.220.52]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XF52h-0001Tg-L9 for bitcoin-development@lists.sourceforge.net; Wed, 06 Aug 2014 17:30:31 +0000 Received: by mail-pa0-f52.google.com with SMTP id bj1so3770062pad.25 for ; Wed, 06 Aug 2014 10:30:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=80u74orp9215pUZnqhZ1Si6joDBHcADez+9xXwVp/x4=; b=hul/NugkHPtzhZtuzx6XoDkW4LAugQtPfJMgEBKXgVfsHa3baEsXqKh5wj4wd/SRaJ tE9nypK4btR16o2YJaq4p4mPAnq3EMnG3hELZjTRUy5A7KfTiuaojaLDz4v7Jh8bJUuf kJqcSNqA+KRPX3d5PQdgoQXyuG8eCZHnDmsaNDpDtZjf3DM9Laq7VNgv0bopO3dJvQ4X UoXeohameWA5ayj7Pjul5f0K+y3QazaOfHxipcBj8K2KhGkZANGjrUR4ZWqDD3PEkf2K OXgzVu+AbV3A+umkervUHgHI7TIO5rtZsYlC5kVADMf75Cy1JSFCz0zHhVnvEh1qqdOx i5OA== X-Gm-Message-State: ALoCoQmXfkk1JkGJwXHuKWL34Ha7aQYlO7Xxfe40DQvkY/52eFZURn0ndp1pdmybMTS/JRiTEh2y X-Received: by 10.66.167.105 with SMTP id zn9mr11736835pab.103.1407346221818; Wed, 06 Aug 2014 10:30:21 -0700 (PDT) Received: from [192.168.127.194] (173-228-106-61.dsl.dynamic.sonic.net. [173.228.106.61]) by mx.google.com with ESMTPSA id p9sm2646297pdl.21.2014.08.06.10.30.17 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Aug 2014 10:30:21 -0700 (PDT) Message-ID: <53E26623.3070107@monetize.io> Date: Wed, 06 Aug 2014 13:30:11 -0400 From: Mark Friedenbach Organization: Monetize.io Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Peter Todd , Bitcoin Dev References: <53E1A8AF.4030206@thinlink.com> <53E23F49.3020605@thinlink.com> <63a80796-609e-43f5-9280-4cd8cf5d2648@email.android.com> <53E2585C.8070009@monetize.io> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1XF52h-0001Tg-L9 Subject: Re: [Bitcoin-development] deterministic transaction expiration 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, 06 Aug 2014 17:30:31 -0000 On 08/06/2014 01:20 PM, Peter Todd wrote: > The general case doesn't require transmission of any merkle data; it > is derived from the tx data. How can that possibly be the case? The information is hidden behind the Merkle root in the transaction. The validator needs to know whether there is an expiry and what it is. What's it supposed to do, guess?