Show Human Readable Protobuf Msg for Custom Txs

[paplco]

Is your feature request related to a problem? Please describe.
When working with custom messages such as those found in the Regen ecocredit module, users of keplr wallet will see the protobuf binary string for message value and not the human readable message.

I am using custom message registry method as described in: https://github.com/cosmos/cosmjs/blob/main/packages/stargate/CUSTOM_PROTOBUF_CODECS.md

This issue was noted as a side effect of protobuf singing.
Quote from commit: "Also, because protobuf sign doc is binary formatted, msgs not natively supported by Keplr may not be human readable."
The commit: f86844d#diff-0f59f6b531470706ceb26dfd437a9f532268c7db41145bbbc60c48d566bbc633

Describe the solution you'd like
Allow a way to show the human readable value of custom protobuf messages so that wallet users can verify what they are signing before approving.

Describe alternatives you've considered
Noticed that Osmosis custom messages such as type: osmosis/lockup/begin-unlock-period-lock do show human readable value with a schema as {"owner":"osmo123...","ID":"123457"}
Perhaps there is a workaround there, or perhaps they are using Amino encoding.

Additional context
Add any other context or screenshots about the feature request here.

[chismo950]

I also wonder how to use type, not type_url, do you know any documentation about it?

[mhagel]

@Thunnini is this issue still active?

It would be nice to see human-readable protobuf message details without forcing the amino API.

[frumioj]

See equivalent for Ethereum/Metamask at EIP 1138 ethereum/EIPs#1138