From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org,
Christopher Jeffrey <chjj@purse.io>
Subject: Re: [bitcoin-dev] Extension block proposal by Jeffrey et al
Date: Thu, 6 Apr 2017 17:18:35 +0000 [thread overview]
Message-ID: <201704061718.35638.luke@dashjr.org> (raw)
In-Reply-To: <20170405165405.GA28519@gmail.com>
On Wednesday, April 05, 2017 4:54:05 PM Christopher Jeffrey via bitcoin-dev
wrote:
> There's understandable confusion about this, but this proposal is not
> meant to be a BIP.
Oh? If this was not meant to be a Bitcoin Improvement Proposal, perhaps you
should clarify somewhere what altcoin you are proposing it for. As it stands,
it certainly did read much like it was meant to be a BIP, and apparently many
others thought so as well.
Admittedly, the bitcoin-dev ML isn't the place for altcoin discussions, and
I'm not particularly interested in spending my time aiding altcoins, so I'll
just end the conversation here until someone re-proposes something similar for
Bitcoin.
Sorry for confusing the nature of your work,
Luke
prev parent reply other threads:[~2017-04-06 17:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 18:03 [bitcoin-dev] Extension block proposal by Jeffrey et al Luke Dashjr
2017-04-04 18:35 ` Johnson Lau
2017-04-05 14:05 ` Olaoluwa Osuntokun
2017-04-05 15:37 ` Greg Sanders
2017-04-05 16:25 ` Joseph Poon
2017-04-05 17:04 ` Johnson Lau
2017-04-05 17:43 ` Christopher Jeffrey
2017-04-10 10:14 ` Johnson Lau
2017-05-09 0:56 ` Christopher Jeffrey
2017-05-09 17:56 ` Johnson Lau
2017-05-10 1:19 ` Christopher Jeffrey
2017-04-05 16:54 ` Christopher Jeffrey
2017-04-06 17:18 ` Luke Dashjr [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=201704061718.35638.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=chjj@purse.io \
/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