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 141CC895 for ; Thu, 13 Aug 2015 16:34:25 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-la0-f50.google.com (mail-la0-f50.google.com [209.85.215.50]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6BD5515F for ; Thu, 13 Aug 2015 16:34:24 +0000 (UTC) Received: by lagz9 with SMTP id z9so29202535lag.3 for ; Thu, 13 Aug 2015 09:34:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=73DzmDqF45Z1Nxz0A8yOk0Ltr5Mnwh73I9eNRJRV5aY=; b=YBfQSYiONigufrgrCMWE6MW2yXcL4OJPfsEcjQ/lV3j1rYC0DjerwmTWZDGVYYQZF4 5wIR1uhpChb6+ApYgY3ItTxngdXcopHrSryd+BstiRpL3aH6y67yywXYmoExNWwCqjBP UQfZtdafrsDkwPhelYn9rDd2ZKU8qac5sb1VB/65w7wo5Z86BiLK2NinFkTp0+jknk69 3zP4kICvEhmd8OXG7EGe/uh5lW1hF0wdE6zznSCvHpa4xjuxzr+F9kGU/1APm69moqOt xmf9ecin98Yz2Zs/6kHNjTfS/21Fovf5+cqRNIq8CEDHt+FnjC+2eatrlrfEoRrZyUaC pw5A== X-Received: by 10.112.63.169 with SMTP id h9mr37131565lbs.104.1439483662626; Thu, 13 Aug 2015 09:34:22 -0700 (PDT) MIME-Version: 1.0 Sender: slashene@gmail.com Received: by 10.25.142.15 with HTTP; Thu, 13 Aug 2015 09:34:03 -0700 (PDT) From: Nicolas Dorier Date: Fri, 14 Aug 2015 01:34:03 +0900 X-Google-Sender-Auth: ltCAEOnTM96uxFS8hN-8RAZQbdE Message-ID: To: bitcoin-dev@lists.linuxfoundation.org Content-Type: multipart/alternative; boundary=001a11c3fd125ef647051d33e8c2 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,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 Subject: Re: [bitcoin-dev] [BIP-draft] CHECKSEQUENCEVERIFY - An opcode for relative locktime (Btc Drak) 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: Thu, 13 Aug 2015 16:34:25 -0000 --001a11c3fd125ef647051d33e8c2 Content-Type: text/plain; charset=UTF-8 Would be wonderful to have this pushed together with CLTV and BIP68. If BIP68 get pushed in the next fork, this CSV is a no brainer. Was there a competing RCLTV implementation somewhere that did not depend on BIP68 for information ? I don't manage to find it. --001a11c3fd125ef647051d33e8c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Would be wonderful to have this pushed together with CLTV = and BIP68.
If BIP68 get pushed in the next fork, this CSV is a no b= rainer.

Was there a competing RCLTV implementa= tion somewhere that did not depend on BIP68 for information ? I don't m= anage to find it.
--001a11c3fd125ef647051d33e8c2--