My pet theory is that every software product has a "peak version". Before that peak version, the product is not yet in a complete state, and it is fairly obvious, both for the developer and user, what features are missing. Once the peak version is reached, new features are not added because they improve the product, but to justify selling the product again to existing customers, and to 'keep the team busy'. Instead o…
Keeping bean counters shouldn’t be the goal, but everyone does like to keep eating. What do you suggest for keeping the business healthy while not making things terrible?
Only problem there is that as ASICs are developed, general purpose CPU mining rapidly becomes grossly inefficient, so you'd somehow need a decentralized coin optimized for extremely high usage scenarios that was also resistant to ASICs. Not really sure how you'd achieve that latter part without simply constantly changing the algorithm, but it poses a complex challenge of changing the algorithm in a purely decentralized fashion in a way that one can not build adaptive ASICs for. Though I would imagine this is a solvable problem.