The expiration timestamp was added to the current time upon deserialization, as if it were an offset. Fix the ambiguity in the internal API.
