From: Matt Corallo <lf-lists@mattcorallo•com>
To: Tom Harding <tomh@thinlink•com>,
Tom Harding via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org>,
bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Idea: Efficient bitcoin block propagation
Date: Thu, 06 Aug 2015 20:55:15 +0000 [thread overview]
Message-ID: <1DEBDD04-5F00-4013-B332-A9293D775338@mattcorallo.com> (raw)
In-Reply-To: <55C3A4BF.1010509@thinlink.com>
On August 6, 2015 8:17:35 PM GMT+02:00, Tom Harding via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>On 8/6/2015 10:16 AM, Sergio Demian Lerner via bitcoin-dev wrote:
>> Is there any up to date documentation about TheBlueMatt relay network
>> including what kind of block compression it is currently doing?
>(apart
>> from the source code)
>>
>
>Another question.
>
>Did the "relay network" relay
>0000000000000000009cc829aa25b40b2cd4eb83dd498c12ad0d26d90c439d99, the
>BTC Nuggets block that was invalid post-softfork? If so,
The version check was only added hours after the initial fork, so it should have (assuming BTC Nuggets or anyone who accepted it is running a client)
> - Is there reason to believe that by so doing, it contributed to the
>growth of the 2015-07-04 fork?
The reason other miners mined on that fork is because they were watching each other's stratum servers, so the relay network should not have had a significant effect. Still, even in a different fork, miners already aggressively relay around the network/between each other, so I'm not so worried.
>- Will the relay network at least validate block version numbers in the
>future?
>
>_______________________________________________
>bitcoin-dev mailing list
>bitcoin-dev@lists•linuxfoundation.org
>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2015-08-06 20:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 19:07 Arnoud Kouwenhoven - Pukaki Corp
2015-08-05 19:27 ` Matt Corallo
2015-08-05 19:53 ` Arnoud Kouwenhoven - Pukaki Corp
2015-08-05 20:16 ` Gregory Maxwell
2015-08-05 21:19 ` Arnoud Kouwenhoven - Pukaki Corp
2015-08-05 22:14 ` Gregory Maxwell
2015-08-06 17:16 ` Sergio Demian Lerner
2015-08-06 17:33 ` Olaoluwa Osuntokun
2015-08-06 18:17 ` Tom Harding
2015-08-06 18:42 ` Gregory Maxwell
2015-08-06 20:50 ` Matt Corallo
2015-08-06 20:55 ` Matt Corallo [this message]
2015-08-06 20:38 ` Matt Corallo
2015-08-07 7:14 ` jl2012
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=1DEBDD04-5F00-4013-B332-A9293D775338@mattcorallo.com \
--to=lf-lists@mattcorallo$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=tomh@thinlink$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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