Closed frol closed 3 years ago
@khorolets yes, please
For future me, data for testing
e0dadd3367ca0f8f655ebbef319253c276813632.lockup.near
259247d17d2f79793776d86ab713dfa0ef09ab800959a0ee41ad974c9840e148
By the way, we broke it again. I'll fix it in current PR
Before:
With this fix:
lockupTimestamp
set, won't display the explanation messagelockupTimestamp
into account just fine (correct start date and computation)