From: Jeremy <jlrubin@mit.edu>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Cc: Bitcoin development mailing list
<bitcoin-dev@lists.linuxfoundation.org>,
lightning-dev <lightning-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Lightning-dev] Inherited IDs - A safer, more powerful alternative to BIP-118 (ANYPREVOUT) for scaling Bitcoin
Date: Fri, 24 Sep 2021 00:27:03 -0700 [thread overview]
Message-ID: <CAD5xwhhZd2Mr17bsPk0gszitROWF13i2hTg_7KvRnR948_zQpw@mail.gmail.com> (raw)
In-Reply-To: <wDdSrhoOhFv2L7-IsDteE5PoDaZJk3aFZSvNgYd_PbuoVwLQ3qwheW-00wV52utUrpDhzsbAKvzYRhm5WUkXBtC-y0YPe9t17TaWodK1WsY=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 179 bytes --]
John let me know that he's posted some responses in his Github repo
https://github.com/JohnLaw2/btc-iids
probably easiest to respond to him via e.g. a github issue or something.
[-- Attachment #2: Type: text/html, Size: 597 bytes --]
prev parent reply other threads:[~2021-09-24 7:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 16:58 [bitcoin-dev] Inherited IDs - A safer, more powerful alternative to BIP-118 (ANYPREVOUT) for scaling Bitcoin Jeremy
2021-09-18 11:37 ` Anthony Towns
2021-09-21 2:11 ` [bitcoin-dev] [Lightning-dev] " ZmnSCPxj
2021-09-24 7:27 ` Jeremy [this message]
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=CAD5xwhhZd2Mr17bsPk0gszitROWF13i2hTg_7KvRnR948_zQpw@mail.gmail.com \
--to=jlrubin@mit.edu \
--cc=ZmnSCPxj@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=lightning-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