public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Addy Yeow <ayeowch@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Requirement for relay field in version packet (protocol version >= 70001)
Date: Mon, 6 May 2013 10:20:01 +0200	[thread overview]
Message-ID: <CANEZrP0BBGEBH5Fhgjr6GC3HNAriEKAGttttWKk834RPsVj24A@mail.gmail.com> (raw)
In-Reply-To: <CAA3bHnxg3BuaVXMqZ2G7G0CiKFAgQFArd2HPW08JFMbEdTFFZw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

It's expected to be there, yes.


On Mon, May 6, 2013 at 9:56 AM, Addy Yeow <ayeowch@gmail.com> wrote:

> >From https://en.bitcoin.it/wiki/Protocol_specification#version, is the
> relay field (bool/1 byte) required in all version packets coming from
> client with protocol version >= 70001?
>
>
> ------------------------------------------------------------------------------
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

[-- Attachment #2: Type: text/html, Size: 1551 bytes --]

      reply	other threads:[~2013-05-06  8:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06  7:56 [Bitcoin-development] Requirement for relay field in version packet (protocol version >= 70001) Addy Yeow
2013-05-06  8:20 ` Mike Hearn [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=CANEZrP0BBGEBH5Fhgjr6GC3HNAriEKAGttttWKk834RPsVj24A@mail.gmail.com \
    --to=mike@plan99.net \
    --cc=ayeowch@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