fip | title | status | type | author | created | updated |
---|---|---|---|---|---|---|
28 |
Delay FIO Address burning after expiration |
Final |
Functionality |
Pawel Mastalerz <[email protected]> |
2021-05-18 |
2021-06-04 |
Contract | Action | Endpoint | Description |
---|---|---|---|
fio.address | burnexpired | /burn_expired | Burn expired FIO Addresses 365 days (up from 90 days) after it has expired. |
There has been an ongoing discussion regrading potentially eliminating FIO Address expiration. In order to provide adequate time for that discussion to conclude and in order to address community's concerns regarding the potential security risk of an expired address being re-registered by an attacker, this FIP proposes extending the time from FIO Address expiration to burning from 90 days to 365 days.
Burn expired FIO Addresses 365 days (up from 90 days) after it has expired.
Unchanged
Burn expired FIO Addresses 365 days (up from 90 days) after it has expired.
Unchanged
Since FIO Addresses will begin to be burned on June 22nd, a solution which can be implemented the fastest was preferred.
Released in fio.contracts v2.3.5. The burn period was moved from 90 to 365 days after expiration.
No changes to actions' request/response.
A long-term strategy for FIO Address expiration is being considered.