From: Rick Wesson <rick@support-intelligence•com>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Roadmap/schedules
Date: Thu, 11 Aug 2011 11:20:23 -0700 [thread overview]
Message-ID: <CAJ1JLtu7UXz2X25iWLKUUmK=oapj8OzGRH964JY=Ppzd8rOfTg@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T2pTg8YG_Q09cnAvsrxquLO-6cWr1tb=fdWtLPBEyJzng@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
On Wed, Aug 10, 2011 at 9:29 AM, Gavin Andresen <gavinandresen@gmail•com>wrote:
> I've been wading through the pull requests and bug lists to figure out
> a roadmap for the next few months.
>
> Here are the things on my priority list:
>
> 1. Where are we at with network health? What metrics should we be
> using? Is there work to be done?
> And meta-issue: can somebody volunteer to be the Bitcoin Network
> Health Inspector to keep track of this?
>
>
I'm already on it, leveraging bitcoinj to do the work. I've added async
capabilities to bitcoinj so that I can peer with everything that will let me
with the goal of publishing quality peer lists via the DNS. Once I can build
some metrics off the network its a matter of creating the visualizations.
I just started on this project last week. Happy to work with others on what
a healty network looks like as well as best ways to communicate status.
also need advise on how to not be an impolite peer.
-rick
[-- Attachment #2: Type: text/html, Size: 1357 bytes --]
prev parent reply other threads:[~2011-08-11 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 16:29 Gavin Andresen
2011-08-10 16:59 ` Matt Corallo
2011-08-10 18:57 ` Pieter Wuille
2011-08-11 11:56 ` Mike Hearn
2011-08-11 17:49 ` bgroff
2011-08-10 20:41 ` Jeff Garzik
2011-08-11 8:48 ` Matt Corallo
2011-08-11 18:20 ` Rick Wesson [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='CAJ1JLtu7UXz2X25iWLKUUmK=oapj8OzGRH964JY=Ppzd8rOfTg@mail.gmail.com' \
--to=rick@support-intelligence$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@gmail$(echo .)com \
/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