Log module hashes if an app hash mismatch is encountered
Context
It's difficult to debug an app hash mismatch because it's not immediately obvious which module is responsible for the mismatch.
Proposal
When debugging locally, Callum and I have resorted to debugging via this print statement. We may consider printing out all module store hashes if an app hash module is encountered. That way if a user encounters this, they can share helpful logs with us.
could you assign this to me, please?
@murluki are you planning on working on this? otherwise i'll have to get started on it.
@ninabarbakadze apologies, got caught up at work but will be posting it tonight. Sorry about the delay.
No worries! That would be amazing! Thanks! @murluki
added with https://github.com/celestiaorg/celestia-app/pull/4453