As the reporter, I'll note It WAS corrected for a brief while after the initial ‘fix’ but has reverted to the incorrect line.
Pretty sure it's a *programming* bug somewhere rather than a data entry error since the incorrect value is the default value of an integer in most programming languages and not anything anyone would ever actually enter a date.
Though that begs the question why other coins with the same 2023-ending date range don't exhibit the ame problem
Only part of the database is updated overnight, it might take up to 10 days to update everything. But since this was updated on first of October, I guess it should have been fixed already.
