public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Adding a pong message to the protocol
Date: Mon, 5 Sep 2011 09:30:24 -0400	[thread overview]
Message-ID: <CAAS2fgQdRP5bd02tR_L6_hWh+qEwXWOVH8KRcpuFiRvKwD5o1w@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3Fh=Ffeh5PtcaL4QBKXUzkFYAar4031-wVZOVQOhngrw@mail.gmail.com>

On Mon, Sep 5, 2011 at 8:04 AM, Mike Hearn <mike@plan99•net> wrote:
> I haven't written a patch for this, I might do so if there's
> sufficient interest.
[snip]
> Thoughts?

I'd rather see effort spent on the root issues, e.g. having nodes
gauge their own suitability (working inbound port, reasonably current
block chain, etc) before becoming advertised listeners.

Or more importantly— figuring some way of setting up network
simulations which could be used to actually _validate_ proposed
changes in this area.

I, or many other people, could spout endlessly about attractive
sounding network enhancements (e.g. move-to-front peer prioritization,
tweaks to peer selection, etc.) but it's all just arm waving without a
way to measure it, and the real network is far too slow to upgrade
(and important) to test things in situ while testnet is far too small
and unlike the real network for useful testing.



  reply	other threads:[~2011-09-05 13:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-05 12:04 Mike Hearn
2011-09-05 13:30 ` Gregory Maxwell [this message]
2011-09-05 14:32   ` 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=CAAS2fgQdRP5bd02tR_L6_hWh+qEwXWOVH8KRcpuFiRvKwD5o1w@mail.gmail.com \
    --to=gmaxwell@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=mike@plan99$(echo .)net \
    /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