From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org,
Billy Tetrud <billy.tetrud@gmail•com>
Cc: Christopher Gilliard <christopher.gilliard@gmail•com>
Subject: Re: [bitcoin-dev] Additional BIPs related to other proposals
Date: Sat, 22 May 2021 02:33:45 +0000 [thread overview]
Message-ID: <202105220233.45883.luke@dashjr.org> (raw)
In-Reply-To: <CAGpPWDY6tuH6pWWj308riYyNfszS2n=KoPUCpxpDz4bRLyACTA@mail.gmail.com>
On Friday 21 May 2021 07:56:51 Billy Tetrud via bitcoin-dev wrote:
> These look like relatively well put together documents. However, they seem
> relatively orthogonal to Bitcoin in that they look like protocols that
> build on top of the bitcoin platform but aren't directly related to
> changing how bitcoin operates at its base layer. Am I miss reading these?
BIPs are not limited to the base layer. Anything that coordinates between
Bitcoin software at any layer can use BIPs.
next prev parent reply other threads:[~2021-05-22 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 2:05 Christopher Gilliard
2021-05-21 7:56 ` Billy Tetrud
2021-05-22 2:33 ` Luke Dashjr [this message]
2021-05-22 6:01 ` Billy Tetrud
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=202105220233.45883.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=billy.tetrud@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=christopher.gilliard@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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