The max possible ttl is now 9223372036854775807ms or ~292471208.677536 years.

On heartbeat, we calculate the sum of the current time in ms and the ttl value. Because this calculation happens in the database query, there is no good way to clamp this value to avoid overflow. I propose we set reasonable maximums for the following values:

• the current time in ms
• the ttl

Setting a bound on the current time will actually be pretty easy because we can do it in assert at the top of the tick. We can choose a value so ridiculously large that the clock should never hit it even in a simulation. If this assertion is triggered, it is likely somebody is messing with the machines clock.

Then we would just need to choose a max ttl value such that:

max_clock + ttl <= 9223372036854775807

But let's create an issue for this and do it later.