Add encode-content-key command to trin-cli

[jacobkaufmann]

What was wrong?

We lack a CLI command to encode content keys, which makes it difficult to interact with the network from the CLI if you want to look up content items.

How was it fixed?

• Split up top-level StructOpt into two commands:
  • json-rpc initiates JSON-RPC requests
  • encode-key encodes content keys
• Move help descriptions from attributes to doc comments.
• Define encode-key subcommand to encode content keys.
  • Support encoding for history content types.
  • Each content type is its own subcommand under encode-key.
    • There is some repetition here, but I think it makes the interface more intuitive.
• Update getting started docs.
  • Update existing JSON-RPC commands.
  • Add section for encoding content keys.

To-Do

• Add entry to the release notes (may forgo for trivial changes)
• Clean up commit history

[mrferris]

Looks great, works great 👍

[jacobkaufmann]

@carver do you want to take a look? Given that you seem to have a use case for this utility, I would like to see how well it meets your needs.

[carver]

@carver do you want to take a look? Given that you seem to have a use case for this utility, I would like to see how well it meets your needs.

A lot of it was just curiosity, and it ended up being pretty straightforward to just generate in python after a quick spec review. But I'm still happy to take a look!

[carver]

Yup, all looks reasonably to me!

[carver]

Any idea the history here of why it used to be -p trin?

[jacobkaufmann]

Not sure, but the two commands are identical, so I prefer the more succinct one. I wish I could remember if I even had a reason to change that in the first place 🤔.

[carver]

Obviously, after the build errors are fixed 😆