What do you think about tool parse, and accept all: address, pubkey or scripthash, and show all that it can resolve at same time?

I prefer to add these functions to GUI.

@meevee98 @shargon @erikzhang I've already made a simple tool to support most of conversion method. https://github.com/neo-ngd/Neo3-Tool. If you'd like, could adjust and merge it into your code.

What do you think about tool parse, and accept all: address, pubkey or scripthash, and show all that it can resolve at same time?

I agree that it's better than having a different command for each conversion. I will modify the code in this way.

@meevee98 @shargon @erikzhang I've already made a simple tool to support most of conversion method. https://github.com/neo-ngd/Neo3-Tool. If you'd like, could adjust and merge it into your code.

Nice. If I may, I will include the other conversions to this implementation.

I prefer to add these functions to GUI.

I think that these commands are also useful in neo-cli.
When we deploy a invoke a smart contract using the neo-cli, the return result is showed encoded in Base64, so a converting tool is needed anyway. If it's in the same application, the work gets faster, doesn't it?

I would love to have this commands on Neo-Cli, thank you Meevee

I've updated this pull request with @shargon's suggestion of tool parse command.
I've also included the other conversion methods from @superboyiii's tool.

It's a unique command now that accepts any value and returns the possible conversions

Tested.

Do we still need to support converting a little end script hash to address?
There is only the big end script hash in your comment, but, in your code, the little one is also included.
If we support both of them, users must pay close attention to the format. 0x61ce772f7a725f93d8311dba9994dd8c50e3e64b and 61ce772f7a725f93d8311dba9994dd8c50e3e64b are quite different.

It's no problem for me @shargon

Maybe we should filter in base64ToString to only ASCII chars. And HexString to String to "non-empty"

Also it's not possible to be Hex if there odd letters

@meevee98 I am not sure if it's my computer, but it spend a lot of time in something trivial, could you check it?

Maybe we should filter in base64ToString to only ASCII chars. And HexString to String to "non-empty"
Also it's not possible to be Hex if there odd letters

@shargon I agree with the empty strings, but I think that the conversions to a string with non-ascii characters should be kept.
I've seen in many smart contracts the concatenation between a string prefix and a bytearray been used and the result usually can't be converted to a string with only ascii characters, so it is possible to be a valid hex string even if there are some odd letters.

For example, this hex string is converted to a string with many non-ascii characters

But that is because part of the hex string is the scripthash of an address

@meevee98 I am not sure if it's my computer, but it spend a lot of time in something trivial, could you check it?

I'm not having this delay 🤔

but I think that the conversions to a string with non-ascii characters should be kept.

Ok :)

I think that 0.2 seconds in your computer it's a lot of time.... we need to find the issue

@shargon I was able to reduce the time to 0.1 seconds by removing the exception throwing in the conversion methods and replacing them with return null.

Could you check if the time is reduced on your computer as well?

@meevee98 It's out of date, could you update it to the latest?