From: Stefan Thomas <moon@justmoon.de>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] BIP: Custom Services
Date: Mon, 13 Aug 2012 09:41:50 +0200 [thread overview]
Message-ID: <5028AFBE.8070104@justmoon.de> (raw)
Hey everyone,
I was working on some custom protocol extensions for Bitcoin that I
wanted to experiment with and I noticed that in order to enable nodes to
announce these services the only mechanism the protocol currently
provides is to use one of the 64 bits of the services field. This is
obviously a resource that will run out quickly if we all just help
ourselves, so I set out to come up with a standardized way to announce
custom protocol extensions, without using up NODE_* flags.
Please kindly review my solution:
https://en.bitcoin.it/wiki/User:Justmoon/BIP_Draft:_Custom_Services
Thanks to Amir Taaki, Mike Hearn and Pieter Wuille who provided
invaluable feedback while writing the draft.
Note: Earlier drafts of this BIP contained a description of a mechanism
for peer exchange for these custom services. However, since that part of
the BIP was (1) just a recommendation and (2) rather complex, Amir and I
agreed to split it off into a separate BIP [1] that will be refined some
more and submitted later.
Cheers,
Stefan
[1]
https://en.bitcoin.it/wiki/User:Justmoon/BIP_Draft:_Custom_Service_Discovery
next reply other threads:[~2012-08-13 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 7:41 Stefan Thomas [this message]
2012-08-13 13:15 ` [Bitcoin-development] BIP: Custom Services Mike Hearn
2012-08-13 20:00 ` Stefan Thomas
2012-08-13 14:24 ` Jeff Garzik
2012-08-13 15:07 ` Gregory Maxwell
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=5028AFBE.8070104@justmoon.de \
--to=moon@justmoon.de \
--cc=bitcoin-development@lists.sourceforge.net \
/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