I wonder whether the financial industry is geared up for the possibility of hyperinflation. Ok countries have coped with it in the past, and there are countries in the danger zone now, but in my view if it were to occur in countries heavily dependent on computer processing of transactions in the future then there would be far bigger ramifications than hitherto.
The reason being that databases consisting of tables that contain fields for monetary units will not be able to store values (they will overflow).
At some stage a move away from having a decimal point in currencies would be a good way to go, because this will remove a big uncertainty as to how database developers treat currency. Then everyone will treat currency in terms of integers, or bigint's or whatever size you want to predict - migrating from one integer range to a bigger integer range is easier than what would happen if everyone had to migrate from what they use at the moment to something else.
For example, I am sure there are designers out there who use "lossy" formats to store currency. The most extreme example being floating point - could this be a reason why the Taunton to Trowbridge syndrome occurred? (see elsewhere on this forum). It is easy to cite floating point calculations which produce wildly inaccurate results because of the algorithm used - floating point arithmetic is not always commutative.
Certainly people are asking for trouble using float, but there are other number formats which have poor techniques for handling extremely large numbers - which effectively get rid of lesser significant digits, which is fine in the scientific world, but not in commerce. I'm sure many developers use such techniques believing they are sound, but are not.
In short, how many systems are going to break when stress-tested in this way? I suspect one helluva lot. Presumably there is some "test suite" that one can run financial transactions through, but have such suites been developed with an eye for hyperinflation, where currency transactions may consist of 25 or more digits - each of which needs to be accounted for?