<div dir="ltr"><div><div><div class="gmail_extra"><div class="gmail_quote">On Tue, Dec 24, 2013 at 8:52 AM, Jeremy Spilman <span dir="ltr">&lt;<a href="mailto:jeremy@taplink.co" target="_blank">jeremy@taplink.co</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Are there any past instances of applications hijacking or interfacing with<br>
the exiting p2p messages, or abusing &#39;getaddr&#39; functionality? Are there<br>
any guidelines on this, or should there be?<br>
<br></blockquote><div><br><div>There was a BIP by <span name="Stefan Thomas" class="">Stefan Thomas </span>for adding custom services to the protocol.  Discovery would be helpful here too.  If this was added, it wouldn&#39;t be intended for use in a hostile way though.<br>
<br></div>This one was the custom services BIP.  It defines a change to the version message and also custom sub-commands.<br><a href="https://github.com/bitcoin/bips/blob/master/bip-0036.mediawiki">https://github.com/bitcoin/bips/blob/master/bip-0036.mediawiki</a><br>
<br>This one discusses how network discovery should be handles.<br><a href="https://en.bitcoin.it/wiki/User:Justmoon/BIP_Draft:_Custom_Service_Discovery">https://en.bitcoin.it/wiki/User:Justmoon/BIP_Draft:_Custom_Service_Discovery</a><br>
</div></div></div></div></div></div>