From: Peter Todd <pete@petertodd•org>
To: Peter Tschipper <peter.tschipper@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] request to use service bit 28 for testing
Date: Mon, 16 Nov 2015 18:24:05 -0500 [thread overview]
Message-ID: <20151116232405.GA6302@savin.petertodd.org> (raw)
In-Reply-To: <5647C375.9050809@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
On Sat, Nov 14, 2015 at 03:27:49PM -0800, Peter Tschipper via bitcoin-dev wrote:
> I'd like to use service bit 28 for testing the block compression
> prototype unless anyone has any objections or is using it already.
Go for it!
AFAIK the only testing service bit in use right now is bit 26, used to
indicate full-RBF support by my replace-by-fee branch:
https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.11.2
Speaking of, you may find the preferential peering code in the above to
be useful. It's a bit of a hack, but it does work.
--
'peter'[:-1]@petertodd.org
000000000000000009c6356b4a0f309636e2b87e263063bee18ac22e91a57deb
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
prev parent reply other threads:[~2015-11-16 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 23:27 Peter Tschipper
2015-11-16 23:24 ` Peter Todd [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=20151116232405.GA6302@savin.petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=peter.tschipper@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