Mitigation Solutions for Path Dependencies

Published by Mario Oettler on

Once a path is taken, it is difficult to leave it, even if it proves to be the less efficient choice. Therefore, it is essential to study measures to overcome a current path dependency:


If a new solution arrives, it has to make switching as easy as possible. One reason for staying on a certain path is the uncertainty of whether others follow or not. If they don’t follow, all their efforts on the new path might be vain. Therefore, it is helpful to allow compatibility with the old path to mitigate the risk. So, users can switch easily back and forth without losing all their work done on one path.

Built-in Break Points

There must be a breakpoint where the whole process is reviewed and forced to update. In Ethereum, for example, this is enforced by the difficulty bomb.