Quote from: pooya87 on Today at 07:20:39 AM

Quote from: franky1 on Today at 06:26:02 AM

basically saying it does everything it can to follow core

Wrong. It is saying it does everything to follow the consensus rules.

Quote

it just wants to follow core, including the bugs. just in a different language.
rather than know what the rules are and have its own less cludgy, buggy methods of doing things to get to the same result

Bugs in this context don't mean what you think they mean.
Two examples of "bugs" of the top of my head are counting sigs in coinbase signature script (sigopcount) and popping an extra item from the stack in OP_CheckMultiSig(Verify).
These are part of the consensus rules that all implementations should follow. They can't be changed without a hardfork.

you snipped out the quote i mentioned which you linked previously. because,, oops the quote mentioned core in each paragraph, which hurts your rebuttal

it also stated it followed all cores test data, thus followed cores possible errors if their test data were wrong/buggy too
please try to read.

do you also know why btcd even used version number 0.22.0 right now. to display they are following the core version 22

as for saying 'its just following consensus. which you forget, whom is in control of consensus changes. yep one dev team, and who is that dev team.. (rhetorical)