Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VkcQn-0007r2-8g for bitcoin-development@lists.sourceforge.net; Sun, 24 Nov 2013 16:21:09 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.170 as permitted sender) client-ip=209.85.214.170; envelope-from=decker.christian@gmail.com; helo=mail-ob0-f170.google.com; Received: from mail-ob0-f170.google.com ([209.85.214.170]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VkcQm-0005aY-DQ for bitcoin-development@lists.sourceforge.net; Sun, 24 Nov 2013 16:21:09 +0000 Received: by mail-ob0-f170.google.com with SMTP id wp18so3289155obc.1 for ; Sun, 24 Nov 2013 08:21:03 -0800 (PST) X-Received: by 10.60.58.166 with SMTP id s6mr2210134oeq.40.1385310063001; Sun, 24 Nov 2013 08:21:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.130.198 with HTTP; Sun, 24 Nov 2013 08:20:22 -0800 (PST) From: Christian Decker Date: Sun, 24 Nov 2013 17:20:22 +0100 Message-ID: To: Bitcoin Development Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (decker.christian[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: bitcoinstats.com] -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1VkcQm-0005aY-DQ Subject: [Bitcoin-development] Network propagation speeds 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: Sun, 24 Nov 2013 16:21:09 -0000 Since this came up again during the discussion of the Cornell paper I thought I'd dig up my measurement code from the Information Propagation paper and automate it as much as possible. The result is the Network Propagation page on bitcoinstats.com (http://bitcoinstats.com/network/propagation/). It takes a daily snapshot of the situation, then calculates the time until blocks and transactions reach a certain percentile of the nodes in the network. There is also a detailed page showing the density function describing at what times nodes learn about the existence of a block/transaction (for example yesterdays distribution: http://bitcoinstats.com/network/propagation/2013/11/23). I intend to add more information and plots over time, but I wanted to push this out quickly as there were some people asking for it. Hope this helps getting the blockchain fork rate down :-) Regards, Chris -- Christian Decker