(Hint: look at the publication date.)
128 bits isn't even enough to get to the putative half-life of proton decay.
There's some truly mind-boggling numbers in https://en.wikipedia.org/wiki/Future_of_an_expanding_univers... "the non-zero probability of producing a new Big Bang in roughly 10^10^10^56 years"(!).
These numbers are far beyond https://datatracker.ietf.org/doc/html/rfc2550#section-2.4.1 , which is only 10^14; about the time star formation ceases.
Time for an updated RFC!
(To be fair to the Long Now, not that they necessarily need fairness, and I'm not a member I just read about them here on HN mostly, adding the initial insignificant zero was intentionally an easy "hack" to keep things recognizable and not get into quagmires like changing the epoch date.)
In the case of the Holocene Calendar the bugs would just be a question of negative dates; in the case of UTC-12:00 it would be a nonnegative epoch time that is nevertheless in 01969 instead of 01970, which will only happen if someone adopts a more westerly timezone like UTC-13:00, pretty much guaranteeing you won't test that case beforehand. (Samoa did something similar in 02011, but it was in the other direction.)
Of course, as other people have pointed out, you shouldn't use fixed-width date fields in your software.
For an extreme version of this, 1961 might be written in scientific notation: 0.196100e4
This is also future-proof as we will always have a built-in 0 at the beginning of the number implying that we never get to "1" and there will always be more time to solve the problems we can't even begin to understand that may exist 10k years from now.
Sorry for the sarcasm, it was the easiest way to make my point.