Closed ttngu207 closed 4 months ago
On a separate note - there are a lot of those epochs with very short duration - please confirm that it's expected (or there's some error in the ingestion logic)
This is due to a bug in block detection, mixing aeon3 and aeon4 data. Fixed
This is for
'social0.2-aeon4'
Pellet time read from block state -
Timestamp('2024-02-08 15:04:58.433983803')
- does not belong to any epoch.These are the epochs around that timestamp
On this case, it looks like the epoch ended at
2024-02-08 15:00:00
(the last chunk of that epoch also ended at2024-02-08 15:00:00
). There isn't a new chunk starting at2024-02-08 16:00:00
, but there is a pellet timestamp at2024-02-08 15:04:58.433983803
retrieved from blockstate