as I said not sure why your core should be corrupted, we check its hash before starting using it at least. so it was corrupted later than when it was refreshed (in theory).
can you download as I did core again and find out if the size is the same? how different/corrupted it is?
No other problems I know about. As I said, I was using snapcraft fine earlier in the day yesterday, then did some updates via apt, rebooted in the evening and it stopped working at that point. Speculating that may be related as I don’t reboot often - this was 12 days uptime.
and as you can see there is a difference of 4 bytes (32bit) in the file. I suspect there is some disk/memory corruption here. However this should be very rare - so if more people are affected it could be something else.
That leads to the question of why it was able to install a core which was ‘broken’ and didn’t roll back or produce an error? if the sha3sum is wrong, why did the core get used?
as we said we do check the hash (actually more than once) during install/refresh, so the file got corrupted later, or there was some kind of memory vs disk content issue during install. Or yet a completely different kind of issue we are not seeing yet.