From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WcmVN-0006rk-Ak for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 02:01:45 +0000 X-ACL-Warn: Received: from mail-pb0-f47.google.com ([209.85.160.47]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WcmVL-00026g-6I for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 02:01:45 +0000 Received: by mail-pb0-f47.google.com with SMTP id up15so239690pbc.34 for ; Tue, 22 Apr 2014 19:01:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ZV5nF80Rh1VgR4Q4qFW+FxLlR9Crcq/SysEq50iCOKU=; b=iGLPC4arj/XQLpx8GCGey4uBgcA59bG+ckmKjo/QrilhVGoZWx/TpDnxAgkeq0Ml2s WKhhDd701v6q6WLvngMJ5xK/MJQw5rzlHvGXsvQQFHB2M6g0RPFo6H0vFKr04vx8bRxM qPJv50Ho5e15ObfIiH26iycQ0YjvtElR50CTdFaRxc2woQNjBh6MXWTLqpD3zJ54ZObx Nn+d22a9o+ix3fdvGwXR9QiprjoUoJ+etPuhVBQ7xumnH4FowP+NGN3fR2DArsyXWXFN 8CC7SuYHqtjr1vD8JvQ0qe61luQl6Yt0HRmKZXlVz/+sGMxnxZ8EHPDSPzC2BBhyXq1k /N2w== X-Gm-Message-State: ALoCoQlpj0GKtP6F987+10YmhPar0nqhzhomH1qYHWoKXUIeSeu2jKKW0UxvXPtkFqvzSqV9szsU X-Received: by 10.68.174.225 with SMTP id bv1mr49642446pbc.12.1398218069339; Tue, 22 Apr 2014 18:54:29 -0700 (PDT) Received: from [192.168.1.89] (99-6-44-248.lightspeed.sntcca.sbcglobal.net. [99.6.44.248]) by mx.google.com with ESMTPSA id tf10sm87789191pbc.70.2014.04.22.18.54.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Apr 2014 18:54:28 -0700 (PDT) Message-ID: <53572B60.4050108@thinlink.com> Date: Tue, 22 Apr 2014 18:54:24 -0800 From: Tom Harding User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <52CDA01B-13BF-4BB8-AC9A-5FBBB324FD15@sant.ox.ac.uk> In-Reply-To: <52CDA01B-13BF-4BB8-AC9A-5FBBB324FD15@sant.ox.ac.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1WcmVL-00026g-6I Subject: Re: [Bitcoin-development] Economics of information propagation X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Apr 2014 02:01:45 -0000 Jonathan - These are a few things I've been wishing for recent data on: - 95th percentile transaction propagation time vs. fees/kb, vs. total fees - Count of blocks bypassing well-propagated transactions vs. fees/kb, vs. total fees - Signed-double-spend confirmation probability vs. broadcast time offset from first spend On 4/20/2014 5:30 PM, Jonathan Levin wrote: > at coinometrics we are working on a modified client to capture information on network propagation and would invite any suggestions of any other useful statistics that would be useful in the development of software.