From: "Eric Lombrozo" <elombrozo@gmail.com>
To: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Hierarchical Deterministic Script Templates
Date: Sat, 21 Nov 2015 03:29:46 +0000 [thread overview]
Message-ID: <em27bdafa1-7188-4c5b-bfbd-2154fc3c7e54@platinum> (raw)
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
A while back, I started working with William Swanson on a script
template format to allow for interoperability in accounts between
different wallets. We made some progress, but both of us got pretty busy
with other projects and general interest was still quite low.
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.
I have started working on a draft for such a standard:
https://github.com/bitcoin/bips/pull/246
Comments, suggestions, and collaboration are welcome.
- Eric
[-- Attachment #2: Type: text/html, Size: 1758 bytes --]
reply other threads:[~2015-11-21 3:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=em27bdafa1-7188-4c5b-bfbd-2154fc3c7e54@platinum \
--to=elombrozo@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox