From mboxrd@z Thu Jan 1 00:00:00 1970 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 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 ; 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)" Date: Thu, 2 Oct 2014 12:39:47 +0800 X-Google-Sender-Auth: oeVcnSUIpX7DGumvyO94OKvFGCM Message-ID: To: "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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
https://bitcointalk.org/index.php?topic=3D145066.0

<= 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?
--001a11c266d8f889540504693597-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XZYI2-0003PZ-UN for bitcoin-development@lists.sourceforge.net; Thu, 02 Oct 2014 04:46:54 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bluematt.me designates 192.241.179.72 as permitted sender) client-ip=192.241.179.72; envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me; Received: from mail.bluematt.me ([192.241.179.72]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1XZYI1-0008LB-2I for bitcoin-development@lists.sourceforge.net; Thu, 02 Oct 2014 04:46:54 +0000 Received: from [172.17.0.2] (gw.vpn.bluematt.me [162.243.132.6]) by mail.bluematt.me (Postfix) with ESMTPSA id 3D18B4A4CF for ; Thu, 2 Oct 2014 04:46:46 +0000 (UTC) Message-ID: <542CD8B3.5060001@bluematt.me> Date: Thu, 02 Oct 2014 04:46:43 +0000 From: Matt Corallo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Score: -2.5 (--) 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 SPF_PASS SPF: sender matches SPF record -1.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1XZYI1-0008LB-2I Subject: Re: [Bitcoin-development] Decreasing block propagation time 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: Thu, 02 Oct 2014 04:46:55 -0000 It already is https://bitcointalk.org/index.php?topic=766190.0;all. Well, ok, a variation on the idea is. Matt On 10/02/14 04:39, Rebroad (sourceforge) wrote: > 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? > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >