From: "Rebroad (sourceforge)" <rebroad+sourceforge.net@gmail.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Decreasing block propagation time
Date: Thu, 2 Oct 2014 12:39:47 +0800 [thread overview]
Message-ID: <CAFBxzAC6566OPT4Ex6Q6cnAAz0y8L6cg9wGcM_Tts401vCfxYQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 220 bytes --]
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?
[-- Attachment #2: Type: text/html, Size: 329 bytes --]
next reply other threads:[~2014-10-02 4:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 4:39 Rebroad (sourceforge) [this message]
2014-10-02 4:46 ` [Bitcoin-development] Decreasing block propagation time Matt Corallo
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=CAFBxzAC6566OPT4Ex6Q6cnAAz0y8L6cg9wGcM_Tts401vCfxYQ@mail.gmail.com \
--to=rebroad+sourceforge.net@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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