Skip to main content
11 events
when toggle format what by license comment
May 11, 2022 at 22:30 vote accept natevw
May 11, 2022 at 22:29 comment added natevw Thanks for finding my old question and offering such a well-rounded answer after all these years! Makes sense that any of these mechanisms could keep the forks mostly separate, and especially when working all in combination.
May 10, 2022 at 15:27 history edited RedGrittyBrick CC BY-SA 4.0
added 2 characters in body
May 10, 2022 at 15:17 comment added RedGrittyBrick @Pieter: Thanks, I have added that information to the answer.
May 10, 2022 at 15:16 history edited RedGrittyBrick CC BY-SA 4.0
added 485 characters in body
May 10, 2022 at 12:57 comment added Pieter Wuille @RedGrittyBrick The shunning is correct. Relaying an invalid block is a protocol violation (in most cases; there are exceptions), and (in Bitcoin Core) will cause the peer to be considered misbehaving. Misbehaving peers are eventually put on a "discouraged" list, which means their connection slot will be dropped and replaced by another when a non-discouraged IP connects. Bitcoin Core further has a mechanism to temporarily actively seek out extra connections when it appears none of its peers have a recent valid block.
May 10, 2022 at 12:10 history edited RedGrittyBrick CC BY-SA 4.0
added 515 characters in body
May 10, 2022 at 12:03 comment added RedGrittyBrick @Michael, Thanks, I'll add that to my answer.
May 10, 2022 at 11:00 comment added Michael Folkson The P2P handshake may also be different (en.bitcoin.it/wiki/Protocol_documentation#version). It depends really whether the hard fork was trying to disrupt Bitcoin as much as possible or it was happy to "play nice" and have a different port, P2P handshake etc
May 10, 2022 at 9:56 history edited RedGrittyBrick CC BY-SA 4.0
added 338 characters in body
May 10, 2022 at 9:41 history answered RedGrittyBrick CC BY-SA 4.0