2 ms·
You (and everyone really) should probably read some more comp.risks http://catless.ncl.ac.uk/Risks/ http://catless.ncl.ac.uk/Risks/ Certain fields have always
by pjc50 4y ago
You (and everyone really) should probably read some more comp.risks http://catless.ncl.ac.uk/Risks/ http://catless.ncl.ac.uk/Risks/
Certain fields have always had a high cost of programming error, including a cost in human life. It's just that cryptocurrency combines this with a first-to-market rush that's somehow still going on, encouraging a rush to error.
- bhaak 4y agoI don't disagree with that there have always been niche areas where there is a high cost to programming errors (like space or medical). But with crypto, the effect is much more direct. The programmer is handling money much more directly and if something goes wrong, they are much more directly affected and not being insulated from the effects.
- FabHK 4y agoYes. In space, aviation, and medical, it is usually someone else that is affected, not the programmer.
- progrus 4y agoAnd in space, aviation, and medical, it takes a long time to go to market.
- AmericanChopper 4y agoAt the first proper job I had we would measure our service outages in dollars per second. It was always in the thousands, and we were just a rather ordinary financial OLTP service.
- Yizahi 4y agoFirst to market is only part of the problem. Another self inflicted problem is that execution of those "smart" "contracts" cost tokens (so essentially money). This incentivizes developers to write the shortest possible code, without any "fluff" like tests or additional checks or more verbose style. And the immutability problem also increases severity of the problem - you either deploy immutable "contract" signifying that it should be respected because it can't be changed later for malicious purpose, or you deploy modifiable "contract" and that is not good for the reputation of the company.
- arlcode 4y agoImmutable code is a poor replacement for trust in a company. It shifts the trust from the company as it is now to the same company (and their capabilities) sometimes in the past. Preferably the company is operated completely anonymously. It seems like the crypto community would do anything to avoid the legal/regulatory system and it's established processes of operation requirements, insurance and liabilities. Doing that they regularly fail at performing the most basics of basic financial duties like not getting hacked and not throwing the keys to the kingdom. I've yet to hear of a bank loosing funds and getting away with telling "tough luck" to their customers, but we've witnessed many crypto "banks" doing just that.
- pjc50 4y agoThe closest I can think of is the TSB migration failure: https://www.theguardian.com/business/2019/nov/19/tsb-it-meltdown-report-computer-failure-accounts https://www.theguardian.com/business/2019/nov/19/tsb-it-melt... That also involved failing to have a viable rollback plan. It affected so many people so badly that questions were asked in Parliament; TSB were down for a week. Now with cryptocurrency we've disintermediated the bank to produce a much better solution: your contract can be down forever and there's no Parliament to ask questions in.