Fix RPC responses for Hash160 types about neo HOT 7 OPEN

That is not how it is done. There is no way in the VM to know what is hash160 or hash256

CSharp

var address = new UInt160(Convert.FromBase64String(byteStringValue));

from neo.

Hello,

Maybe not the VM, but the node. The types are stored in the contract manifest.

from neo.

That will change the interface and break all current apps using it.

from neo.

Yes, and this is too dangerous to change. The best solution might be to add another RPC endpoint and change the SDKs first.
We can argue that developers should use their own RPC nodes, but most applications use public RPC nodes. Then, it's probably ideal to introduce a new endpoint instead of changing the existing ones.

from neo.

That's to much. When a developer can easily change the base64 to bytes and reverse bytes.

from neo.

This can't be fixed, see neo-project/neo-modules#609 (comment)

from neo.

Why it can't be fixed if it's an RPC endpoint?

The 'GetInvokeResults' method is not part of the VM. It could accept an additional parameter to parse types using the manifest.

If the conversion fails, it's because there is a bug in the smart contract. Most compilers won't allow you to return different types. This can only happen using "incorrect" storage calls.

If the conversion fails, the developer can either fix their contract or omit the "parse types" parameter.

from neo.