Request for Enhanced Error Message Clarity: Improve Error Message for Invalid Hexadecimal Input

[ObiajuluM]

While working on signing and submitting payment transactions, I encountered an issue with the memo field. I inadvertently passed unprocessed text to the memo field, resulting in the error ValueError: non-hexadecimal number found in fromhex() arg at position 0.

This error message is currently quite generic, making it challenging to pinpoint the specific cause of the issue within the broader context of a transaction.

I would greatly appreciate it if the error messaging could be more specific in this scenario. For example, a more informative message could indicate:

• The invalid character is encountered within the memo field.
• The position of the invalid character within the string.

This enhanced clarity would significantly improve the debugging process and expedite issue resolution.

[ckeshava]

Hello, thanks for raising this issue. Can you share your input which caused this error ?

[ObiajuluM]

I was trying to create a payment transaction and I provided a memo field without formatting the memo_format parameter