pull down to refresh
If your use of bitcoin requires honest developers, how do you expect it to do its job? If we are here using bitcoin because we believe it has a chance to resist the state, we have to expect that the state will attempt to compromise the development process. And I don't think that is something that we can count on recognizing. Therefore, we should expect that there will be compromises and position ourselves so that we don't have to care when it happens.
Having multiple implementations makes it easier for users to jump ship when flaws are spotted or because they feel that the implementation is compromised. When there's only one viable implementation, jumping ship means forking and building a community around a new fork. Seems like it would be far more desirable to already have a community of developers working on it.
jumping ship means forking and building a community around a new fork
Bitcoin doesn't need any forks... it's fine as it is IMO
I was referring to a fork of the Core repo, not validation rules.
OK thanks for the clarification sounds good
"You're weak on logic, that's the trouble with you. You're like the guy in the story who was caught in a sudden shower and who ran to a grove of trees and got under one. He wasn't worried, you see, because he figured when one tree got wet through, he would just get under another one."
Well, I thank you for the Asimov story, I hadn't read that one.
Having been in a number of rain storms, I know that some trees provide better cover than others.
If you prefer a world of one implementation that is battled over like some holy ground, have at it. We should all be pleased that Bitcoin is a permissionless network.
I said expect not ignore. Multiple implementations seem to me to increase the expectation of review. Rather than relying on one implementation, users would have to actively choose their software. I completely disagree with you.