This came out of a discussion with @leighmcculloch. We want to make message generation extremely uniform, so every argument to a contract function should appear in the message. Currently, we are entirely excluding the Signature type (which includes more than just a signature) from the message.
What would you like to see?
It's not possible to include the signature itself (because you can't produce the signature without the message), so we should convert the Signature to an Identifier and include that Identifier in the message.
What alternatives are there?
It would also be reasonable to include a () in the message.
What problem does your feature solve?
This came out of a discussion with @leighmcculloch. We want to make message generation extremely uniform, so every argument to a contract function should appear in the message. Currently, we are entirely excluding the
Signature
type (which includes more than just a signature) from the message.What would you like to see?
It's not possible to include the signature itself (because you can't produce the signature without the message), so we should convert the
Signature
to anIdentifier
and include thatIdentifier
in the message.What alternatives are there?
It would also be reasonable to include a
()
in the message.