Return-Path: <elombrozo@gmail.com> Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 1183E7D for <bitcoin-dev@lists.linuxfoundation.org>; Sat, 21 Nov 2015 03:30:03 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 951C5D5 for <bitcoin-dev@lists.linuxfoundation.org>; Sat, 21 Nov 2015 03:30:02 +0000 (UTC) Received: by pacdm15 with SMTP id dm15so134593175pac.3 for <bitcoin-dev@lists.linuxfoundation.org>; Fri, 20 Nov 2015 19:30:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:reply-to:user-agent:mime-version :content-type; bh=IBsrx7I18VezPuXV/95iWlHYW2cgZuWmdXOETkVwgjk=; b=Dp5mCdxoD7J6xdslBrd23vvFp2qry0V+s1Bc6sY1bCLlBoWLf3tomVw4AkosxlozZB vBXZclToF+lE/3DM3iD8JX+aS9EWOIoUXLDsqs0KB3YBUkrkz202QowUhrjUV50yXdRy oNQslN2dtz+VIXzmdm2EEGiPYLpkCDfTPH87Jfrm1QQ9OAqdYEc+fA3t+aS9ZS9nTkmk MXHbuwq6WRBns05iE2sJjvWLrO1uY5RyNDh6Y/BAt44pK/W5g7mGC27vz5tW1eIgqb/Z /bEbIktFtW5CR8OJkzxrQli8oHDL0vipxXJ16063p9ZJL1LD+5At2nUgGLXaGnQxVhuP tqOA== X-Received: by 10.98.80.22 with SMTP id e22mr3187074pfb.34.1448076602336; Fri, 20 Nov 2015 19:30:02 -0800 (PST) Received: from [192.168.1.108] (cpe-76-167-237-202.san.res.rr.com. [76.167.237.202]) by smtp.gmail.com with ESMTPSA id rc5sm1437028pbc.95.2015.11.20.19.30.01 for <bitcoin-dev@lists.linuxfoundation.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 20 Nov 2015 19:30:01 -0800 (PST) From: "Eric Lombrozo" <elombrozo@gmail.com> To: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> Date: Sat, 21 Nov 2015 03:29:46 +0000 Message-Id: <em27bdafa1-7188-4c5b-bfbd-2154fc3c7e54@platinum> Reply-To: "Eric Lombrozo" <elombrozo@gmail.com> User-Agent: eM_Client/6.0.23181.0 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------=_MB3F846721-3C33-4F7A-9E63-E5232FA6E661" 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 X-Mailman-Approved-At: Sat, 21 Nov 2015 04:18:59 +0000 Subject: [bitcoin-dev] Hierarchical Deterministic Script Templates X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org> List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> X-List-Received-Date: Sat, 21 Nov 2015 03:30:03 -0000 --------=_MB3F846721-3C33-4F7A-9E63-E5232FA6E661 Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable A while back, I started working with William Swanson on a script=20 template format to allow for interoperability in accounts between=20 different wallets. We made some progress, but both of us got pretty busy= =20 with other projects and general interest was still quite low. It seems interest has picked up again, especially in light of recent=20 developments (i.e. CLTV, relative CLTV, bidirectional payment channels,=20 lightning), where nongeneralized script formats will not readily support= =20 the rapidly advancing state-of-the-art in script design. I have started working on a draft for such a standard:=20 https://github.com/bitcoin/bips/pull/246 Comments, suggestions, and collaboration are welcome. - Eric --------=_MB3F846721-3C33-4F7A-9E63-E5232FA6E661 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <HTML><HEAD> <STYLE id=3DeMClientCss>BLOCKQUOTE.cite { PADDING-LEFT: 10px; MARGIN-LEFT: 5px; BORDER-LEFT: #cccccc 1px solid; PADD= ING-RIGHT: 0px; MARGIN-RIGHT: 0px } BLOCKQUOTE.cite2 { PADDING-TOP: 0px; PADDING-LEFT: 10px; MARGIN-LEFT: 5px; BORDER-LEFT: #cccc= cc 1px solid; MARGIN-TOP: 3px; PADDING-RIGHT: 0px; MARGIN-RIGHT: 0px } .plain PRE { FONT-SIZE: 100%; FONT-FAMILY: monospace; WHITE-SPACE: pre-wrap; FONT-WEIGH= T: normal; FONT-STYLE: normal } .plain TT { FONT-SIZE: 100%; FONT-FAMILY: monospace; WHITE-SPACE: pre-wrap; FONT-WEIGH= T: normal; FONT-STYLE: normal } A IMG { BORDER-TOP: 0px; BORDER-RIGHT: 0px; BORDER-BOTTOM: 0px; BORDER-LEFT: 0px } BODY { FONT-SIZE: 12pt; FONT-FAMILY: Tahoma } .plain PRE { FONT-SIZE: 12pt; FONT-FAMILY: Tahoma } .plain TT { FONT-SIZE: 12pt; FONT-FAMILY: Tahoma } </STYLE> </HEAD> <BODY> <DIV>A while back, I started working with William Swanson on a script templ= ate format to allow for interoperability in accounts between different wall= ets. We made some progress, but both of us got pretty busy with other proje= cts and general interest was still quite low.</DIV> <DIV> </DIV> <DIV>It seems interest has picked up again, especially in light of recent= developments (i.e. CLTV, relative CLTV, bidirectional payment channels,= lightning), where nongeneralized script formats will not readily support= the rapidly advancing state-of-the-art in script design.</DIV> <DIV> </DIV> <DIV>I have started working on a draft for such a standard: <A href=3D"http= s://github.com/bitcoin/bips/pull/246">https://github.com/bitcoin/bips/pull/= 246</A></DIV> <DIV> </DIV> <DIV>Comments, suggestions, and collaboration are welcome.</DIV> <DIV> </DIV> <DIV>- Eric</DIV></BODY></HTML> --------=_MB3F846721-3C33-4F7A-9E63-E5232FA6E661--