Fix REX maturity date bug

[DouglasHorn]

Fixing bug in REX maturity calculation that writes 2106-02-07T06:28:15 as the maturity date of some deposits instead of the proper maturity date, therefore locking SYS tokens in REX for 84 years.

Change Description

Deployment Changes

• Deployment Changes

API Changes

• API Changes

Documentation Additions

• Documentation Additions

[DouglasHorn]

I believe I might have found a solution to the REX maturity bug in EOSIO that locks up SYS tokens so they can't be withdrawn by writing 2106-02-07T06:28:15 as the maturity date instead of calculating the proper maturity date. It was calculating it as end_of_days which is time_point_sec::maximum() I'm not certain why they use this at all, frankly, but it looks like it was being calculated in a wrong place instead of using get_rex_maturity()

Would someone take a look at this and check my edit. I think doing this will not only prevent it from happening in the future, but allow users with locked REX tokens to fix them with the consolidate() action - making them available to unstake in 4 days.