control status: Show checkpoint height(s)

[matevz]

SUMMARY

Currently, there is no nice way to obtain the (latest?) checkpoint height that can be used for fast sync unless you already run a node and you check your datadir/consensus/state/mkvs_storage.badger.db/checkpoints folder. Add a list of available checkpoints to the control status output.

[martintomazic]

Is this still needed?

[matevz]

Is this still needed?

If not, then this chapter needs to be updated to reflect it https://docs.oasis.io/node/run-your-node/advanced/sync-node-using-state-sync

[kostko]

I believe it is needed so one can configure a sufficiently old trust hash/height.

[martintomazic]

I believe it is needed so one can configure a sufficiently old trust hash/height.

Ok I see. This is useful if you already have a node and want to spin another one or tell a "friend".

Optionally, this could be displayed as part of the explorer for people that don't have their node. (Although do we really want to encourage centralized points of truth).

Update: Nevermind, cli defaults to public gRPC endpoints, so no need to propagate to explorers.

[martintomazic]

If not, then this chapter needs to be updated to reflect it

Will think about improving the docs.

Right now I am more concerned with default trust period of 30days in the default config:

1. As stated by the state sync docs this value should be significantly smaller than the unbounding period (2 weeks in our case?).
2. Finally, checkpoints happen every week on mainnet, probably only the last one is useful for state sync given that older ones already fall out of unbonding period.
   • Related to this we might want to double checkpointing frequency?