How do different implementations of the Bitcoin Cash client know which type of coin they're processing?

2

TL;DR: Where in this code does the SV client figure out that it's not processing an ABC blockchain?

This image prompted my question.

There are a couple different mutually incompatible (I am assuming anyway) implementations of the Bitcoin Cash cryptocurrency client software...

  1. Bitcoin Cash ABC
  2. Bitcon Cash SV

My question assumes that each implementation processes their respective transactions using similar but mutually-incompatible blockchain processing rules.

Is it normal to run a Bitcoin Cash SV client implementation in a Bitcoin Cash ABC network? And vise versa? How, then, does one implementation know that the network it is running in, is (in)compatible with its particular processing rules?

algoHolic

Posted 2018-11-24T14:55:03.457

Reputation: 29

Answers

0

They don't.

They have different, but sometimes common, consensus rules. There are two competing fork blocks with different transaction ordering rules and some transactions with either OP_MUL or OP_DATASIGVERIFY. One of the blocks are valid for that client, followed by many valid blocks. Sometimes, they process transactions of both network, as the replay protection is optional. They simply process if something is valid, or not if it's not.

MCCCS

Posted 2018-11-24T14:55:03.457

Reputation: 5 827

„...One of the blocks are valid for that client, followed by many valid blocks...“ — Thanks but that's still unclear to me. Please can you rephrase it to be clearer? Please, bear in mind; I am not an expert like you :) — „...as the replay protection is optional...“ — That too. Please paraphrase? Please can you address these original questions also: „...Is it normal to run a Bitcoin Cash SV client implementation in a Bitcoin Cash ABC network? And vise versa?...“ – algoHolic – 2018-11-24T17:44:44.240

1@algoholic 1) The following blocks are valid to that client, as they use the same consensus rules.2) Transactions made after the fork are valid on both chains by default, unless the different, new added opcodes are used. 3) There's no new network magic. As a result, nodes of different forks can communicate, but not about everything is valid for both. There are different consensus rules which are strictly different. Sorry for the unclear parts, it's definitely my fault. – MCCCS – 2018-11-24T18:00:13.020

Asked: 2018-11-24T14:55:03.457

Viewed: 59 times

Active: 2019-08-25T20:03:05.460