I never claimed that. You claimed that I claimed it.
Yeah? Then WTF is this?:
This is simply a tired talking point with no technical basis. Looking at the current BSV GitHub repository:
gmaxwell - 144 commits
deadalnix (Sechet) - 766 commits
sepa (Wuille) - 835 commits
Your coin was largely built by Blockstream and Bitcoin Cash devs, and it remains that way.
You are quite clearly attempting to refute my point about relative fidelity to satoshi's protocol with some irrelevant claim about attributed lines of code - in other words, trying to use some aspect of a software implementation in a disucssion about protocol.
Huh, I didn't think you could fork protocols. I admit I didn't know that previously.
Regardless, BSV's "forking of the protocol back into near compliance with the original definition" is your opinion, and nothing more. You're playing a meaningless game of "gotcha" in order to avoid confronting the reality that, in addition to being on an entirely different chain twice removed from the original, your coin's implementation of the Bitcoin PROTOCOL contains stuff that renders it incompatible with the original implementation of the PROTOCOL.
OK, let's discuss it. The problem was fixed via soft fork. Anything else you want to bring up from 10 years ago?
You cannot just inject fancy stuff like Segshit or rbf into smtp / VoIP / FTP ... whatever and hope everyone buys that as being compliant after such , cause you kept the initial logo (ticker) that keeps some noisy idiots, anonymous, criminals and a herd of nuti-noobs with fancy hats 'using' that crap
Better ask a layer before coming to financial world
This is more of interest right now
https://mobile.twitter.com/CalvinAyre/status/1263167631076364288