From: Tier Nolan <tier.nolan@gmail.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Peer Discovery and Overlay
Date: Tue, 24 Dec 2013 10:47:26 +0000 [thread overview]
Message-ID: <CAE-z3OXaucepVnN_GbxVQPyeoxYsPirinfamg7fi9CJEOzuRMA@mail.gmail.com> (raw)
In-Reply-To: <op.w8k9l8qayldrnw@laptop-air.hsd1.ca.comcast.net>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
On Tue, Dec 24, 2013 at 8:52 AM, Jeremy Spilman <jeremy@taplink.co> wrote:
> Are there any past instances of applications hijacking or interfacing with
> the exiting p2p messages, or abusing 'getaddr' functionality? Are there
> any guidelines on this, or should there be?
>
>
There was a BIP by Stefan Thomas for adding custom services to the
protocol. Discovery would be helpful here too. If this was added, it
wouldn't be intended for use in a hostile way though.
This one was the custom services BIP. It defines a change to the version
message and also custom sub-commands.
https://github.com/bitcoin/bips/blob/master/bip-0036.mediawiki
This one discusses how network discovery should be handles.
https://en.bitcoin.it/wiki/User:Justmoon/BIP_Draft:_Custom_Service_Discovery
[-- Attachment #2: Type: text/html, Size: 1401 bytes --]
next prev parent reply other threads:[~2013-12-24 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 8:52 [Bitcoin-development] Peer Discovery and Overlay Jeremy Spilman
2013-12-24 10:47 ` Tier Nolan [this message]
2013-12-24 14:02 ` Peter Todd
2013-12-24 17:11 ` Warren Togami Jr.
2013-12-24 17:15 ` Mike Hearn
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=CAE-z3OXaucepVnN_GbxVQPyeoxYsPirinfamg7fi9CJEOzuRMA@mail.gmail.com \
--to=tier.nolan@gmail.com \
--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