Implement tendermint lite client commands about relayer-archive HOT 8 CLOSED

Anton and I discussed the cli interface and proposed the following changes:

• Merge the Init and Update Cmd to a start command because they almost do the same thing.

• Add a getHeader and getValidatorSet command which takes the height as an argument and returns the header and validator respectively. This can be used to confirm that what has been relayed is now in the other blockchain.

from relayer-archive.

cc @cmwaters

from relayer-archive.

I propose the following sub-commands:

lite reset [chainID] --trusted-hash=0xaaabbb --trusted-height=1
lite reset [chainID] --url https://xyz.com
lite delete [chainID]

lite header chainID # returns latest header without params
lite header chainID 1 # returns header at height 1 (if stored)
lite header chainID -1 # returns first stored header

lite vals chainID # returns latest validator set without params
lite vals chainID 1 # returns validator set at height 1 (if stored)
lite vals chainID -1 # returns first stored validator set

from relayer-archive.

Q:

1. do we need lite stop and lite delete sub-commands? What's the point of stopping the light client? maintenance?
2. should lite stop also delete all the data? What's the point of having a separate command?

My opinion:
we don't need stop (for now) but delete is required because process can crash and the user will need to manually delete the data sometimes.

from relayer-archive.

@melekes agreed with removing stop and adding delete. Like the lite get-header and lite get-valset. Would be nice if you could also use that to query for the roots of trust too.

from relayer-archive.

Update the list of sub-commands: cosmos/relayer#1 (comment)

from relayer-archive.

Would be nice if you could also use that to query for the roots of trust too.

that's what lite header is for

from relayer-archive.

@melekes @cmwaters really enjoyed working with y'all on this. Going to close this issue as complete!

from relayer-archive.