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 <rebroad@gmail.com>) id 1XZYBb-0002dq-14
	for bitcoin-development@lists.sourceforge.net;
	Thu, 02 Oct 2014 04:40:15 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.41 as permitted sender)
	client-ip=209.85.215.41; envelope-from=rebroad@gmail.com;
	helo=mail-la0-f41.google.com; 
Received: from mail-la0-f41.google.com ([209.85.215.41])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XZYBZ-0007eE-UK
	for bitcoin-development@lists.sourceforge.net;
	Thu, 02 Oct 2014 04:40:14 +0000
Received: by mail-la0-f41.google.com with SMTP id pn19so1659268lab.14
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 01 Oct 2014 21:40:07 -0700 (PDT)
X-Received: by 10.112.209.37 with SMTP id mj5mr57667107lbc.55.1412224807109;
	Wed, 01 Oct 2014 21:40:07 -0700 (PDT)
MIME-Version: 1.0
Sender: rebroad@gmail.com
Received: by 10.112.157.42 with HTTP; Wed, 1 Oct 2014 21:39:47 -0700 (PDT)
From: "Rebroad (sourceforge)" <rebroad+sourceforge.net@gmail.com>
Date: Thu, 2 Oct 2014 12:39:47 +0800
X-Google-Sender-Auth: oeVcnSUIpX7DGumvyO94OKvFGCM
Message-ID: <CAFBxzAC6566OPT4Ex6Q6cnAAz0y8L6cg9wGcM_Tts401vCfxYQ@mail.gmail.com>
To: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11c266d8f889540504693597
X-Spam-Score: -0.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
	(rebroad[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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: 1XZYBZ-0007eE-UK
Subject: [Bitcoin-development] Decreasing block propagation time
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 02 Oct 2014 04:40:15 -0000

--001a11c266d8f889540504693597
Content-Type: text/plain; charset=UTF-8

https://bitcointalk.org/index.php?topic=145066.0

The idea proposed in the above article seemed like an excellent idea. What
is holding this up from being implemented? Does someone need to code it, or
write a BIP first?

--001a11c266d8f889540504693597
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><a href=3D"https://bitcointalk.org/index.php?topic=3D14506=
6.0">https://bitcointalk.org/index.php?topic=3D145066.0</a><div><br></div><=
div>The idea proposed in the above article seemed like an excellent idea. W=
hat is holding this up from being implemented? Does someone need to code it=
, or write a BIP first?</div></div>

--001a11c266d8f889540504693597--