I will report it because I was a little worried about the explanation of /local/account/transfers {incoming, outgoing, all}.
I am not good at English, so I'm sorry if I made a mistake.
It is written at line 1275 of index.html like this.
The following requests are similar to the ones above but are able to return transaction data with decoded messages.
In this sentence, it is an image that decodes HEX and returns it.
I think that this is unencrypt, not decode.
The grounds are as follows.
It describes the return value that executed this API.
- non HEX -> {”payload":"61626364656667","type":1} <-- (input value ="abcdefg")
- HEX------> {”payload”:”feabcd","type":1} <--(input value ="abcde")
- non HEX & Crypto -> {”payload”:"6162636465666768696a6b6c6d6e","type":1} <--(input value = "abcdefghijklmn")
- HEX & Crypto -----> {”payload”:”feabcdef1234567890","type":1} <- (input value -"abcdef1234567890")
Thanks
I will report it because I was a little worried about the explanation of /local/account/transfers {incoming, outgoing, all}.
I am not good at English, so I'm sorry if I made a mistake.
It is written at line 1275 of index.html like this.
In this sentence, it is an image that decodes HEX and returns it.
I think that this is unencrypt, not decode.
The grounds are as follows.
It describes the return value that executed this API.
Thanks