From: Billy Tetrud <billy.tetrud@gmail•com>
To: Christopher Gilliard <christopher.gilliard@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Additional BIPs related to other proposals
Date: Thu, 20 May 2021 21:56:51 -1000 [thread overview]
Message-ID: <CAGpPWDY6tuH6pWWj308riYyNfszS2n=KoPUCpxpDz4bRLyACTA@mail.gmail.com> (raw)
In-Reply-To: <CAK=nyAxZ3ohoO4NSmHSiUh7+MHDCQcSvPBkOL2=G=VLNyzu07A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
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?
On Sat, Apr 24, 2021 at 12:08 AM Christopher Gilliard via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> I have created three additional BIPs that are associated with my recent
> proposals. They can be found here:
>
> https://github.com/cgilliard/bips/blob/notification/bip-XXXX.mediawiki
>
> and here:
>
> https://github.com/cgilliard/bips/blob/moderation/bip-XXXX.mediawiki
>
> and here:
>
> https://github.com/cgilliard/bips/blob/wot/bip-XXXX.mediawiki
>
> Please reply with any feedback, questions, or comments.
>
> Regards,
> Chris
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 1998 bytes --]
next prev parent reply other threads:[~2021-05-21 7:57 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 [this message]
2021-05-22 2:33 ` Luke Dashjr
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='CAGpPWDY6tuH6pWWj308riYyNfszS2n=KoPUCpxpDz4bRLyACTA@mail.gmail.com' \
--to=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