From: Gregory Maxwell <greg@xiph•org>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Fwd: Services bit for xthin blocks
Date: Tue, 8 Mar 2016 06:09:53 +0000 [thread overview]
Message-ID: <CAAS2fgQxWi=vTov3NiNsEzvAU1eDDdH1p2M=7wf5Qw6g1Az_3w@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgSf_qYaT7ahQTbmRoQpG57qgF26NKVuGGaEzpMZmCOFoA@mail.gmail.com>
On Tue, Mar 8, 2016 at 5:14 AM, Dave Scotese <dscotese@litmocracy•com> wrote:
> I think a BIP is a good idea, but rather than making such a specific
> proposal as "Let's use bit 4 to indicate communication of thin blocks," how
> about a more general one like "Let's use bit(s?) 4(-5?) as user-agent
Not communicated in address messages, so useless for discovery.
I think any feature which could do this could use the BIP130 approach instead.
next prev parent reply other threads:[~2016-03-08 6:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 20:06 [bitcoin-dev] " G. Andrew Stone
2016-03-07 20:51 ` Gregory Maxwell
2016-03-07 21:10 ` dagurval
2016-03-08 2:35 ` G. Andrew Stone
2016-03-08 17:19 ` Luke Dashjr
2016-03-09 18:11 ` G. Andrew Stone
2016-03-09 21:11 ` Tier Nolan
2016-03-08 5:14 ` Dave Scotese
[not found] ` <CAAS2fgSf_qYaT7ahQTbmRoQpG57qgF26NKVuGGaEzpMZmCOFoA@mail.gmail.com>
2016-03-08 6:09 ` Gregory Maxwell [this message]
2016-03-07 21:09 ` Tier Nolan
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='CAAS2fgQxWi=vTov3NiNsEzvAU1eDDdH1p2M=7wf5Qw6g1Az_3w@mail.gmail.com' \
--to=greg@xiph$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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