• eg: PoS has math in the policy. The policy is subject to change
• eg: The amount of reward for each PoW is also mathematical and subject to change.
• eg: The level of difficulty (how many leading zeros) is a mathematical control, subject to change.

All of these policy complexities are breeding grounds for bugs and fraud. The complexity undermines the public trust and stability of this “currency”.

Imagine a network policy change (among other changes) requires a software upgrade. What if 44% of the nodes object to the policy change?

Who approves the pull request? Is there any oversight on the approval process? The approver and the original author could be brothers or even the same person using two identities 🙁

How can the millions of end-users trust the implementation, when the software is so complex?

In the legal system, individual judges form a hierarchy. The top judges are highly visible, under the spotlight. Their verdicts are constantly scrutinized and peer-reviewed. This legal system has evolved for thousands of years.

— I told Dahlan about my trust in linux or mysql or other OSS
The banks who use linux to maintain accounts have a big job to ensure each linux upgrade is well-tested. That layer (of protection) shields customers from the potential vulnerabilities in OSS.

I never had a doubt in any of my banks using linux. Similarly, I never had a doubt in them using manual calculation.