Closed pinnate-modo closed 1 day ago
This happens when a block is currently being parsed. The blocks are initially inserted with null hashes, and the hashes are updated at the end of the parsing process. Additionally, the API database may take some time to be updated as all events need to be parsed. If this only occurs with the last block, it is not a bug.
I think this should be fixed, but it's not urgent.
e.g. it will report null consensus hashes in the
/blocks/<block_height>
route, and if you look in the sqlite3 db you'll see that the values are there and correct. Similar issues were reported with MINTS' supply.