There is lots of scope of improvement in the `tkn chains` command. Currently it prints payloads and signatures in TaskRuns but there is a lot of manual intervention needed post that since output is in binary and non human-readable format. It needs to be piped to other tools to make meaning out of it.

We need to explore on how the chains subcommand be improved and become a first class citizen.

More details need to be provided by whoever picks this up in a TEP, but here are my initial thoughts:

• rekor integration (so finding and using UUID becomes intuitive)
• cosign integration (so signature and attestation verification becomes intuitive)
• setting config values can be done via the CLI instead of having to edit the configmap

On the UI side of things:

It needs to be explored if having a UI for Tekton Chains which can -

• show signatures, attestations
• verify TaskRuns
• sign images and artifacts
• configure Chains via dialog box
• enable/disable signing, etc
  will add value to users or not!?