tendermint

Let's add info useful for debugging the web and mobile frontends.

• Node.js version (cc @marinhoarthur @JoseRFelix anything else?) — this is about the local version, not the one bundled with the CLI
• Dart/Flutter version (@Zfinix anything else?)

We introduced a system to manage flappy tests differently (see gnolang/gno#201).

The goal of this PR is to be kept open while there is at least one flappy test in the codebase.

To get an up-to-date list of flappy tests, you can use the following command: git grep func\ TestFlappy

Since raw queries only return encrypted keys, it's pointless and will break implementations coming from other networks without letting anyone know.

We should remove it from the next version

e.g. https://github.com/crypto-org-chain/chain-main/blob/0f99b253887b4bcce0dac2fd65635fb07c00920b/x/nft/keeper/keeper_test.go#L52

it may be worth switching to https://github.com/onsi/ginkgo

It could be helpful in the future to see which block producers are producing invalid blocks, so we should log their address after the application rejects a block.

https://github.com/celestiaorg/celestia-core/blob/69b91f082e1ed9cb348551143fbdc776be358020/consensus/state.go#L1284-L1290

Summary

When registering a resolver with the command-line, the content hashes JSON input is currently:

{
  "content_hashes": [
    {
      "graph": {
        "hash": "YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY=",
        "digest_algorithm": "DIGEST_ALGORITHM_BLAKE2B_256",
        "canonicalization_algorithm": "GRAP

Depends on: #443

Currently named ibctypes package provides helpers to fetch Consensus State and Validator Set from dumped files
We support the yaml format which is the default format of the dumping commands for our experimentations
We must in the future eventually support other format for dumped files