📅 Original date posted:2015-08-06 📝 Original message:On August 6, 2015 8:17:35 ...

Matt Corallo [ARCHIVE] /

npub1e46…xmcu

2023-06-07 15:45:29

in reply to nevent1q…erwu

📅 Original date posted:2015-08-06
📝 Original message:On August 6, 2015 8:17:35 PM GMT+02:00, Tom Harding via bitcoin-dev <bitcoin-dev at 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 at lists.linuxfoundation.org
>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Author Public Key

npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcu

Show more details

Published at

2023-06-07 15:45:29

Kind type

1 Short Text Note

Event JSON

{ "id": "65d846c344b2bcca327c7bd32c0d9e008903baaef2f07a570e03e5fd76dc2938", "pubkey": "cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba", "created_at": 1686152729, "kind": 1, "tags": [ [ "e", "158880a596c782b1fb4c5a60a229c1c08a5de1f9a4400f68dd2a5506a1a8001b", "", "root" ], [ "e", "eaecac9f68f1a2539bddb28098c345c0ff34ad75de205edcc91214ad6522d4df", "", "reply" ], [ "p", "cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba" ] ], "content": "📅 Original date posted:2015-08-06\n📝 Original message:On August 6, 2015 8:17:35 PM GMT+02:00, Tom Harding via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003eOn 8/6/2015 10:16 AM, Sergio Demian Lerner via bitcoin-dev wrote:\n\u003e\u003e Is there any up to date documentation about TheBlueMatt relay network\n\u003e\u003e including what kind of block compression it is currently doing?\n\u003e(apart\n\u003e\u003e from the source code)\n\u003e\u003e\n\u003e\n\u003eAnother question.\n\u003e\n\u003eDid the \"relay network\" relay\n\u003e0000000000000000009cc829aa25b40b2cd4eb83dd498c12ad0d26d90c439d99, the\n\u003eBTC Nuggets block that was invalid post-softfork? If so,\n\nThe 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)\n\n\u003e - Is there reason to believe that by so doing, it contributed to the\n\u003egrowth of the 2015-07-04 fork?\n\nThe 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.\n\n\u003e- Will the relay network at least validate block version numbers in the\n\u003efuture?\n\u003e\n\u003e_______________________________________________\n\u003ebitcoin-dev mailing list\n\u003ebitcoin-dev at lists.linuxfoundation.org\n\u003ehttps://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev", "sig": "0112ae11d1ef3ac2408f3e8a35cf109495f0cdba189ebd8289ffb8d07395bd6755332184776e6e0ea8f816cc0e818e7e5afc283e9d19eb560905a27e353a9079" }